Bzr development stopped

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12-11-23 11:36 AM, Brendan Simon (eTRIX) wrote:
> On 23/11/12 11:00 PM, bazaar-request at lists.canonical.com wrote:
>> I'd be a lot more interested in seeing some bug-fixes installed
>> in the bzr-dev tree, to tell you the truth.
> 
> Isn't the answer a public fork ??  There are so many examples of
> this working (gcc => egcs=>gcc, OpenOffice.org => LibreOffice come
> to mind)

In my experience, forks usually happen when people are unhappy with
the leadership of a project.  (Not necessarily all people, and it may
be a cordial disagreement about direction or focus.)  Is that the
problem we've been having?  I haven't seen complaints that people
can't get their branches landed.

The project actually is designed to avoid single points of failure, so
that any 2 of the 33 approved reviewers can get a branch landed.

I think the problem is that there isn't as much development as we'd
like.  But a fork won't fix that, unless for some reason the
organization of the project is significantly hindering development.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCvrJkACgkQ0F+nu1YWqI1w+gCcCNLzfruNjys6wA+LBB0fXAud
ks4AnjN1M6TTzHkT3emZfm5CIJ0dDRZD
=62PM
-----END PGP SIGNATURE-----