+1 not sure on release overhead but release often is desirable from
where I sit. Nothing wrong with triggering on a major functional
addition.
Bob
On 2010-04-07, at 2:08 AM, Jacopo Cappellato <jacopo.cappell...@hotwaxmedia.com
> wrote:
I would suggest to:
1) release 10.04 before the merge is done
2) merge the code to the trunk, switch to it, fix any possible issue
3) do another release (10.06?)
I know this is not inline with what we currently think a release
should be, but this is very inline with what the ASF practices and
so I will continue to insist with the release-often practice. :-)
Jacopo
On Apr 4, 2010, at 8:21 PM, Adrian Crum wrote:
I would like to start bringing parts of the
executioncontext20091231 branch into the trunk before we create the
next release branch. The implementation of the new security design
is not finished, but it will be disabled - so everything will still
work the same.
My goal is to allow users of the 10.x release to plan for the
forthcoming changes, and maybe have the conversion to the new
design completed by the release that follows 10.x.
I will wait a few days, and if there are no objections I will begin
merging the design into the trunk.
-Adrian
