Moving to dev list. You can act as release manager. You can just svn rm the existing 2.0.1 tag, and I'd use the existing scripts to create the tag and the release candidate: http://svn.apache.org/repos/asf/pivot/infra/bin/create-tag.shand http://svn.apache.org/repos/asf/pivot/infra/bin/create-release.sh
-T On Tue, Nov 15, 2011 at 5:33 AM, Sandro Martini <sandro.mart...@gmail.com>wrote: > Hi all, > tomorrow I think I'll close (I hope forever now :-), code has already > been committed last week and all is working in my environments) > remaining issues for 2.0.1, and then we could start to prepare the > much awaited 2.0.1 release !! > To block newly to 2.0.1 only important issues should be discovered this > week ... > > Someone has objections (or problems that need to be fixed) ? > Roger, all is good for you ? > > Tell me. > > > Do you think could be a good idea to prepare a snapshot for jars, and > ask even our users to make some test on it (saying they are and rc, > but I'd prefer to not vote an rc, so the "snapshot" term) ? > > > @Todd: > I can be the Release Manager, or do you prefer to do it yourself ? > > > Remainder for me (sorry, you know my little memory ...): > when all is good, delete existing 2.0.1 tag and re-tag ... > > > Bye >
