You can apply the "Fabio Rule" ;-) there: "send me a patch".
The compromise from the committers does not need to be "we will fix
everything in both branches for free and send you a postcard to say we're
sorry for the bug", but "we will accept patches for the 3.x branch".
Remember the patches for _bugs_ will be identical for both branches in most
cases (3.x does not need to add new features once released)
Diego
On Thu, Oct 14, 2010 at 10:50, Julian Maughan <[email protected]>wrote:
> We can't even get (most) contributors to write patches for one code
> line, nevermind for two.
>
> On Oct 14, 9:49 pm, Diego Mijelshon <[email protected]> wrote:
> > So far, the consensus seems to be in the compromise solution: keep the
> 3.x
> > branch targeting .NET 3.5 and 4.x targeting .NET 4.0.
> > That does imply a bit of additional work (backporting patches), but it
> keeps
> > things simple enough. A guideline for submitted patches should be
> > established, so the contributors do the work themselves when fixing bugs,
> > instead of deferring everything to the committers.
> > We could then establish a threshold of .NET 4.0 adoption that will result
> in
> > killing the 3.x branch, like 90% (I have no idea how to measure it, but
> I'm
> > wearing my free brainstorming hat at the moment. Maybe downloads/month)
> >
> > Diego
>
