On 02/14/2013 12:21 PM, Stefan Sperling wrote:
> Philip indicated yesterday on IRC that all local move features
> he wanted to get to implemented for 1.8 now have code written.
> So now we're all waiting for the "local moves" yellow light on
> roadmap.html to turn green.
Awesome! Congratulations, Philip!
> I think now is the time where we should either start cutting 1.8 alpha
> releases from trunk, or branch 1.8 and then start issuing alpha releases
> from the branch. In either case we should ask the community to build
> binaries and ask our user base to help test them. (I don't expect alpha
> builds to be used in IDEs, however many users could try to update
> refactored working copies with the command line client and report back.
> This would also be a good test for the 'svn upgrade' code.)
>
> What do you all think?
As you said, every day we delay branching 1.8 is a day in which real
stabilizing work can get done without the cost of additional process. On
the other hand, that's also a day in which potentially de-stabilizing work
can get done without focused additional eyes and process to help catch the
problems until later. Seems like a toss-up to me.
The benefits that I see to branching now are that 1) it sends the signal to
our users that we're serious about actually releasing something, and 2) it
call us all into agreement about what that something will be as we mutually
agree to hold off on slipping in new features and resolve to stabilize and
ultimately ship what we have.
As such -- and assuming no one else has a feature waiting in the wings and
can make a compelling case for further delaying the release to accommodate
it -- I lean towards branching ASAP. And yes, +1 on delivering alphas as
soon as the branch is cut!
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Enterprise Cloud Development
Received on 2013-02-14 18:36:52 CET