Hi, I would like to test Maven Plugins Release Candidates. I know there is a brief guide https://maven.apache.org/guides/development/guide-testing-releases.html But I think this is not very complete and/or it is outdated.
The summary of the guide is to run mvn verify For instance this is not true for Surefire. Can someone explain better how is it expected to run a check on an RC ? In other Apache projects that I know/work on usual checks are: - try to build and run tests on the propostes source artifacts. - apache-rat/licensing issues - check signatures/shasums.. - check proposed maven artifacts Usually voters when the give their '+1' add an explanation about the tests the performed on the RC, I see this is not very common practice in Maven VOTE threads. Second question, in Maven what is really 'released' ? Are you releasing the SOURCE ZIP ? or something else ? As far as I know in Apache we are 'releasing' the source code and we are providing binaries for convenience to users. I understand that Maven is somehow a very special case. My questions are just to understand better in order to give a more significant contribution to the project, I am pointing out problems. Thank you all for carrying on Maven Project ! Cheers Enrico --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
