quick ping: where are we exactly - trying to close that topic before next year ;)? From my understanding current issues are not blocking and we could move forward if the release note is fixed manually after the vote.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> 2017-12-17 21:51 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>: > > > Le 17 déc. 2017 19:35, "Thomas Vandahl" <t...@apache.org> a écrit : > > On 15.12.17 14:05, Romain Manni-Bucau wrote: > > Here what I tested: > > > > 1. svn co .... > > 2. mvn clean install > > 3. mvn source:jar > > > > => the same trash is here > > > > 4. mvn clean source:jar > > > > => same happens > > > > so I guess something more fishy happens :( > > What is wrong with > mvn -Prelease release:prepare > mvn -Prelease release:perform > ? > > > > The tag is wrong so followed the steps to have a commons release - the > link in previous thread - even if it looks broken to me. > > > Please closely follow the steps outlined in > http://commons.apache.org/releases/prepare.html > You will get a clean download page and proper RELEASE-NOTES then. > > Bye, Thomas. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > >
