Stefano Bagnara wrote:
> Imho there are many features that should be changed before adding them
> to the final 2.3.0 release.
Let's add them to 2.4, 2.5, whatever. I feel a keen need for a stable (as
in reliable) release, and then we can make changes.
> I think that the current trunk is almost ready for an alpha 2 release.
> We could schedule the next release for the end of the next week
> can you take care of the release? (we should remember to tag the
> code we release, this time)
Yes, to both. I should have time to do that on Friday afternoon, baring any
unforeseen complications when I see the oral surgeon on Friday morning (just
a follow-up). We'll want to vote first, of course, but we have from now
until Thursday to do some sanity checking, clean up any minor nits, and
vote.
> About the stability issue I think we talked about this in past: if we
> want to feature freeze we should branch.
As above, when I say stable, I don't mean that the features are frozen. I
mean that the code base is reliable and solid. We have made enough core
changes to key areas that I have not had that comfort level. The need to
revert some changes seems to corroborate my feeling. But I am quite pleased
that we now have so much better testing that we can more rapidly validate
changes.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
