Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Re: Regressions and a patch release proposal
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Dan Fandrich via curl-library <curl-library_at_lists.haxx.se>
Date: Thu, 7 Nov 2024 18:10:43 -0800
On Fri, Nov 08, 2024 at 01:00:36AM +0100, Daniel Stenberg via curl-library wrote:
> After the 8.11.0 release earlier this week several regressions have been reported. Some of them
> rather annoying for the users experiencing them.
>
> In normal circumstances, I would have voted for a patch release next week. This time however, I
> personally am going to be traveling for the most part of the coming three weeks which makes it
> inconvenient to make a release in this period.
>
> I propose we cut the release cycle in half this time and do a patch release on December 11,
> without opening the feature window at all. As a sort of compromize. This gives us time to focus on
> getting things to stablize and I can do the release properly once I am back home from my travels.
It's been a while since I remember so many different people chiming in with
problems with a release, so I would prefer to see a patch release sooner rather
than later. How about a patch release Friday (tomorrow/today) instead? That
will have given the big fixes 24 hours to bake in git so there shouldn't be too
many surprises. It's not an ideal situation w.r.t. timing, but IMHO it's better
than letting the current release live for another 5 weeks.
Dan
Date: Thu, 7 Nov 2024 18:10:43 -0800
On Fri, Nov 08, 2024 at 01:00:36AM +0100, Daniel Stenberg via curl-library wrote:
> After the 8.11.0 release earlier this week several regressions have been reported. Some of them
> rather annoying for the users experiencing them.
>
> In normal circumstances, I would have voted for a patch release next week. This time however, I
> personally am going to be traveling for the most part of the coming three weeks which makes it
> inconvenient to make a release in this period.
>
> I propose we cut the release cycle in half this time and do a patch release on December 11,
> without opening the feature window at all. As a sort of compromize. This gives us time to focus on
> getting things to stablize and I can do the release properly once I am back home from my travels.
It's been a while since I remember so many different people chiming in with
problems with a release, so I would prefer to see a patch release sooner rather
than later. How about a patch release Friday (tomorrow/today) instead? That
will have given the big fixes 24 hours to bake in git so there shouldn't be too
many surprises. It's not an ideal situation w.r.t. timing, but IMHO it's better
than letting the current release live for another 5 weeks.
Dan
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-11-08