Hi Robert,
I would like to suggest we begin to move forward this week with
Sequoia 4.0. Here are the steps from my point of view:
1.) Tag the current contents of CVS HEAD (actually I would like to
create a branch for this) so that we can merge from it as needed later
on. At this point 3.0 can be discarded.
I guess we can create a branch at any time from the tag. But if you want
to branch right away, I don't see any issue.
2.) Merge 2.10 into CVS HEAD, fully replacing current contents of that
codeline.
3.) Branch immediately to create a 4.0-STABLE branch. We will move
our commercial development to this branch.
My understanding was that 4.0 would have some significant changes
especially with respect to configuration files and code cleanup. If you
want to provide a 4.0 with the current 2.10 branch then fine but we will
have to shift currently planned 4.0 features to another version number
to avoid confusion.
It will probably be an overkill to backport all HEAD modifications into
that stable branch and you will be probably better off creating a stable
branch including the new features once the code has stabilized in the
HEAD. Or maybe I just did not understand the intent of that branch.
Where would you see fixes such as SEQUOIA-980 go? In 2.10 branch, in
HEAD, in that stable branch?
4.) Implement CruiseControl builds for CVS HEAD and 4.0-STABLE.
5.) Start to implement the GPL test suite. The main problem with the
test suite is that it may take a little while to devise a good way to
start and stop controllers and set up databases. We are developing a
new management framework that may be useful for this.
Do you want the test suite to be in Sequoia or in a separate project?
Please let me know how this plan suits you.
That looks good to me. I'll start tomorrow by tagging the HEAD (so that
you can branch anytime), tag current 2.10 and overwrite the HEAD with
this tagged 2.10 version. This should get us covered and allow us to
rollback to the current state if needed.
Then I'll get things moving in the HEAD to start implementing the new
4.0 features (mostly code cleanup and 3.0 backports). I'll put
corresponding JIRA entries as I go.
Cheers,
manu
--
Emmanuel Cecchet - Research scientist
EPFL - LABOS/DSLAB - IN.N 317
Phone: +41-21-693-7558
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
