Congratulations to SDAP on getting the first release through the voting process! And thank you Riley for your huge efforts as release manager.
The basic steps are to send a '[RESULT]' email, move the artifacts, add a "downloads" page to the site, and send an announcement. Here is a detailed list of steps: 1. Send the [RESULT] email to general@incubator. 2. Choose a release date. (I generally publish a release before ~4pm pacific time, so that my local date is the same as the UTC date. Prevents website inconsistencies.) 3. Register the release at https://reporter.apache.org. 4. It's worth checking that the site complies with branding requirements, since the announcement will generate traffic and scrutiny. 5. Compose the announcement, and send it to annou...@apache.org. They are moderated. They generally have a particular format, in particular, starting with a description of the project, and a description of why the release is notable. (Plenty of examples in the archive [1].) I'm conservative and write in plain text formatted at 60 characters, so that no one's client will do stupid wrapping. The first draft might be rejected, so I wouldn't send the announcement to dev@ until the message to announce@ goes through. 6. Add a template for the announcement email to the 'howto" for the next release manager. 7. Send out a tweet. Optionally, do some other promotional stuff, like adding a 'news' item to the site, posting a video to youtube. (What about a quick video of downloading the release and starting a server or whatever you consider to be the minimal 'smoke test' demo?) 8. In Calcite, we mark bugs 'fixed' as the patches are merged, and we only mark the bugs 'closed' after the release has happened. If SDAP has a similar process, close those bugs. 9. Finalize that 'howto' for the next release manager, add it somewhere that they can find it, and post it to dev@. Maybe someone else could help with the site and promotional work? Riley has done a huge amount of work over the holiday period to get this release out. While you're adding a downloads page to the site, update the team page [2], and a link to Slack. 10. Make another release in 2 months, to prove that the muscle still works. Julian [1] https://lists.apache.org/list?annou...@apache.org [2] https://sdap.apache.org/team On Tue, Jan 17, 2023 at 6:36 PM Riley Kuttruff <r...@apache.org> wrote: > > So it looks like the IPMC vote passed. I'm assuming the next/final steps are > 1) moving the release artifacts to the dist/release area and 2) sending an > announcement, correct? > > - Riley > > On 2023/01/17 17:46:31 Nga Chung wrote: > > This was announced in the DISCUSS thread here [1] so maybe it was missed by > > folks. > > > > Thanks for your guidance regarding the meeting format. We'll make sure to > > follow and send out a summary. > > > > Best, > > Nga > > > > [1] https://lists.apache.org/thread/b2z796mfzfl6h0gj7m8mo8x25yt4dxoh > > > > On Tue, Jan 17, 2023 at 9:38 AM Julian Hyde <jh...@apache.org> wrote: > > > > > Thanks for the heads up. Was this announced earlier? > > > > > > In Apache we need to be inclusive of people who prefer asynchronous > > > communication (in other time zones, for example) so be sure to not > > > make any decisions at the meeting, and send a summary of the meeting > > > to this list. A good pattern is to start discussions at the meeting > > > and then convert them into email discussions on the dev list. > > > > > > Julian > > > > > > On Tue, Jan 17, 2023 at 9:24 AM Nga Chung <nch...@apache.org> wrote: > > > > > > > > Hi all, > > > > > > > > Our first SDAP monthly meeting is today at 15:00 - 16:00 Pacific time. > > > > > > > > Join from the meeting link > > > > https://jpl.webex.com/jpl/j.php?MTID=m6d205ee391099975ab22ae1b4a65df53 > > > > > > > > Join by meeting number > > > > Meeting number (access code): 2761 748 8734 > > > > Meeting password: MjdFissq569 > > > > > > > > Best, > > > > Nga > > > > >
