On 20 June 2013 12:32, Dirkjan Ochtman <dirk...@ochtman.nl> wrote: > On Thu, Jun 20, 2013 at 12:12 PM, Dave Cottlehuber <d...@jsonified.com> wrote: >> 1. a special 1.4.0 release that only support R15B+ is 1.3.1 + the >> changes that are only on master at the moment ( >> 1696-update-mochiweb-2-4-2 branch). > > "Special" releases sounds... not good.
Ditto, while it would be a proper release, it seems like it would be confusing for people. But a 1.3.1 + the R16B part would be a reasonable path towards a future 1.5 off master, which already has the >= R14B4 restriction. >> 2. providing homebrew with a .patch file that sits on top of 1.3.1 >> release, using a backport approach like macports does >> (1696-backport-mochiweb-2-4-2-1.3.x branch). > > That sure seems like a fine approach. This is currently my preference. >> 3. a stable 1.3.1+R16B-backport fork for homebrew with the same fix as >> #2.. I would be ok to maintain that until the next master-based >> release if required. >> (1696-backport-mochiweb-2-4-2-1.3.x branch again). This would be fine >> for homebrew team I think. > > I don't see how this is very different from #2. It's on a fork rather than a huge patch, easier to maintain and possibly more credible. >> Note that the 2.4.2 mochiweb is the *last* release that still supports >> < R15B, and it's already at 2.6.0. > > So can we do 2.6.0 mochiweb for 1.4.0? Not without ditching < R15B support, which I feel is a step too far for most distros. A+ Dave
