Hi Stuart,
On Jan 6, 2010, at 3:07 AM, Stuart Monteith wrote:
Hello Craig,
I have already volunteered to be the release manager,
Then you have already passed the biggest hurdle. ;-)
although unless you've read through the past couple of months of
postings you are unlikely to have picked up on that, it's not
written on our wiki pages. I have taken some tags for the release
candidates - currently there is only Steve and myself who is
commiting code. This is our first release, so we are feeling our way.
That is the Apache way. Look around at other projects, especially at
other incubating projects that have made releases. There are several
examples within the past month.
I've been wanting to get the release done correctly, without any
nasty ongoing legal problems.
It's unlikely that you will encounter ongoing legal problems. Getting
a release candidate reviewed by the RAT program will expose much of
the legal issues. The rest is making sure that the release bits are
reviewed by the kato team and voted on and then voted on by the
incubator.
Quoting Robert Donkin from the 14th December:
"i've been floating the idea of a multi-stage audit to try to help
podlings pass the technical side of their first release without too
much pain. fancy trying it out?"
I replied yes, it sounded like a good idea, but we've still to get
details of what that involves.
I'm not sure either. Robert is busy with some schoolwork so you might
inquire on the incubator list to see if he's communicated his ideas
more widely. I don't recall any details.
Regards,
Craig
Thanks for your input Craig,
Stuart
Craig L Russell wrote:
If there is consensus (no need for a vote, just discussion) that
it's time to make a release, *someone* needs to volunteer to be
*release manager* and actually take control of the release process.
[Usually the release manager creates an svn branch for the release
so by definition it's frozen at that point. Nothing gets added to
the release branch without explicit permission from the release
manager.]
Once you have a release manager, there's a process that each team
works out. You can copy others' release process or make your own.
Here's the process that OpenJPA uses. http://openjpa.apache.org/releasing-openjpa.html
It might be too heavyweight but offers some things that you should
be thinking about anyway, like how to stage the release, how to
vote, what to name releases, etc.
Good luck,
Craig
On Jan 5, 2010, at 7:06 AM, Steve Poole wrote:
Soooo same question ... Do we just call a vote now?
Sent from my iPhone
On 5 Jan 2010, at 13:59, Stuart Monteith <stuk...@stoo.me.uk> wrote:
I second that. I'd like for us to freeze changes to the codebase,
except those
that are necessary for a release - and for us to do what is
necessary to make
a release available.
Thanks,
Stuart
Steve Poole wrote:
Greetings to everyone - hope you all had a good holiday.
Just trying to get back up to speed. i did spend some time
working on a
experimental implementation to help with the Snapshot API
discussion. I'll
share more about that later.
In the meantime - what do we do next with the release candidate
- do we just
need to call a vote ?
--
Stuart Monteith
http://blog.stoo.me.uk/
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@sun.com
P.S. A good JDO? O, Gasp!
--
Stuart Monteith
http://blog.stoo.me.uk/
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@sun.com
P.S. A good JDO? O, Gasp!
