Hi Oleg I have a question about how you usually handle release versioning in HttpComponents.
More specifically: - how do you decide when it is worth cutting a new maintenance release? - how do you decide which fixes make it into the next release and which ones should wait? - do you usually batch fixes until there is enough value, or do you cut a release as soon as there is one sufficiently important fix? I am trying to understand the practical release discipline you follow for the project. Arturo On Thu, Apr 23, 2026 at 3:30 PM Oleg Kalnichevski <[email protected]> wrote: > On Mon, 2026-04-20 at 12:52 +0200, Arturo Bernal wrote: > > Hi Oleg > > > > Sure, I can do that. > > > > I will take care of the remaining 5.6.1 release steps from step 8 > > onward > > and will follow the guide and one of the recent release announcements > > as a > > template. > > > > I will let you know if I run into any issues. > > > > > > Arturo > > > > Hi Arturo > > Many thanks for finalizing the 5.6.1 release. Now, if you want to > proceed with the idea of being a RM, please take a look at the HC > release tools and the release guide [1] that I have developed over the > years to help myself to deal with the most annoying aspects of ASF > release process. > > Mind you, I built it for myself, based on my personal preferences. It > suits primarily my habits of building releases. I did try the Maven > release plugin several times but could not make it do what I thought > was required by the ASF release guidelines. > > You are welcome to try out a different release approach but then you > will be on your own. > > Oleg > > [1] https://github.com/ok2c/httpcomponents-release-tools/wiki > > > > > > On Sun, Apr 19, 2026 at 11:19 AM Oleg Kalnichevski <[email protected]> > > wrote: > > > > > Hi Arturo > > > > > > If I understand it correctly you have expressed interest in acting > > > as a > > > release manager for some of HC releases. If this is the case, I > > > need to > > > warn you upfront, this is a very tedious task and a deeply > > > undignifying > > > role. > > > > > > This is what you can do as a small warm-up exercise. > > > > > > I have just prepared the release artifacts for version 5.6.1 of > > > HttpClient. What still remains to be done is the project website > > > update, release announcement and some post release tasks. > > > > > > Would you be interested in taking over from mere here? If so, > > > please > > > follow this release guide starting here [1] from step 8 (Checkout > > > HC > > > Website Project) > > > > > > Use one of the latest HttpClient bug fix release announcements as a > > > template [2]. If at any point you need help, just let me know. > > > > > > Oleg > > > > > > [1] > > > > https://github.com/ok2c/httpcomponents-release-tools/wiki/WebsiteUpdate > > > [2] > > > https://lists.apache.org/thread/ws36033hfzshh8jv6tgcgo1fcw3qb3xm > > > > > > ------------------------------------------------------------------- > > > -- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
