Re: [sup-talk] slowly catching up

[William Morgan <wmorgan-sup@masanjin.net>]

Reformatted excerpts from Rich Lane's message of 2009-11-05:
> Rather than committing directly to mainline, I'd rather keep a public
> repo that I apply incoming patches to and that William can pull from.
> This way I could do a lot of the first-line work and he could get a
> more stable flow of patches to make releases from.

That sounds good to me. I'm happy to add you to the gitorious repo, of
course, but this is definitely more in line with the git lifestyle.

We have a couple options on how to organize this, but I think the best
would be for you to maintain one or more branches that I treat as
integration branches, and periodically merge into master whenever you
tell me they're ready. That's a very minimal amount of work for me. I
can just merge it and forget it.

The only things to be careful about in such a setup are not merging next
into your branch (merging master in is fine and good to keep up with
other stable changes), and not rebasing. And we will have to coordinate
on releases, if nothing else so that I can make reasonable changelogs
and release notes.

How does that sound?

> I can imagine that a lot of William's work caused by being the central
> repository is reviewing the patches that get sent in. I'd like for
> anyone who feels interested to read through incoming patches and comment
> on them. I don't want any strict processes just yet, but I'd like to see
> a couple of positive reviews (depending on the complexity of the patch,
> etc) before things get merged.

That would be great. Or heck, even an "I applied it and it works for
me" is useful.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk