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. > > > > >
