Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # general >> Branching and testing strategy for 0.22

Copy link to this message
Re: Branching and testing strategy for 0.22
Would it be worthwhile to give branches unique, persistent names?
branch-0.22-qa1, branch-0.22-qa2, etc. Then problems in a later incarnation
of the QA branch could be regression-tested against the previous one.

Your point about automated builds is, however, noted. If this were git,
branch-0.22 could be a "floating" branch which is aliased with the most
recent qa branch name. Can we do something similar with svn?

We could remove all the QA branches when we officially cut for RC, if you're
concerned about clutter.

- Aaron

On Mon, Aug 23, 2010 at 3:19 PM, Owen O'Malley <[EMAIL PROTECTED]> wrote:

> I'd like to get started testing 0.22.
> I plan to start making mini-branches for QA. These branches will be
> snapshots that QA can use for testing with an expected lifetime of two weeks
> each. Only bug fixes that are blocking QA will be applied to the
> mini-branches and every two weeks, the base of the branch will be moved to
> the head of trunk. This will allow QA to test a point in time (possibly with
> required bug fixes) with requiring development to continually maintain two
> branches.
> To simplify automated builds, I'll call the branch the final name of
> "branch-0.22." But it will be rebased every two weeks or so.
> Are there any concerns?
> -- Owen