You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Norman Maurer <no...@googlemail.com> on 2011/05/13 11:25:08 UTC
James Server Release
Hi there,
How does others feel about branch current trunk and release it as
first beta of James Server 3.0.0 ?
I think we have fixed everything needed for 3.0.0 and just need to be
sure we stabilize it. New development would still happen in trunk and
only get backported if it feels save enough for upcoming 3.0.0
Bye,
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: James Server Release
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Mon, May 16, 2011 at 10:42 AM, Eric Charles <er...@apache.org> wrote:
> +1 for beta1.
>
> I have no strong idea for a branch for this (is someone ready to backport
> bug corrections?), maybe a tag ?
If we're going to ship a beta then I hope we'll push for a 3.0.0.
quickly based on that code base on a release branch. In this case,
maybe we should use review then commit on the branch and port only
selected fixes from trunk.
I hope we'll still look to release regular milestones based on trunk
to allow early adopters to trial new features.
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: James Server Release
Posted by Eric Charles <er...@apache.org>.
+1 for beta1.
I have no strong idea for a branch for this (is someone ready to
backport bug corrections?), maybe a tag ?
Tks,
Eric
On 15/05/2011 20:03, Robert Burrell Donkin wrote:
> On Fri, May 13, 2011 at 12:40 PM, Norman Maurer
> <no...@googlemail.com> wrote:
>> The idea with the branch was just to make sure we don't introduce bugs
>> while add new features...
>>
>> But I'm not strong on this. I'm just strong on call the next release beta
>
> +1
>
> I think a promotion style release process would be a good fit for
> James. So, I'd like to see a branch ideally just used for version
> changes (milestone->beta->full).
>
> I would like to continue cutting milestones from trunk to allow easy
> access to new features.
>
> Robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: James Server Release
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Fri, May 13, 2011 at 12:40 PM, Norman Maurer
<no...@googlemail.com> wrote:
> The idea with the branch was just to make sure we don't introduce bugs
> while add new features...
>
> But I'm not strong on this. I'm just strong on call the next release beta
+1
I think a promotion style release process would be a good fit for
James. So, I'd like to see a branch ideally just used for version
changes (milestone->beta->full).
I would like to continue cutting milestones from trunk to allow easy
access to new features.
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: James Server Release
Posted by Norman Maurer <no...@googlemail.com>.
The idea with the branch was just to make sure we don't introduce bugs
while add new features...
But I'm not strong on this. I'm just strong on call the next release beta
Bye
Norman
2011/5/13, Stefano Bagnara <ap...@bago.org>:
> 2011/5/13 Norman Maurer <no...@googlemail.com>:
>> Hi there,
>>
>> How does others feel about branch current trunk and release it as
>> first beta of James Server 3.0.0 ?
>>
>> I think we have fixed everything needed for 3.0.0 and just need to be
>> sure we stabilize it. New development would still happen in trunk and
>> only get backported if it feels save enough for upcoming 3.0.0
>
> I don't have good knowledge of the current trunk status, but maybe it
> is a better plan if changes still happen in trunk and we keep
> releasing betas from trunk. I would branch only for RC.
>
> That said, this is only an idea.. the most important thing is to have
> the beta released.. if it comes from a branch or from trunk is a
> detail!
>
> Stefano
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: James Server Release
Posted by Stefano Bagnara <ap...@bago.org>.
2011/5/13 Norman Maurer <no...@googlemail.com>:
> Hi there,
>
> How does others feel about branch current trunk and release it as
> first beta of James Server 3.0.0 ?
>
> I think we have fixed everything needed for 3.0.0 and just need to be
> sure we stabilize it. New development would still happen in trunk and
> only get backported if it feels save enough for upcoming 3.0.0
I don't have good knowledge of the current trunk status, but maybe it
is a better plan if changes still happen in trunk and we keep
releasing betas from trunk. I would branch only for RC.
That said, this is only an idea.. the most important thing is to have
the beta released.. if it comes from a branch or from trunk is a
detail!
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org