Hello Josh, Josh Elser <els...@apache.org> schrieb am Fr., 20. Mai 2016 um 05:28 Uhr:
> One more (final?) snafu: turns out I used the "wrong" name for the > artifacts in dist.a.o which caused the website to have the wrong links. > > Just corrected that, sadly the website will continue to be a little off > for another 24hrs. These are some more places that the docs could use > some help (I knew what needed to be done already, but, obviously, I > didn't do it quite right on my own). > Are you talking about [1]? Please add any improvements you find necessary. I've done it so often that I'm probably unaware of little inconsistencies. :-) Benedikt [1] http://commons.apache.org/releases/release.html > > I plan to send out the ANNOUNCE as soon as I see most of the mirrors are > updated again. > > - Josh > > sebb wrote: > > On 19 May 2016 at 18:43, Josh Elser<els...@apache.org> wrote: > >> sebb wrote: > >>> On 19 May 2016 at 03:14, Josh Elser<els...@apache.org> wrote: > >>>> Hi all, > >>>> > >>>> Worked through the remaining steps for this release. dist.a.o (dev and > >>>> release) were both updated, trunk was bumped to 2.2-SNAPSHOT, nexus > repo > >>>> was > >>>> released, reporter.a.o was updated, and the svn tag was renamed. I did > >>> > >>> It's better to copy rather than rename. > >> > >> Sorry, I did an `svn cp`, IIRC. Just didn't write the correct verb here > :) > > > > Yes, I have since seen the commit message. > > > >>>> remove the checksums on the signatures before promoting the Nexus > >>>> repository > >>>> (thanks for pointing that out Bernd and Sebb). Just pushed all of the > >>>> fixVersion=2.1 issues out as well. > >>>> > >>>> Copying from Ralph's 2.0 announcement: > >>>> > >>>> <snip> > >>>> The Apache Commons team is pleased to announce the release of Apache > >>>> Commons > >>>> VFS 2.1 > >>> > >>> We ought to include a paragraph on what VFS does. > >>> The Announce will be seen much wider than just the VFS user community. > >>> Yes, people can check the website, but a brief description would be > >>> very helpful. > >> > >> I see a sentence on the website that would be easily included. Any > >> suggestions of other text that could be included? Oh, and I guess who > all is > >> normally included besides announce@a.o? users@c.a.o? Anyone else? > > > > Normally: > > > > Commons: dev, users > > ASF: announce > > > >>>> Details of the changes and bug fixes in this release can be found in > >>>> the release notes: > >>>> http://www.apache.org/dist/commons/vfs/RELEASE_NOTES.txt > >>> > >>> Likewise it would be useful to provide a short summary of the main > >>> changes in the release. > >>> In this case there are so many that it might be hard to summarise, so > >>> perhaps something like: > >>> > >>> "VFS 2.1 is binary compatible with 2.0. > >>> It includes many new features and bug fixes; please see the release > >>> notes for details." > >>> > >>> The intention of adding this info is to inform potential new users why > >>> they might want to take a look at VFS, and to inform existing users > >>> why they might want to upgrade. > >>> > >>> Note that at some point RELEASE_NOTES.txt became RELEASE-NOTES.txt > >>> The former should be deleted from the web site once the announce has > >>> occured. > >> > >> Sounds great. Will include this too. > >> > >>>> Anything else I missed? > >>> > >>> Any superseded releases need to be removed from dist/release. > >>> It should be safe to do this once the announce has been sent, assuming > >>> the process above has been followed. > >>> > >>> Also tidy the RN files (as mentioned above). > >> > >> Oo, I guess I jumped the gun a little bit here. I cleaned up the 2.0 > release > >> when I pushed out 2.1 to dist/release. > > > > Yes, that's not ideal. > > > > There needs to be an overlap while mirrors get the new release. > > The website and announce can then be done > > And then the old release can be removed > > > >>> S. > >>> P.S. well done and thanks for getting this far. > >> > >> And thank you for your help too! > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> For additional commands, e-mail: dev-h...@commons.apache.org > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
