Could the current tree be made more clear?

[Nicolas Sebrecht]

On Wed, Aug 08, 2012 at 06:08:50PM +0100, Kevin Lyda wrote:

> OK, I think I understand. To explain my issue, Homebrew on OS X
> supports two sources for each "formula" (i.e. package): a stable
> version and a "head" version.
> 
> The patch in August (
> https://github.com/OfflineIMAP/offlineimap/commit/6c85a4518d ) to fix
> Gmail support is only in the OfflineIMAP tree, so I would like to
> point the Homebrew offlineimap formula "head" version to that. As you
> later say...
> 
> > Though, the WIP/development for the next release will happen on
> > OfflineIMAP github organization. Main developers and contributors are
> > aware of this change and users don't not care much. Latters will be
> > advised in time.
> 
> ...so it would seem those willing to brave the bleeding edge, the
> OfflineIMAP tree is correct as the spaetz tree is pretty much in
> maintenance mode.
>
> The only reason I say all this is because the Homebrew maintainer is
> understandably cautious and is concerned that the right tree is being
> chosen for head.
> 
> https://github.com/mxcl/homebrew/pull/14046
> 
> If you can confirm or correct my understanding,

You're right.

Notice that this fix was merged in master. So, we are in the situation
where a patch is considered to be safe enough to be widely spread to
the users without beeing included in a release, for now.

For those who want to "brave the bleeding edge", the right place is the
next branch in the OfflineIMAP organization repository. Though, the
Gmail patch is not in the next branch, currently. This is wrong and an
error from us. As said, we are in a transition with a young team.

I guess you'd prefer to wait some time before pointing your "head"
formula to the next branch which I expect to become the true head in the
future.

>                                                 I've already pointed
> him at this thread so any reply should be visible to him. The patch
> does work; my Gmail backups now work.

Yes, we had other users reporting that the patch is fixing the issue.
Thanks for the feedback.

-- 
Nicolas Sebrecht