2017-05-16 16:44 GMT+03:00 Rémy Maucherat <r...@apache.org>: > 2017-05-16 14:43 GMT+02:00 Konstantin Kolinko <knst.koli...@gmail.com>: > >> 2017-05-16 14:56 GMT+03:00 Rémy Maucherat <r...@apache.org>: >> > 2017-04-30 11:10 GMT+02:00 jean-frederic clere <jfcl...@gmail.com>: >> > >> >> Hi, >> >> >> >> I will try to tag and propose taglibs-standard-1.2.6 for release >> >> tomorrow, any comments? >> >> >> > >> > Since this didn't happen, I plan to add a pre_126_bz60950 tag instead. >> > Would that be acceptable ? >> >> I'd prefer more explicit "1.2.6" in the name. >> >> Maybe just name it a "release candidate", e.g.: >> https://svn.apache.org/repos/asf/tomcat/taglibs/standard/tag >> s/taglibs-standard-1.2.6-RC1/ >> >> Ok, I will probably do that. I could attempt to make the real 1.2.6 > release, but the RELEASING.txt looks incomplete (pom.xml would presumably > need to be updated, CHANGES.txt as well), and I would have trouble making > the binaries available and signing them. I would of course feel a lot more > optimistic if I was at ApacheCon with a lot of "support" people around :)
>From commits history, I think that the pom files are updated automatically by maven-release-plugin. That is "mvn release:prepare" step in RELEASING.txt. http://maven.apache.org/maven-release/maven-release-plugin/ CHANGES.txt - yes, it has to be updated, or at least reviewed that all changes are listed there. https://svn.apache.org/viewvc?view=revision&revision=1665588 Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
