I think following the same approach as Archiva is the best way to go.
Let's pick out how many we can do in the first two weeks, then do a
big "bug bash" to try and find all the known issues and file them
either for further betas or 1.1.x. Then we should know how many betas
we'll have left.
Brett Porter a écrit :
On 02/08/2007, at 7:46 AM, Emmanuel Venisse wrote:
For a project notifier, I think we can keep what we have actually, but
for a group notifier, we can send a single mail by project group.
The mail can be sent after the build of the latest project of the
group, I don't
How many beta do you want to do? I think 2 or 3 will be enough. But I'm agree
we can't resolve all beta-2 issues by Aug 15.
Emmanuel
Brett Porter a écrit :
Hi,
How do people feel about planning betas to fit into: Aug 15, Aug 29, Sep
12, Sep 26? (for releases, votes are the monday before)
I
