[petsc-dev] What needs to be done before a release?

Sean Farley sean at mcs.anl.gov
Fri May 11 11:59:51 CDT 2012


>    You can continue to do development; just continue to PULL into your development repository but don't PUSH to the master. To apply fixes to petsc-dev use another repository or one of "the cool guys" (Sean, Jed, and Matt's) way of only pushing up some changes.

I use phases (introduced in 2.1) to mark changesets as 'secret' so
they don't get pushed:

http://mercurial.selenic.com/wiki/Phases

I also use the color extension so that I can see the phase of each
changeset, see my .hgrc for example:

https://bitbucket.org/seanfarley/settings/src/1db1e00bd5b1/.hgrc



More information about the petsc-dev mailing list