FWIW, I set the date in changes.xml so that it goes with the RC git tag which then becomes the release tag. If the RC fails, then I update the date, so we have a clear record, YMMV.
Gary On Sat, Jul 10, 2021, 06:12 Stefan Bodewig <bode...@apache.org> wrote: > On 2021-07-10, Bruno P. Kinoshita wrote: > > > The RELEASE-NOTES.txt for 1.21 starts with "Compress 1.20 now at least > > requires Java 8 to build and run." which is a bit confusing, but not a > > major issue. (Maybe it would be better to say "Compress 1.20 and later > > require Java 8..."?) > > It is going to be > > "Compress 1.21 is the first release to require Java 8 to build and run." > > I've already fixed it locally. > > > We also have 2 README files, .txt and .md. We probably want a single > > README file. > > README.txt has been there since the initial commit in CVS, I'd > guess. When Commons decided to have uniform README.mds the .txt file has > been left in. It may actually contain information not present in > README.md. > > > The README.md contains the download instructions for 1.21, so I think > > that's the one we see on GitHub. > > Yes, github prefers markdown over text. > > > But I just looked at the source ZIP in the dist area, and it only > > contains README.txt, no README.md. > > This is a different kind of readme, it never occured to me to copy the > README from the source tree as they have different purposes. The one in > dist describes the downloadable artifacts, not the project. In addition > I don't believe markdown files will render favorably in a directory > listing. > > > Reports look good. The changes report is showing the 1.21 release as > > not released yet. Normally I think that that date is set to the RC > > creation date. > > Not sure. I've always done it that way and set the release date just > before publishing the site (and when merging the git tag back to > master). The site will need to be updated anyway (javadocs published for > example). > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
