accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1438) Move MiniAccumuloCluster & Runner packaging to it's own module.
Date Tue, 21 May 2013 14:33:17 GMT


Keith Turner commented on ACCUMULO-1438:

bq.  In the future, if I have a change to 1.5 and 1.6, should I wait to do the merge into
1.6? I'm still not completely clear on the plan there and I've noticed many others doing the
merge from 1.5 into trunk.

Its in some mailing list thread.  We decided to hold off on major moves in trunk until after
1.5.1.  The expectation is that we will find a lot of bugs that need to need to be fixed in
1.5 and merged forward.   The plan is to apply bug fixes in 1.5 branch and merge them forward
to trunk.  We had a feature freeze on jan 25 for 1.5, but now its almost june and we still
have not released 1.5.  IMO we (myself included) need more discipline about making only necessary
changes to 1.5.  The goal should be to release 1.5, not continually improve it.
> Move MiniAccumuloCluster & Runner packaging to it's own module.
> ---------------------------------------------------------------
>                 Key: ACCUMULO-1438
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: mini
>            Reporter: Corey J. Nolet
>            Assignee: Corey J. Nolet
>            Priority: Minor
>             Fix For: 1.6.0, 1.4.4, 1.5.1
> Create a new mini module for the all the classes currently in

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message