On Jul 5, 2009, at 8:58 AM, James Turnbull wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Brice Figureau wrote:
>>
>> Agreed, 0.25 seems to be in good shape. As soon as the more important
>> bugs are fixed (I'm still worried by 2296), then I think we could
>> have a
>> rc1.
>
> Can we decide what remaining new features, if any, are going in then
> for rc1? Brice's regex code? The Windows code? Others? Can we
> make a quick list and if there aren't tickets then please add them
> so we can assign them to an appropriate release.
I think the Windows code is ready; I'd just like Paul's final sign-off
then at least one person's indication that they've successfully used
it. If it's ready, it should be included.
I think everything else is already in the list, but some customer work
of mine may end up there. I should know within a day or two.
>
>>> As to later releases, I really think we need to switch to something
>>> like the kernel uses, where the 'next' branch is recreated
>>> periodically from the code that is accepted for release. This
>>> puts a
>>> higher burden on James as the release maintainer (although not a
>>> ton,
>>> since it could pretty easily be turned into a straightforward rake
>>> task), but it makes it trivial to add and remove code chunks from
>>> the
>>> branch.
>
> Doesn't bother me as long as someone comes up with some rules and
> automation around this.
Something like:
* Maintain a file of all of the branches you're merging in, in the
order they'll be merged, with the repository included in the file
* Have a script that:
* removes the 'next' branch
* makes a new 'next' branch based on current 'master' or most recent
release
* pulls each branch
* merges each branch into a new 'next' branch
IMO, the only hard part is the maintenance of that file. On the one
hand, you'd want to version control that file, on the other hand, of
course you can't because you're constantly recreating the branch. I'd
probably add a version of that file to the newly-created branch,
however, so everyone can see exactly what's included.
Maybe the file itself should be available publicly or something? I
dunno.
Seem simple enough? Want me to make that script for you?
--
Zeilinger's Fundamental Law:
There is no Fundamental Law.
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
