Right, thanks Robert
So the question is, whether we want or need to keep three lists.
We have:
- the reporter data
- the releases page
- the downloads list/page
I'm usually not updating the reporter data on a release and it seems
others are not doing that either. The same happens sometimes to the web
site, especially the download list.
Bottom line, the three sources get out of sync today.
Automation and generation brings up another problem: technical names vs
human friendly names. If you look at the reporter data, we have there
"Servlets Post 2.3.6" as well as "org.apache.sling.servlets.post 2.3.8".
Now for all user facing info, I think the human friendly names are much
better ("Servlets Post x.y.z").
Overall, this can become a very complicated thing. I'm not saying we
should not solve it, but I think there is more to it than just
identifying the single source of truth
Carsten
On 05.05.2020 10:05, Robert Munteanu wrote:
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
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
