Yes I supposed last few commits won't be able undo other way. Next time this will not happen, we will make "safe" commitments first.
What branches were introduced? The apache branch had master and surefire-954-test only. The whole problem was with maven-release-plugin:2.2.1 and some other with SSLv3 and not-generated MD5 in Nexus repository. We were unable to deploy release versions. Thus the team decided to use the latest maven-parent and apache POM which means that now we use maven-release-plugin:2.5.1 working with git client 1.9.5. Since we have quite urgent fixes in surefire I will call a vote. The people reported next two major issues only, so we have 98 major, and after surefire 2.19 the number of issues should decrease again. Then we will have let's say more stable code and API to prepare for surefire 3.0. Since the rest of the issues are a lot of features, after fixing them in 2.19, we will get better imagination of what API the people would like to customize in 3.0 instead of plugin's pom configuration. ----- BR, tibor17 -- View this message in context: http://maven.40175.n5.nabble.com/problem-to-git-reset-hash-at-git-wip-us-apache-org-repos-asf-tp5820756p5820822.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
