On Wed, 8 Jan 2014, Steve Holme wrote:

> With both of these issues it might be worth bringing the next release
> forward even more (to say the 22nd - two weeks and implement an immediate
> feature freeze).

If there are Linux/BSD distributions that ship 7.34.0 they can fix their
versions immediately with the commit we have. That's kind of what many of them
already do when users file bugs in their trackers.

I'm getting the feeling lately that we have more bugs we should fix before we
release rather than rush to get a new release out that still have a bunch of
serious-enough problems left that then more or less would create another
release we should fix quickly.

This said, I don't want to dismiss those who are in pain due to bugs we
already have fixed...

So... [fighting back and forth with all this in my head]

I suggest we take *3* weeks from now on to fix bugs, and we stop features
immediately. That'll bring out a new release on January 29th instead. That's
basically what you said, just extending the bug fixing a little due to the
amount we already have in progress here on the list.

Anyone else want to voice their views?

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html