balay at petsc:/sandbox/balay/petsc-dev $ hg tags tip 23486:c76fb3cac2a4 release-3.2 20307:cad0859b4453 release-3.1 15532:f6965e7f147c release-3.0.0 13216:621178841b37 release-2.3.3 10547:c59a3fc37afc release-2.3.2 9364:1aa4d6336f27 balay at petsc:/sandbox/balay/petsc-dev $
When we do the release - we do add a tag for it [in the release repo - that propegates to petsc-dev]. But the release is not done yet. However we haven't been adding tags for patch updates. Satish On Thu, 31 May 2012, Dave Nystrom wrote: > Is there a tag that reflects the petsc-dev state at release time? > > Thanks, > > Dave > > Satish Balay writes: > > I've now created the release repos - so petsc-dev is now open for all > > commits. > > > > [If you've accumulated petsc-dev related commits - rebasing them with > > current petsc-dev - before pushing would be good.] > > > > > > Release related commits should now go to the release repo [and not > > directly to petsc-dev]. Please use the usual release repo > > workflow. i.e: > > > > - clone the release repos > > - commit/push [to release-repos] > > - from petsc-dev clone - pull/merge release commits and push to petsc-dev. > > [or defer this last step to me until the release] > > > > ssh://petsc at petsc.cs.iit.edu//hg/petsc/releases/petsc-3.3 > > ssh://petsc at petsc.cs.iit.edu//hg/petsc/releases/BuildSystem-3.3 > > > > Satish > > > > On Thu, 17 May 2012, Barry Smith wrote: > > > > > > > > petsc-dev folks, > > > > > > Recall that we are in a phase of a code freeze that means do not > push random new code to petsc-dev, push only bug fixes and clean up to > petsc-dev. By all means keep on with code development, just don't push the > new stuff to petsc-dev. > > > > > > We hope to make the release repository (and then tarball) next > Wednesday May 23. So please do be checking the nightly builds and making > fixes to petsc-dev. > > > > > > Barry > > > > > > Note: threaded code and GPU code will not be supported with the release > (users should continue to use petsc-dev after the release) so > fixes/extensions to those things are not needed and shouldn't be pushed to > petsc-dev at the moment. > > > > > > > > >
