Am 30.06.2011 14:17, schrieb Robert Burrell Donkin:
On Thu, Jun 30, 2011 at 12:39 PM, Eric Charles<e...@apache.org> wrote:
<snip>
I was just wondering, especially when I see how the other Apache projects
create there releases, if we could rely for beta2 on a manual check, and
report the automated track for next release.
A fully released automated tool set is unlikely to arrive for a few months.
I would like to see an efficient release pipeline which will allow
James to be released often.
Let's see you could split and distributed the remaining jars to be reviewed
in 3 or 4 parts, each parts being taken by a committer responsible to add
the needed mention in the NOTICE.
Parallelism is unlikely to save much time at this stage, and might
slow stuff down. Everyone should really independently audit the
components in the assembled artifact and ensure that the contents of
the NOTICE and LICENSE are right.
The main issues for me are a slow development cycle caused by
unnecessary integration and targeting a moving target. IMO eliminating
this bottleneck will save more time than the cost of cutting the
additional release. Once we have a smooth pipeline, if this call turns
out to be wrong, we can just move the assembly back in.
Robert
I'm still not 100 % conviced.. Why not just freeze trunk for a few days ?
Bye,
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
