4) Cut the special purpose loose and let interested parties set up
sub-projects to work on them and release versions of individual special
purpose projects as required to support new releases of the trunk.
Focus on getting the core and framework into a stable well documented
product with:
- a clear roadmap,
- frequent releases of production quality code that most people are
running in production
- a clear documented process for adding new special purpose modules or
user customizations
and work towards a community that is not running private forks of the
trunk because the releases are not usable in production and do not get
new bug fix releases in a suitable timeframe.
The support of special purpose modules will be up to the community that
wants to use them.
Ron
On 07/01/2015 5:13 AM, Jacques Le Roux wrote:
I think we need to make a decision about this. Let me summarize the
alternatives I proposed:
1. Put the state of the specialpurpose components in trunk when the
branch was freezed r1505933 and then add the bug fixes since
https://issues.apache.org/jira/issues/?filter=12329808
2. let the future R13.07 releases as is the R13.07.01, ie without the
specialpurpose components but ecommerce.
3. Put the EntityQuery stuff in the specialpurpose components took at
the revision I said, and put back the relevant components (to be
defined, who cares about ebay and google for instance?)
The 1st alternative is obviously the more professional solution but
it's heavy. The 3rd alternative is easier and safer (less changes) but
it break the rules of no new features in released packages. Nobody
like the 2nd alternative it seems.
Jacques
Le 15/12/2014 09:37, Jacques Le Roux a écrit :
The last possibility is to put the EntityQuery stuff in the
specialpurpose components took at the revision I said, I guess it's
the only blocking new feature, small and safe exception...
Jacques
Le 15/12/2014 06:36, Jacques Le Roux a écrit :
You mean a new branch as a suggested, or?
Jacques
Le 15/12/2014 02:01, Pierre Smits a écrit :
We can cut a release tomorrow including all that was left out of
the r13.x
branch. And have a release available to the public within a week.
There are
no issues in JIRA that could block it.
And after that we can work on getting consensus on what stays in
and what
doesn't.
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Sat, Dec 13, 2014 at 3:53 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
I think a bit about this today. There is one alternative. We could
decide
to let the future R13.07 releases as is the R13.07.01, ie without the
specialpurpose components but ecommerce. And we would freeze a new
branch
where we would keep some of the specialpurpose components
disabled, but not
all, as Jacopo suggested.
Advantages: it's easy to do, we have not to collect and apply the
specialpurpose bug fixes in trunk since 12329808. The R13.07
releases will
be consistent, no need to explain to our users what happened between
R13.07.01 and R13.07.02
Drawbacks: when we will deliver our next freezed branch releases
our users
could ask why now some of the specialpurpose components are back.
But this
is easy to explain. Of course the R13.07 releases will always miss
the
specialpurpose components but ecommerce.
We need to face it, removing the specialpurpose components but
ecommerce
was not a good idea. But putting them back in is a lot of work. So
if our
users really want to use the R13.07 releases will some specific the
specialpurpose components it would be their own responsibility.
Opinions?
Jacques
Le 30/11/2014 19:02, gil portenseigne a écrit :
Hi,
I think it's the good way to do (not trunk, but branch state) !
Gil
Le 30/11/2014 16:56, Jacques Le Roux a écrit :
Hi,
Initially I wanted to write a complete email with several concerned
points. I changed my mind and prefer to discuss each point in
separated
emails, though in the same thread. It will be easier.
The 1st point which comes to my mind is what to exactly put back in
release branch.
We can't put the current trunk HEAD state, because we will face
the rule
which says that we shall not add new features in release
branches. And
obviously there are some since we freezed this branch and
moreover few (at
least EntityQuery) are blockers. So I guess we should put the
state of the
specialpurpose components in trunk when the branch was freezed
http://svn.apache.org/viewvc?view=revision&revision=r1505933 and
then
add the bug fixes since https://issues.apache.org/
jira/issues/?filter=12329808
We cannot rely only on Jira, at least it's a start.
Jacques
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
