> get rid of the dev KEYS file

This is a oneshot action. I removed the file with (in case any
community member want to know how to do that):

  $ svn rm https://dist.apache.org/repos/dist/dev/incubator/fesod/KEYS
-m "Remove KEYS from dev channel"
  Committing transaction...
  Committed revision 87349.

For removing old RCs, it should be part of the release process,
typically a step of cancelling a candidate. You can take [1] as an
example.

[1] 
https://github.com/apache/asyncband/blob/64d7a94ddb5ab9f2e130f8f1cc8f392301e73ebe/RELEASE.md?plain=1#L210-L218

Best,
tison.

tison <[email protected]> 于2026年9月8日周二 18:11写道:
>
> -1 binding
>
> I second to PJ's comment. While it may not be a blocker, I'd try to
> nudge the PPMC to consider why we have two source tarballs. It seems
> the fesod-parent one is unnecessary and generated by some automation.
> Please provide some information or try to avoid that if it is
> unnecessary.
>
> Best,
> tison.
>
> PJ Fanning <[email protected]> 于2026年9月8日周二 18:07写道:
> >
> > 0 from me. I can't +1 while you continue to have 2 source releases and
> > no description as to why you need them.
> >
> > On Tue, 8 Sept 2026 at 11:05, PJ Fanning <[email protected]> wrote:
> > >
> > > Can you remove the old RCs from 
> > > https://dist.apache.org/repos/dist/dev/incubator/fesod/ and get rid of 
> > > the dev KEYS file?
> > >
> > >
> > > On 2026/09/08 07:46:17 Xin Yan wrote:
> > > > +1 (binding)
> > > >
> > > > On 2026/09/06 09:33:44 ian wrote:
> > > > > Hello Fesod Community,
> > > > >
> > > > > This is a call for a vote to release Apache Fesod 2.1.0-incubating as
> > > > > Release Candidate 4 (RC4).
> > > > >
> > > > > The source release candidate tarball and zip are available at:
> > > > >
> > > > > https://dist.apache.org/repos/dist/dev/incubator/fesod/2.1.0-incubating-rc4/
> > > > >     apache-fesod-2.1.0-incubating-src.tar.gz
> > > > >     fesod-parent-2.1.0-incubating-source-release.zip
> > > > >
> > > > > The git tag to be voted on:
> > > > >     https://github.com/apache/fesod/tree/2.1.0-incubating-rc4
> > > > >     (commit 715cccb4 "chore: bump revision to 2.1.0-incubating for RC4
> > > > > release")
> > > > >
> > > > > Release checksums (SHA-512):
> > > > >     apache-fesod-2.1.0-incubating-src.tar.gz
> > > > >       
> > > > > d7eeaa4da0a4febbe2c35083c447f3a92365062dee91acb97b16e6685718832cba
> > > > >       e6d3fd52dbc26188c0db1f934920db57c1e7428b70cea768f57db9995086cc
> > > > >     fesod-parent-2.1.0-incubating-source-release.zip
> > > > >       1b3502a4b14c024ca23c82af56ea881579c60d956a2047f636f941921391574a
> > > > >       77deb9e4072860055ed4883c618aa2163e9a7f7e1187774b2213a47719b870db
> > > > >
> > > > > The artifacts were compiled with JDK 8 (class file major version 52) 
> > > > > and all
> > > > >   916 tests pass. The Maven staging repository (for testing only, not 
> > > > > the
> > > > >   object of this vote) is:
> > > > >     
> > > > > https://repository.apache.org/content/repositories/orgapachefesod-1051/
> > > > >
> > > > > The signing key used is:
> > > > >     https://downloads.apache.org/incubator/fesod/KEYS
> > > > >     fingerprint CCCFA0EAA4BFB4A441D4D770FDD68C1D3497B880
> > > > >
> > > > > Please vote on releasing these binaries and source artifacts as 
> > > > > Apache Fesod
> > > > > 2.1.0-incubating. The vote will be open for at least 72 hours.
> > > > >
> > > > >     [ ] +1  approve the release
> > > > >     [ ]  0  abstain
> > > > >     [ ] -1  disapprove (with reason)
> > > > >
> > > > > Vote members should verify the release following the checklist at
> > > > > https://github.com/apache/fesod/blob/main/docs/release/verification.md
> > > > >
> > > > > This vote requires at least 3 binding +1 votes from PMC members. A 
> > > > > minimum
> > > > > of 72 hours will be given.
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Zhang Zhe
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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]
> > >
> >
> > ---------------------------------------------------------------------
> > 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]

Reply via email to