I'm working on a branch to use mochiweb 1.4.1 in trunk for a the 1.2 release.
b.
On Fri, Nov 26, 2010 at 3:06 PM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
> On Fri, Nov 26, 2010 at 15:57, Jan Lehnardt <jan@apache.org> wrote:
>> I wonder what the best solution here is. The problem with updating
>> to the latest Mochiweb right before a release is that subtle issues
>> don't have time surfacing in trunk. To ensure stable releases we
>> should be conservative with updates (modulo critical bug fixes of
>> course) or upstream libraries. How can we best ensure to keep them
>> up to date enough while not compromising a release's stability?
>
> The best solution IMO is if you can rely on upstream releases but
> specify which versions have been tested with. I.e. I'm happy to keep
> an older version of mochiweb around if you're not going to want to
> upgrade to the shiny new version right before a CouchDB release.
>
> Cheers,
>
> Dirkjan
>
|