On Tue, 2020-05-05 at 08:11 +0200, Carsten Ziegeler wrote: > > On 04.05.2020 16:36, Bertrand Delacretaz wrote: > > On Mon, May 4, 2020 at 4:22 PM Carsten Ziegeler < > > [email protected]> wrote: > > > ...Today, if someone forgets to add a release to our webpage, we > > > can easily > > > fix that later on by editing that page and adding an old release. > > > Is > > > that possible with the reporter, too?.. > > > > Yes, the reporter nags us with > > https://reporter.apache.org/addrelease.html?sling and we can use > > that > > form at any time to add missing releases. > > > > > ...Or in other words, todays release page is very easy to > > > maintain - and > > > for a release you have to edit the downloads page anyway. At > > > first look, > > > relying on the reporter data seems to be more complicated... > > > > I think it depends whether we agree that the reporter.a.o data is > > required - if that's a yes, maintaining our own page duplicates > > data. > > > > Right, so lets talk about that first :)
Here's what I dug up on that (emphasis mine) The PMC MUST submit a quarterly report to the board [1]. The board reporting guidelines [2] have a REQUIRED section titled "When did the project last make any releases?". In [1] it is mentioned that (the PMC) CAN use the Apache Committee Reporter tool to simplify some data collection for (the) report. We also have an item in our release management document [3] that mentions the reporter service. What I take out of this is that the reporter tool is not mandatory, but keeping a record of releases so they are included in the board report it. In practice, I have been using the reporter tool to generate the board report, and not the list on our website. Thanks, Robert [1]: https://www.apache.org/dev/pmc.html#ensure-the-projects-quarterly-board-report-is-submitted [2]: https://www.apache.org/foundation/board/reporting [3]: https://sling.apache.org/documentation/development/release-management.html#promoting-the-release-1
