Re: [log4cxx] Next steps / release?
The release has been formally completed at this point; mirrors have their copy of the official tar.gz file. -Robert Middleton On Fri, Jan 6, 2023 at 7:36 AM Tobias Frost wrote: > > On Mon, Jan 02, 2023 at 10:45:37PM -0500, Robert Middleton wrote: > > Awesome! Thanks for the packaging work that you do. Once we get it > > voted on you should have a proper release. > > FYI, release-team acked the transistion and we've got the go to do the > transition. So once the proper release is available, I now could upload > it to unstable for the final steps needed to complete the transition, > but I prefer to do this with the final release. > > Do you have an ETA when the release will become available? (It's still > a bit time critical…) > > -- > Cheers, > tobi > > -- > tobi > > > -Robert Middleton > > > > On Mon, Jan 2, 2023 at 2:52 PM Tobias Frost wrote: > > > > > > Update: > > > > > > FTP masters have been very quick and approved the package, so the > > > snapshot is > > > already in experimental. [1] > > > > > > I've also rebuilt all reverse depdencies successfully and asked the > > > release team > > > to approve the transition. [2] > > > > > > [1] https://packages.debian.org/source/experimental/log4cxx > > > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027746 > > > > > > Cheers, > > > -- > > > tobi > > > > > > On Sat, Dec 31, 2022 at 10:52:43AM +0100, Tobias Frost wrote: > > > > On Thu, Dec 29, 2022 at 05:21:34PM -0500, Robert Middleton wrote: > > > > > > > > > The last time we talked about this Tobias Frost said that the > > > > > soft-freeze for Debian is the 12th of January[1], so after that point > > > > > an updated library wouldn't make it into Debian. I would like to get > > > > > this version into Debian if possible(as that is the distribution I > > > > > use), but that depends on Tobias' availability. > > > > > > > > To have a chance to make that happen, I've started the transistion > > > > workflow [1]. > > > > TBH, due to the soft freeze is in less than two weeks, changes are high > > > > that > > > > we won't make it, but at least I want to have tried it. > > > > > > > > The first step is "Upload your new version to experimental (and have it > > > > clear > > > > NEW)", which is what I've just have done: I've uploaded a snapshot > > > > (commit > > > > cbd23ff1) to debian experimental. This needs now to be approved by the > > > > (Debian) > > > > ftp masters, which is (usually) for such a change quick, but if they > > > > aren't or > > > > not happy for any reason, this can spoil the game. [2] > > > > > > > > Only after that, I can ask for a transition slot from the release team. > > > > If they are > > > > not happy with a transition that late (IOW that short before the > > > > freeze), well > > > > that will be something I have to accept and that will mean 1.0.0 not in > > > > bookworm. > > > > > > > > In parallel I'll see if the reverse dependencies are still building > > > > with the > > > > new version, as for any breakage I will need to have patches available… > > > > > > > > So, let's see how it works out. > > > > > > > > [1] if you want to know the details: > > > > https://wiki.debian.org/Teams/ReleaseTeam/Transitions > > > > [2] It needs to go through NEW due to the binary package rename, due to > > > > the SONAME bump. > > > > > > > > -- > > > > tobi
Re: [VOTE] Release log4cxx 1.0.0
Adding my +1. With that, the release passes with 3 binding votes from me, Volkan, Remko, and two votes from Stephen and Thorsten. Thanks to all for your work; I will send out the release notification shortly. -Robert Middleton On Fri, Jan 6, 2023 at 9:07 AM Volkan Yazıcı wrote: > > +1 > > Shared website link contains a typo, correct one: > https://logging.staged.apache.org/log4cxx/next_stable/ > > On Sun, Jan 1, 2023 at 7:06 PM Robert Middleton > wrote: > > > This is a vote to release log4cxx 1.0.0 > > > > Please download, test, and cast your votes on the log4j developers list. > > [] +1, release the artifacts > > [] -1, don't release because... > > > > This vote will remain open for 72 hours(or more if required). > > > > All votes are welcome and we encourage everyone to test the release, > > but only Logging PMC votes are “officially” counted. As always, at > > least 3 +1 votes and more positive than negative votes are required. > > > > Changes can be found on JIRA: > > https://issues.apache.org/jira/projects/LOGCXX/versions/12351043 > > > > Tag: > > For a new copy do "git clone > > https://github.com/apache/logging-log4cxx.git; and then "git checkout > > tags/v1.0.0-RC1" > > For an existing working copy, do "git pull" and then "git checkout > > tags/v1.0.0-RC1" > > > > Web site: https://logging.staged.apache.org/log4cxx/next_stable/ > > > > Distribution archives: > > https://dist.apache.org/repos/dist/dev/logging/log4cxx/ > > > > Building directions are on the website(under 'Development'). Note > > that APR is required to build(as well as boost if your compiler does > > not support C++17). > > > > -Robert Middleton > >
Re: [VOTE] Release log4cxx 1.0.0
+1 Shared website link contains a typo, correct one: https://logging.staged.apache.org/log4cxx/next_stable/ On Sun, Jan 1, 2023 at 7:06 PM Robert Middleton wrote: > This is a vote to release log4cxx 1.0.0 > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts > [] -1, don't release because... > > This vote will remain open for 72 hours(or more if required). > > All votes are welcome and we encourage everyone to test the release, > but only Logging PMC votes are “officially” counted. As always, at > least 3 +1 votes and more positive than negative votes are required. > > Changes can be found on JIRA: > https://issues.apache.org/jira/projects/LOGCXX/versions/12351043 > > Tag: > For a new copy do "git clone > https://github.com/apache/logging-log4cxx.git; and then "git checkout > tags/v1.0.0-RC1" > For an existing working copy, do "git pull" and then "git checkout > tags/v1.0.0-RC1" > > Web site: https://logging.staged.apache.org/log4cxx/next_stable/ > > Distribution archives: > https://dist.apache.org/repos/dist/dev/logging/log4cxx/ > > Building directions are on the website(under 'Development'). Note > that APR is required to build(as well as boost if your compiler does > not support C++17). > > -Robert Middleton >
Re: [log4cxx] Next steps / release?
On Mon, Jan 02, 2023 at 10:45:37PM -0500, Robert Middleton wrote: > Awesome! Thanks for the packaging work that you do. Once we get it > voted on you should have a proper release. FYI, release-team acked the transistion and we've got the go to do the transition. So once the proper release is available, I now could upload it to unstable for the final steps needed to complete the transition, but I prefer to do this with the final release. Do you have an ETA when the release will become available? (It's still a bit time critical…) -- Cheers, tobi -- tobi > -Robert Middleton > > On Mon, Jan 2, 2023 at 2:52 PM Tobias Frost wrote: > > > > Update: > > > > FTP masters have been very quick and approved the package, so the snapshot > > is > > already in experimental. [1] > > > > I've also rebuilt all reverse depdencies successfully and asked the release > > team > > to approve the transition. [2] > > > > [1] https://packages.debian.org/source/experimental/log4cxx > > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027746 > > > > Cheers, > > -- > > tobi > > > > On Sat, Dec 31, 2022 at 10:52:43AM +0100, Tobias Frost wrote: > > > On Thu, Dec 29, 2022 at 05:21:34PM -0500, Robert Middleton wrote: > > > > > > > The last time we talked about this Tobias Frost said that the > > > > soft-freeze for Debian is the 12th of January[1], so after that point > > > > an updated library wouldn't make it into Debian. I would like to get > > > > this version into Debian if possible(as that is the distribution I > > > > use), but that depends on Tobias' availability. > > > > > > To have a chance to make that happen, I've started the transistion > > > workflow [1]. > > > TBH, due to the soft freeze is in less than two weeks, changes are high > > > that > > > we won't make it, but at least I want to have tried it. > > > > > > The first step is "Upload your new version to experimental (and have it > > > clear > > > NEW)", which is what I've just have done: I've uploaded a snapshot (commit > > > cbd23ff1) to debian experimental. This needs now to be approved by the > > > (Debian) > > > ftp masters, which is (usually) for such a change quick, but if they > > > aren't or > > > not happy for any reason, this can spoil the game. [2] > > > > > > Only after that, I can ask for a transition slot from the release team. > > > If they are > > > not happy with a transition that late (IOW that short before the freeze), > > > well > > > that will be something I have to accept and that will mean 1.0.0 not in > > > bookworm. > > > > > > In parallel I'll see if the reverse dependencies are still building with > > > the > > > new version, as for any breakage I will need to have patches available… > > > > > > So, let's see how it works out. > > > > > > [1] if you want to know the details: > > > https://wiki.debian.org/Teams/ReleaseTeam/Transitions > > > [2] It needs to go through NEW due to the binary package rename, due to > > > the SONAME bump. > > > > > > -- > > > tobi signature.asc Description: PGP signature
