As for all steps I think there is a little bit more, but I'm not sure
what it looks like after a certain point, ie signing and posting the
release according to the ASF process, and of course learning that is
part of the point of the release candidate (RC).
When we do a final release we'll want to do a branch, but I'm not
sure if we want to do that for release candidates at this point
(unless there is something being developed we want to keep out of the
release... ?).
Anyway, the full release process I think would look something like this:
1. svn export (either trunk for early RC, or the release branch for a
release or later or more isolated RC)
2. for a framework only build: remove the applications directory
3. ant run-install
4. zip/tgz and PGP sign
5. post somewhere for download - perhaps on the wiki until it's
official or something?
6. send request for review to Incubator PMC
7. add links to it on the Apache OFBiz (should we start using
AOFBiz?) web site and incubation status page
On #5: for the incubator I guess this is different from the main ASF
download mirrors and would just go on the web site server or
something? If it goes on the web site I guess we should add it to the
site directory in SVN, perhaps in a releases sub-directory or
something, and then just update on the people.apache.org server and
off it goes...
Looking at these the next step is to figure out what we need to do
for PGP signing. If I understand it right one of the individuals on
the PMC would just use their personal key to sign the release. Is
that correct? If this person needs to be in the web of trust and that
needs to be done face to face with an ASF member that is already in,
then perhaps Jacopo would be the best candidate for this as he can
somewhat easily meet with David Welton. Does that sound reasonable?
Then Jacopo could just sign this first release.
There are some other things we should probably do, like release notes
and testing and such. We used to spend quite a bit of time doing
those early on which is one reason we stopped doing releases so much:
it got to the point where it took a few days to a couple of man-weeks
just to go through and prepare everything. There has been quite a lot
of testing and fixing going on recently, and we can refer to Si's
blog and the Jira tracker in a fairly short and simple release note.
Does this sound reasonable?
-David
On Sep 2, 2006, at 8:49 AM, David Welton wrote:
I've updated the "developers" page, the Incubator status page and
also
I've committed the last license changes and now OFBiz is licensed
under
the ASL2.0
Thanks!
Now we have completed *all* the tasks in the Incubator's status page:
http://incubator.apache.org/projects/ofbiz.html
I guess that, the very last step before starting the exiting
process is
to prepare a release candidate: since the LICENSE and NOTICE files
are
already in SVN, and since the current SVN is pretty stable, I
think it
is a matter of:
1) exporting (svn export) the svn tree
2) zipping it
Am I simplifying too much the whole thing?
Well... depending on your plans for the release, you might think about
QA'ing it some, and adding in any docs that are available, but that's
up to you guys.
Should we prepare a schedule for the last steps in order to quickly
start the exiting process?
Yes... I'm kicking myself for not having done a GPG key exchange with
David J in Portland. We could do one here in Padova, to start tying
you guys into the GPG "web of trust":
o Releases are PGP signed by a member of the community
o Developers tied into ASF PGP web of trust
Aside from that, though, we should be in pretty good shape. Yoav,
any comments?
--
David N. Welton
- http://www.dedasys.com/davidw/
Linux, Open Source Consulting
- http://www.dedasys.com/
