Re: Releasing 1.6

On Thu, Aug 7, 2008 at 1:15 AM, Hyrum K. Wright
<hyrum_wright_at_mail.utexas.edu> wrote:
> [moving this to dev@ - apologies to those joining us mid-program]
>
>> On Thu, Aug 7, 2008 at 5:19 AM, Justin Erenkrantz <justin_at_erenkrantz.com>
>> wrote:
>>>
>>> Let's just create 1.6 *today* that has that feature and move on. So
>>> what that 1.5 didn't last long? Tough. If it's useful for
>>> CollabNet's paying customers, it's probably way more useful for our
>>> own users.
>>>
>>> There is no reason that we need to wait six months to get this feature
>>> in the hands of our users. We *can* be nimble and quick and put out
>>> 1.6 that just adds this one feature to 1.5 and move on.
>>>
>>> Now, that said, since CollabNet apparently really wants to see this
>>> feature out, I'd hope they'd volunteer to do the grunt RM work for 1.6
>>> since I'm sure Hyrum could use a rest. =) -- justin
>
> I've got the process down pat by now, no use somebody else having to come up
> to speed. :)
>
> In all honesty, if we've got the features, people don't mind the overhead,
> and we think that it will be a benefit to our users, I've no problem bumping
> up the release "schedule" to put out 1.6 sooner. And I'd be happy to RM it.

I am going to be offline today, so wanted to get at least one comment in.

I am not going to object if we want to release 1.6, but I'll point out
the feature we want to put in a branch is not even 100% complete (does
not support Windows or OSX yet). For our immediate needs, Unix is the
greatest pain. I think it is better to stick to a date for 1.6 as
planned and let the release train leave the station whether everything
people wanted is ready or not. If we branch now, for a lot of us that
put all our efforts into 1.5 stabilization, which lasted through the
1.5.1 release, we will not have had any time to even think about what
we wanted for 1.6, let alone code it.

Having a branch has virtually no impact on the project or its release
schedule, and as was stated privately, if no one has an interest in
the work, then we can just do the branch privately.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org