Re: APR 1.7.1 release?
I'm willing to RM APR and APR-util 1.7 releases. Would propose we set a date out 2 weeks, anything lingering needs to be finalized with the usual oversight no later than the 8th, and we tag on the 14th, announce on the 15th when the mirrors have caught up. That gives enough days for committers to review the last changes to these release branches. But I'd be happier co-RM'ing this with a newer committer/PMC participant who wants to learn the ropes. Any volunteers? Other thoughts or observations? On Tue, Aug 31, 2021 at 3:09 AM Rainer Jung wrote: > > Hi there, > > any chance we find an RM for a APR 1.7.1 release? At least there was the > fix for CVE-2021-35940 and CHANGES contains 15 more items (many of them > platform specific or build improvements). Last release 1.7.0 was in > April 2019. > > For APR-util I don't know the current state and release needs for the > 1.6.x and 1.7.x branches. Last 1.6.x release was in October 2017, 1.7.x > has never been released. CHANGES for 1.6.x only contains one > apr_dbm_gdbm fix plus a minor libtool use improvement. > > Apache httpd is planing to start a release cycle soon and it would be > nice to have a clean APR 1.7.1 and maybe APR-util also. > > Thanks and regards, > > Rainer
Re: [VOTE] Re: http2 test suite
On Wed, Sep 01, 2021 at 10:56:15AM +0100, Joe Orton wrote: > On Mon, Aug 30, 2021 at 08:39:17AM +0200, Ruediger Pluem wrote: > > On 8/28/21 4:00 PM, Yann Ylavic wrote: > > > On Fri, Aug 27, 2021 at 10:07 AM ste...@eissing.org > > > wrote: > > >> Related to that, do we exempt "./test" from RTC in 2.4.x/STATUS? > > > > > > +1 for CTR, that's how the tests framework works de facto already (a > > > single framework/trunk is run for both trunk and 2.4.x). > > > > +1 on CTR for this. > > +1 from me too to make test/ CTR for 2.4.x, let's make this a proper > vote thread. > > (I would hold off a week or so on enabling the h2 tests in Travis for > 2.4.x until we are confident they are stable in trunk CI runs) > +1 Regards Giovanni signature.asc Description: PGP signature
Re: Failed: apache/httpd#1856 (candidate-2.4.49 - cd5b61d)
I think there are some jobs that are excluded if not "2.4.x", so it's doing some trunk-only stuff. On Thu, Sep 2, 2021 at 1:37 PM ste...@eissing.org wrote: > > Not sure what to make of this. I think testing a release candidate is fine, > but > I do not really see what was wrong. > > Maybe tomorrow, I see it... > > - Stefan > > > Am 02.09.2021 um 18:12 schrieb Travis CI : > > > > apache / httpd > > candidate-2.4.49 > > Build #1856 failed24 mins and 12 secs > > Stefan Eissingcd5b61d CHANGESET → > > release candidate 2.4.49 > > > > git-svn-id: > > https://svn.apache.org/repos/asf/httpd/httpd/tags/candidate-2.4.49@1892807 > > 13f79535-47bb-0310-9956-ffa450edef68 > > Want to know about upcoming build environment updates? > > > > Would you like to stay up-to-date with the upcoming Travis CI build > > environment updates? We set up a mailing list for you! > > > > SIGN UP HERE > > Documentation about Travis CI > > Have any questions? We're here to help. > > Unsubscribe from build emails from the apache/httpd repository. > > To unsubscribe from all build emails, please update your settings. > > > > Travis CI GmbH, Rigaer Str. 8, 10427 Berlin, Germany | GF/CEO: Randy Jacops > > | Contact: cont...@travis-ci.com | Amtsgericht Charlottenburg, Berlin, HRB > > 140133 B | Umsatzsteuer-ID gemäß §27 a Umsatzsteuergesetz: DE282002648 > -- Eric Covener cove...@gmail.com
Re: Failed: apache/httpd#1856 (candidate-2.4.49 - cd5b61d)
Not sure what to make of this. I think testing a release candidate is fine, but I do not really see what was wrong. Maybe tomorrow, I see it... - Stefan > Am 02.09.2021 um 18:12 schrieb Travis CI : > > apache / httpd > candidate-2.4.49 > Build #1856 failed24 mins and 12 secs > Stefan Eissingcd5b61d CHANGESET → > release candidate 2.4.49 > > git-svn-id: > https://svn.apache.org/repos/asf/httpd/httpd/tags/candidate-2.4.49@1892807 > 13f79535-47bb-0310-9956-ffa450edef68 > Want to know about upcoming build environment updates? > > Would you like to stay up-to-date with the upcoming Travis CI build > environment updates? We set up a mailing list for you! > > SIGN UP HERE > Documentation about Travis CI > Have any questions? We're here to help. > Unsubscribe from build emails from the apache/httpd repository. > To unsubscribe from all build emails, please update your settings. > > Travis CI GmbH, Rigaer Str. 8, 10427 Berlin, Germany | GF/CEO: Randy Jacops | > Contact: cont...@travis-ci.com | Amtsgericht Charlottenburg, Berlin, HRB > 140133 B | Umsatzsteuer-ID gemäß §27 a Umsatzsteuergesetz: DE282002648
Failed: apache/httpd#1859 (candidate-2.4.49 - ababb7a)
Build Update for apache/httpd - Build: #1859 Status: Failed Duration: 24 mins and 2 secs Commit: ababb7a (candidate-2.4.49) Author: Stefan Eissing Message: Post tag updates git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/tags/candidate-2.4.49@1892813 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/httpd/compare/3566f1dd4b1d...249100054faf View the full build log and details: https://app.travis-ci.com/github/apache/httpd/builds/236802508?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/httpd repository going to https://app.travis-ci.com/account/preferences/unsubscribe?repository=16806660&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://app.travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Failed: apache/httpd#1857 (candidate-2.4.49 - d458b74)
Build Update for apache/httpd - Build: #1857 Status: Failed Duration: 21 mins and 29 secs Commit: d458b74 (candidate-2.4.49) Author: Stefan Eissing Message: release candidate 2.4.49 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/tags/candidate-2.4.49@1892809 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/httpd/compare/d990cfa86dec...3566f1dd4b1d View the full build log and details: https://app.travis-ci.com/github/apache/httpd/builds/236796377?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/httpd repository going to https://app.travis-ci.com/account/preferences/unsubscribe?repository=16806660&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://app.travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Failed: apache/httpd#1856 (candidate-2.4.49 - cd5b61d)
Build Update for apache/httpd - Build: #1856 Status: Failed Duration: 24 mins and 12 secs Commit: cd5b61d (candidate-2.4.49) Author: Stefan Eissing Message: release candidate 2.4.49 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/tags/candidate-2.4.49@1892807 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/httpd/commit/cd5b61dc60c4 View the full build log and details: https://app.travis-ci.com/github/apache/httpd/builds/236795061?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/httpd repository going to https://app.travis-ci.com/account/preferences/unsubscribe?repository=16806660&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://app.travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Re: release?
On 9/2/21 3:06 PM, Eric Covener wrote: > Since you are going through this I wanted to mention: > > I think the public doc we have should mention everything that's done > during ther release, even the security stuff that is somewhat private. > The ASF-wide security policy is already public > (https://www.apache.org/security/committers.html) and this is just the > mechanics of it for us. > > Anyone object? This way we have one linear place to point to. +1 Looks sensible. The details of an actual security issue should not be public until we make it so, but the procedure we use can be. Regards Rüdiger
Re: release?
Since you are going through this I wanted to mention: I think the public doc we have should mention everything that's done during ther release, even the security stuff that is somewhat private. The ASF-wide security policy is already public (https://www.apache.org/security/committers.html) and this is just the mechanics of it for us. Anyone object? This way we have one linear place to point to. On Mon, Aug 30, 2021 at 7:36 AM ste...@eissing.org wrote: > > In what state is our release handling? Given someone holding my hand, could I > do it? Or is it better to look someone over the shoulder while he does it? > > Cheers, > Stefan -- Eric Covener cove...@gmail.com
Re: release scripts
On Thu, Sep 2, 2021 at 8:21 AM ste...@eissing.org wrote: > > OK, small hickup. The build shell for the manuals wants a JDK 1.8 or 11... > uhm...I need a time machine, or we can change the check there. > > Since I am not experienced in our manual stuff, can someone knowledgable > check this? If it doesn't create a crazy diff from what's currently generated, it's fine. Maybe time to strip out the check.
Re: release scripts
OK, small hickup. The build shell for the manuals wants a JDK 1.8 or 11... uhm...I need a time machine, or we can change the check there. Since I am not experienced in our manual stuff, can someone knowledgable check this? - Stefan > Am 01.09.2021 um 13:27 schrieb ste...@eissing.org: > > > >> Am 01.09.2021 um 13:15 schrieb Eric Covener : >> >> On Wed, Sep 1, 2021 at 6:08 AM ste...@eissing.org wrote: >>> >>> Having a look at the release scripts and how they work. >>> >>> I think we can use SVN and its branches/tags in a bit smarter way >>> and make things easier. As Christophe mentioned, he would like a >>> "--dry-run" option, because when things do not run smoothly to the >>> end, you have not only a local messed-up state but the SVN repro >>> itself is also changed without easy remedies. >> >> LGTM. Maybe even separate -tmp and -candidate branches aren't needed? > > We can do without, yes. Seems more simple that way. > >> It's all scratch space for the RM. >> Does the release branch get moved to a tag at the end? > > Yes, that line was missing, I saw too late and did not > want to add another mail to my wall of text. So > >> svn mv branches/2.4.49-candidate tags/2.4.49 > > would be the last thing at the voting.
