it's usually best to make sure that other folks aren't going to be committing to the wrong project. it's also inconvenient moving uncommitted code so folks may want to finish up first. so, the way these things have been done in the past is for a volunteer to post a proposal with a time and if no one veto's by the time it arrives, go ahead.

same with the release. it's usually best to push out a release candidate first follow later by the release. the initial stage would be for someone to propose someone to act as release manager.

- robert

On 18 Nov 2004, at 21:43, Oliver Zeigermann wrote:

OK, I am asking too much, I will just try and see if just moving the
projection works. Is there anything else that should be done then?
Docs are ok, JUnit tests as well, stuff is feature complete and
stable. Why not call for a relase vote?

Please tell me if I got it all wrong again ;)

Oliver

On Thu, 18 Nov 2004 22:36:22 +0100, Oliver Zeigermann
<[EMAIL PROTECTED]> wrote:
On Thu, 18 Nov 2004 20:01:53 +0000, robert burrell donkin
<[EMAIL PROTECTED]> wrote:
On 18 Nov 2004, at 16:09, Oliver Zeigermann wrote:
after the result's been announced (and providing no objections are
lodged by the pmc) i would suggest that the next step you can take is
to start drawing up a migration plan (who'll do what when) and start
thinking about planning for a release (the wiki's a good medium for
release planning).

May idea was that I just copy the project from sandbox to proper without changes and then start a vote for a 1.0 release. Am I just an idiot?

Oliver


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to