On Mon, 28 Sept 2026 at 16:22, Dave Fisher <[email protected]> wrote: > > > > > On Sep 28, 2026, at 8:04 AM, sebb <[email protected]> wrote: > > > > On Mon, 28 Sept 2026 at 15:35, Dave Fisher <[email protected] > > <mailto:[email protected]>> wrote: > >> > >> Currently the difference between dist.apache.org/release > >> <http://dist.apache.org/release> and downloads.apache.org > >> <http://downloads.apache.org/> are technical and Infrastructure > >> preference. The content should be automatically identical - the sync takes > >> some time. The downloads.apache.org <http://downloads.apache.org/> is > >> meant for non-ASF use and is able to handle internet scale. > >> > >> For a podling it is more important to get the download page correct than > >> the vote email. > > > > If the sync can take some time, then all the more reason to ensure > > that KEYS is linked from downloads.a.o in both vote email and download > > page. > > What if the sync has not happened when the RC is published? > > Hopefully the KEYS file is changed when a new Release Manager has their key > added, or a current RM adds a new key. This activity should be documented as > a separate process from building releases, but I know that it is not. > > > > > Also, I could not find a source download page on the website. > > The download web page is a requirement for announcing the release and is > typically updated after the VOTE succeeds.. Publishing it early is > advertising an unapproved release which is not allowed outside of normal > development channels.
It is only the release details that must not be published in advance. There is no issue in publishing the KEYS link. This appears to be the first ASF release, so that may be why there is no download page for the source, however there are links to download the CLI. It would be useful to see a mock-up of the proposed download page before approving the RC. Sebb > Best, > Dave > > > > > Sebb > >> Best, > >> Dave > >> > >>> On Sep 28, 2026, at 1:51 AM, Michele Sciabarra <[email protected]> > >>> wrote: > >>> > >>> Actually, this is where initally placed the KYES but our mentors > >>> instructed us that the correct place for the KEYS is where we put it. > >>> > >>> On 2026/09/27 22:57:27 sebb wrote: > >>>> On Sun, 27 Sept 2026 at 15:48, Jean-Baptiste Onofré <[email protected]> > >>>> wrote: > >>>>> > >>>>> +1 (binding) > >>>>> > >>>>> I checked: > >>>>> - source distribution > >>>>> -- incubating is in the name/version > >>>>> -- checksum and signature are good > >>>>> -- DISCLAIMER is present (standard incubating wording) > >>>>> -- LICENSE (ALv2 + bundled component licenses) and NOTICE (ASF > >>>>> copyright + proper third-party attributions) look good > >>>>> -- ASF header is present in all expected files > >>>>> -- No binary/compiled file found in the source distribution (just > >>>>> images) > >>>>> > >>>>> Regards > >>>>> JB > >>>>> > >>>>> On Sun, Sep 27, 2026 at 1:46 PM Michele Sciabarra > >>>>> <[email protected]> wrote: > >>>>>> > >>>>>> Hi all, > >>>>>> > >>>>>> I'd like to request an Incubator PMC vote on the first Apache > >>>>>> OpenServerless > >>>>>> source release, version 0.9.0 (incubating), release candidate 6. > >>>>>> > >>>>>> OpenServerless is a self contained serverless distribution allowing to > >>>>>> setup a FaaS system with a complete development environment and > >>>>>> integrated services. > >>>>>> > >>>>>> The release proposal passed with +4 binding, +2 non binding and 0 > >>>>>> other votes. > >>>>>> > >>>>>> https://lists.apache.org/thread/slpthzqyjp94gnb0mv530jhp8zfsz87p > >>>>>> > >>>>>> The artifacts for this release candidate can be found at: > >>>>>> > >>>>>> https://dist.apache.org/repos/dist/dev/incubator/openserverless/0.9.0-incubating-RC6 > >>>>>> > >>>>>> The Git tag to be voted upon is: > >>>>>> > >>>>>> v0.9.0-incubating-RC6 > >>>>>> > >>>>>> https://github.com/apache/openserverless/releases/tag/v0.9.0-incubating-RC6 > >>>>>> > >>>>>> Release artifacts are signed with the GPG key of the release manager. > >>>>>> > >>>>>> The KEYS file is available at: > >>>>>> > >>>>>> https://dist.apache.org/repos/dist/release/incubator/openserverless/KEYS > >>>> > >>>> The KEYS file should be linked from > >>>> https://downloads.apache.org/incubator/openserverless/KEYS > >>>> as that is the location from where downloaders should fetch the file. > >>>> > >>>>>> > >>>>>> Please download, verify, and test the release candidate. > >>>>>> > >>>>>> The vote will run for a minimum of 72 hours and close no earlier > >>>>>> than 2026-10-01 > >>>>>> > >>>>>> Please vote: > >>>>>> > >>>>>> [ ] +1 Release this package as Apache OpenServerless 0.9.0-incubating > >>>>>> [ ] +0 > >>>>>> [ ] -1 Do not release this package because... (reason required) > >>>>>> > >>>>>> Checklist for reference: > >>>>>> [ ] Download links are valid > >>>>>> [ ] Checksums and signatures are valid > >>>>>> [ ] LICENSE/NOTICE files exist > >>>>>> [ ] No unexpected binary files in source > >>>>>> [ ] All source files have ASF headers > >>>>>> [ ] Can compile from source > >>>>>> > >>>>>> On behalf of the Apache OpenServerless Podling PMC (PPMC), > >>>>>> -- > >>>>>> Michele Sciabarrà - [email protected] - linkedin.com/in/msciab > >>>>>> Apache OpenServerless committer - reddit.com/r/openserverless > >>>>>> Apache OpenWhisk PMC member - Author Learning Apache OpenWhisk > >>>>>> > >>>>>> --------------------------------------------------------------------- > >>>>>> 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] > >>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > <mailto:[email protected]> > > For additional commands, e-mail: [email protected] > > <mailto:[email protected]> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
