Stefano Bagnara wrote:
I don't agree: imho we already have a stable release out: 2.2.0.
of course. i correct myself: we should focus on putting out official
stable releases on a regular basis.
We'll get feedback and contributions if we add features people need,
otherwise people will switch to different mail servers.
and the only way to get people to use these features are final releases.
what turns people away is a project seemingly dead from that perspective.
I would prefer to have a few more alpha cycle and possibly introduce new
features before 2.3.0 but I'll not be -1 on putting out a release on the
current feature-set.
If we want to feature freeze here for 2.3.0 then I think we should
create a branch so that we can also keep going on with new code.
About "release dates" I don't think we can decide a release date: no one
here work on James as a full time "priority" job, so we can release when
things are ready.
If you feel the core was better 4 months ago we can even branch the code
from 4 months ago and release from there, but please don't slow down the
*few* developing efforts out there.
you are doing a great job applying patches, writing large chunks of code
yourself, supporting users. (thank you very much, by the way!) beyond
that, i have the feeling that development is slowed down more than
accelerated by not having an official release out for month.
there is no need for going back 4 months, AFAICT.
of course we should not release if not ready! but release preparation
needs some extra efforts which need to be focused into a shorter
timespan. 8 weeks until ApacheCon seem realistic to me. it's a goal not
a burden.
Bernd
Stefano
Bernd Fondermann wrote:
Noel J. Bergman:
But if we don't adopt some
discipline on what changes we do, we will never get a release out. I
was
hoping to do a release many months ago, but a flurry of changes to
the core
wiped out all chance of that happening. Now, with a lot of work from
Bernd
and Stefano (and backing out some changes), the core is starting to feel
stable again, and we can look forward to a release. But not if we keep
changing things.
Agreed.
As an Apache project we should put more focus one the user community
in terms of putting out stable releases. We would get back feedback
and contributions.
Why not aim for ApacheCon Europe 06 as a release date for 2.3?
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
