Thanks for pointing this out. To me, it means one thing: release more often. The way I read it, publishing is not forbidden per se, but rather advertising. That's consistent with GitHub repo clones being available, but without "clone me at GitHub" ribbons.
On the other hand, I rewrote the manual (which was still talking about CVS), suggesting that the proper way to propose code changes would be a GitHub PR rather than an archive uploaded to Bugzilla, so please correct me if I'm wrong before Ant 1.10.3 gets released... Gintas 2018-03-17 13:07 GMT+01:00 Jaikiran Pai <jai.forums2...@gmail.com>: > I was about to send a mail to the user mailing list about the Ant nightly > job which publishes the daily snapshots, so that they can test some bug > fixes and new features (JUnit 5 in particular). However, I happened to read > the Apache release policy[1] which states regular users aren't even meant > to know about such snapshots. > > That seems a bit too restrictive, especially for open source projects. Is > that documentation being followed and if it is, then I guess I shouldn't be > letting the user@ mailing list know about these snapshots nor ask them to > test out the new feature? > > After reading that policy, I'm starting to wonder if the Jenkins job > should even publish these snapshots. > > [1] http://www.apache.org/legal/release-policy.html#publication > > -Jaikiran > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
