Hi,
I'd like the release guide if the steps we follow are a bit different
than what is normally done or if there are some variations to how we
perform some steps. But if we were just about going to rephrase all
of what has already been said somewhere else I'd prefer just about
having a pointer
As an example of how much simpler things could be if we got our maven builds
set up so maven automated everything see:
http://incubator.apache.org/cxf/building.html#Building-Performingarelease
But, I still think a RM should understand whats going on so mvn shouldn't be
a substitute for having
Let me come up with some initial document over the weekend, and we
could start providing feedback on top of that, also we could check if
there is going to be any value on that or not.
On 7/25/07, ant elder [EMAIL PROTECTED] wrote:
As an example of how much simpler things could be if we got our
Luciano Resende wrote:
Should we start thinking on a formal release guide, merging together
couple documents we already have as of today, and also creating a
checklist as it looks like couple release candidates are having the
same issues ?
+1 - yes, most definitely.
Yours, Mike.
I agree we could do things to improve our releases. Most ASF releases end up
having several RCs, its a natural part of the process, I'm not sure it
indicates any failing somewhere. We've been restructuring our builds and
distributions recently, with changes like that going on there will be
snip..
There's already lots of doc about doing releases in the ASF - on the ASF
main dev pages and within the Incubator site etc.
The problem with there being lots of docs is that there are, ahem, lots of
docs. Where is the definitive set of guides that provide the detail required
to
On 7/24/07, ant elder [EMAIL PROTECTED] wrote:
I agree we could do things to improve our releases. Most ASF releases end up
having several RCs, its a natural part of the process, I'm not sure it
indicates any failing somewhere.
IMHO when you use the RC method, having multiple RCs does not
On 7/24/07, ant elder [EMAIL PROTECTED] wrote:
snip
- change builds to use the maven release plugin to avoid most of the manual
steps when creating a release
- use maven to as much as possible automate the adding of dependency
information to the LICENSE and NOTICE files
- update the RAT tool
Should we start thinking on a formal release guide, merging together
couple documents we already have as of today, and also creating a
checklist as it looks like couple release candidates are having the
same issues ?
-- Forwarded message --
From: ant elder [EMAIL PROTECTED]
Date:
