Hi, thanks for this work, I think having the notable-change-items also in the status.xml is a good thing because it is easier to remember what changes did happen at the time the changelog is updated compared to when the release is prepared later by one dev who might not be aware that somebody else did build something a while back.
Dominik. On Fri, Oct 21, 2016 at 12:23 PM, Javen O'Neal <one...@apache.org> wrote: > I added the major changes from the 3.15 release notes [1] to the > detailed changelog [2] in r1765977 [3]. > > [1] https://www.apache.org/dyn/closer.lua/poi/release/RELEASE-NOTES.txt > [2] https://poi.apache.org/changes.html > [3] https://svn.apache.org/viewvc?view=revision&revision=1765977 > > We could choose to update the changelog with the major changes when we > announce a release, create the "RELEASE-NOTES-<majorver>.txt" as Nick > suggested, or both. > If we decide that it's a headache maintaining the major changes in two > locations and prefer going with "RELEASE-NOTES-<majorver>.txt", then > we can revert the changes I made to status.xml > > In the meantime, what's the best way to retrieve old release notes? > Were they committed to a private or public SVN server? If not, we can > dig through the dev@ email archive for the [VOTE] email, but this > would take longer to extract. > > On Thu, Sep 29, 2016 at 3:08 PM, Nick Burch <n...@apache.org> wrote: > > On 29/09/16 15:29, Javen O'Neal wrote: > >> > >> Do we archive the release notes somewhere so that someone can read a > >> high-level summary of the changes for each release? Digging through > >> the dev@ email list archive to find the release notes draft or > >> searching a web archiver of one of the mirrors at a date in the past > >> seem suboptimal. There is no release notes file in the subversion tag > >> or a page on our site that summarizes the changes in a release more > >> concisely than changes.html. > >> > >> The current https://poi.apache.org links to both 3.14 and 3.15, but we > >> overwrote the 3.14 release notes on > >> https://www.apache.org/dyn/closer.lua/poi/release/RELEASE-NOTES.txt > >> and all mirrors when we released 3.15. > > > > > > After a final release, the homepage and download page should only ever > link > > to the most current final version. No other versions should live on the > dist > > area, otherwise infra get grumpy... > > > > When we do an alpha or beta release, then homepage + download should > link to > > both > > > > If we don't already, it might be good to deploy the release notes twice, > > once as "RELEASE-NOTES.txt" (overwritten often), once as > > "RELEASE-NOTES-<majorver>.txt". The latter would then always be > available > > from archive.apache.org even after a newer final release. Thoughts? > > > > Nick > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > > For additional commands, e-mail: dev-h...@poi.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > >
