Then, why not simply report the 10.04 to 10.06 (or 10.05), like Ubuntu did for
6.06 (which should have been 6.04 and have been
rather reported for 2 months)
I see 3 reasons:
* Confusion, I'm quite sure we will have to answer much users who will ask
about the differences. This is not a big issue, but I
think it will increase users confusion which is never good. People and even more markets
like stability and "certainty" (I'd say
mental certainty, as it's not real certainty, but what is reality, science?)
* Thanks to Ean's recent trends post
http://www.google.com/trends?q=ofbiz&ctab=0&geo=all&date=all&sort=0 I wonder if
the most
important marketing thing for us (not for the ASF) is not releasing. So if we
make 2 relases in 2 months, the effect is watered down
and as I said confusion increase.
* We would like to include the layered lookups. Apart 2 minor issues they work
well but when a calendar is called (it's hidden
behind). The calendar issue is maybe not that big because Sascha already solved
a such issue for lookups called from a lookup. But
there is also another issue I found this weekend. We would want to make things
as simple as possible for users. In order to do so,
we decided that the layer would be the default. There is currently an issue
with this also. I tracked it yesterday evening but did
not have enough time to finish it yet.
The 3rd reasons is maybe not a delay problem, and I also like the release often
strategy. It's only that I get some Schizophrenia:
as a developper I prefer the Apache way (release often strategy), but as a
consultant I prefer the Ubuntu way. It's all about
marketing, I let you think about that :o)
Jacques
From: "Jacopo Cappellato" <jacopo.cappell...@hotwaxmedia.com>
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
