Yup, it's Hard, and I'll note that branching too early could reduce
testing, much like keeping the stuff on the frickin' branch for so
long was horribly costly.
When we did 1.0, we stabilized on the trunk, not on a branch. You
branch to allow other dev to occur on the trunk. Or when you're in
*the* final stretch. Thus, the idea of branching on a date is
somewhat, inherently wrong. It is hard to know *today* what sort of
shape the trunk will be in.
IMO, the concept of a date is corporate-speak. The proper mechanism is
a status file of open items, along with the open issues (oh, and the
idea of an issue for all work items is also corporate). Then people
focus on the file/issues and work that to empty. *then* branch.
Note that posting a weekly summary of 1.5 issues, along with that
status file is a great way to "surface" the info so that all devs can
see what is left. If that email can also cover progress, then devs can
also see/feel like stuff is happening.
This is more akin to agile dev than classic feature&date product
delivery, which usually fails anyway.
Cheers,
-g
On Aug 31, 2007, at 10:33 AM, "Hyrum K. Wright" <hyrum_wright@mail.utexas.edu
> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Mark Phippard wrote:
>> On 8/30/07, Karl Fogel <kfogel@red-bean.com> wrote:
>>> "Mark Phippard" <markphip@gmail.com> writes:
>>>> I propose October 12th as that date, which gives us 6 full weeks of
>>>> development time, and if we get the pieces in place quickly for a
>>>> release candidate, gives us enough time to get the GA out before
>>>> the
>>>> end of the year. Personally, I think we should shoot for end of
>>>> November, so that X-Mas and holiday season does not get in the way.
>>> +1
>>>
>>> I think it's time to set a date and mean it. We've got to get this
>>> thing out before the end of the year!
>>
>> Thanks for responding. I thought this would have got more responses
>> than it has.
>>
>> Hyrum, Erik, Vlad, Ivan, Eric, Blair ???
>>
>> You've all contributed a lot already and recently. You must have
>> opinions.
>
> I *always* have opinions. :)
>
> Personally, I still have a few tweaks to make to the 'log -g' and
> 'blame
> - -g' stuff, and I think I can have that done in the next couple of
> weeks. There are also a couple of known issues (they are in the issue
> tracker, iirc), and I plan to look at those also. I'm going to be
> busy
> with academic pursuits for the next few months, so my time to work on
> Subversion may be fairly limited.
>
> I think branching 1.5 on October 12th would be good goal. But, I also
> think that the stabilization period is going to take a while. Merge
> tracking is Hard, and I just have this sneaky suspicion that we're
> going
> to discover some interesting bugs with the increased testing when we
> start releasing RCs. There's nothing wrong with that (I prefer known
> bugs to unknown ones), but it's something we should remember. There's
> just a lot in this release.
>
> - -Hyrum
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFG2FC4CwOubk4kUXwRAv4JAJ9aaYx3PFF6O+fAe3WvDnToUd/kNwCfYCLc
> Gse/NOOsAOg9L07Fiwoq5m4=
> =OBb3
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 31 20:48:17 2007