Ok, So, copying stuff from dev to release can only be done by PMC members, so I guess I’m out of the game and one of you folks needs to do it.
I’d say if this is not done by the end of the coming week, I’ll probably go a different route and have someone appointed PMC membership by the board to finish this release. Chris Von: Christofer Dutz <christofer.d...@c-ware.de> Datum: Sonntag, 19. November 2023 um 11:11 An: Cocoon PMC List <priv...@cocoon.apache.org>, dev@cocoon.apache.org <dev@cocoon.apache.org> Cc: Cocoon PMC List <priv...@cocoon.apache.org> Betreff: [RESULT] [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ Ok, So, I will now announce the vote as over and as successful, as we have 3 binding +1 votes. * Francesco Chicchiriccò * Cédric Damioli * David Crossley As it seems that nobody here is able/willing to help with getting my key into the dist KEYS file and I can’t move the release from dev to dist … I will work with infra on doing this and potentially using some board-overrides. Which is super unfortunate that I have to use this tool in order to get the release out, as this implies an inability of the current PMC to actually perform releases, which is number 1 cause for going to the attic. Chris Von: Christofer Dutz <christofer.d...@c-ware.de> Datum: Donnerstag, 16. November 2023 um 10:03 An: Cocoon PMC List <priv...@cocoon.apache.org>, dev@cocoon.apache.org <dev@cocoon.apache.org> Cc: Cocoon PMC List <priv...@cocoon.apache.org> Betreff: AW: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ Ok. So I didn’t wait for the business trip to end and gave it another try. I Added my key to the end of the existing KEYS file, and whenever I wanted to commit it, I get “permission denied”. Someone pointed out here, that this is usually because of an “http” instead of a “https” url, but I checked that and this was not the case: cdutz@MacBook-Pro-von-Christofer cocoon % svn info --show-item repos-root-url https://dist.apache.org/repos/dist I also tried providing my apache user-id and password, but I still get this reply: svn: E195023: Ändern der Datei »/Users/cdutz/Temp/cocoon/cocoon/KEYS« durch den Server zurückgewiesen svn: E175013: Zugriff auf »/repos/dist/!svn/txr/65331-1j1c/release/cocoon/KEYS« verboten So … I’d love to add my key, but seems I’m not allowed … so If any of you would be so kind and do that for me, I’d love to finalize the RC process (However I expect someone else to also have to move the RC to the distribution area, because I would expect to also not be allowed to move the files in SVN. Chris Von: Christofer Dutz <christofer.d...@c-ware.de> Datum: Mittwoch, 15. November 2023 um 21:40 An: Cocoon PMC List <priv...@cocoon.apache.org>, dev@cocoon.apache.org <dev@cocoon.apache.org> Cc: Cocoon PMC List <priv...@cocoon.apache.org> Betreff: Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ I'll do that as soon as I'm back from my business trip. Chris Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> ________________________________ From: David Crossley <cross...@apache.org> Sent: Wednesday, November 15, 2023 3:57:44 AM To: dev@cocoon.apache.org <dev@cocoon.apache.org> Cc: Cocoon PMC List <priv...@cocoon.apache.org> Subject: Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ Our KEYS file is at https://dist.apache.org/repos/dist/release/cocoon/KEYS Chris, please add yours to that one, rather than "replacing" it as is indicated in your temporary KEYS file. And extensive gratitude to you for taking on this task. -David On Sun, Oct 29, 2023 at 09:01:12PM +0000, Christofer Dutz wrote: > Here’s the KEYS file … there wasn’t any, so I initialized it with my key. > > https://dist.apache.org/repos/dist/dev/cocoon/KEYS > > Chris > > Von: Christofer Dutz <christofer.d...@c-ware.de> > Datum: Sonntag, 29. Oktober 2023 um 21:09 > An: dev@cocoon.apache.org <dev@cocoon.apache.org> > Cc: Cocoon PMC List <priv...@cocoon.apache.org> > Betreff: Re: [VOTE] Apache Cocoon 2.3.0 RC2 > https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ > I added my key to the KEYS file in the svn repo one level up.. > > Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> > ________________________________ > From: Peter Hunsberger <peter.hunsber...@gmail.com> > Sent: Sunday, October 29, 2023 6:16:02 PM > To: dev@cocoon.apache.org <dev@cocoon.apache.org> > Cc: Cocoon PMC List <priv...@cocoon.apache.org> > Subject: Re: [VOTE] Apache Cocoon 2.3.0 RC2 > https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ > > Everything looks good except I can't check the signature, I get "No public > key" from gpg. I believe I need a copy of your public key to import? > > Peter Hunsberger > > > On Sun, Oct 29, 2023 at 6:55 AM Christofer Dutz > <christofer.d...@c-ware.de<mailto:christofer.d...@c-ware.de>> wrote: > > Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote > > on accepting it for release. All Maven artifacts are available under [1]. > > Voting will be open for 72hr. > > > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 > > are required to pass. > > > > Release tag: > https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/ > > Director revision of the tag: 1913422 > > > > Per [3] "Before voting +1 PMC members are required to download > > the signed source code package, compile it as provided, and test > > the resulting executable on their own platform, along with also > > verifying that the package meets the requirements of the ASF policy > > on releases." > > > > You can achieve the above by following the guide of a fellow Apache project > [4]. > > > > [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items > in [4]) > > [ ] -1 reject (explanation required) > > > > > > [1] https://repository.apache.org/content/repositories/orgapachecocoon-1007 > > [2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ > > [3] https://www.apache.org/dev/release.html#approving-a-release > > [4] > https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release > >
