Thank you for your feedback, Hervé.
I've opened three jira issues to document changes that went into
r1185951. Looking at svn log I believe all user-visible changes since
alpha-1 have corresponding jiras now.
Anything else you think will make release review easier to proceed?
--
Regards,
Igor
On 12-05-20 10:06 AM, Hervé BOUTEMY wrote:
Hi Igor,
Yes, the release process is the basic way to go: I can help if you need.
The hard part IMHO will be to have people being sufficiently confident to vote
on
the content, since this is a "hard-core" component :)
I had a look at actual site [1]: looks promising, with actual release being
2.0-alpha-1
Then I looked at Jira and found only one issue fixed [2]: uh, really only one?
From fast svn log look, I found r1185951 with a nice comment: seems like this
one deserves at least one Jira issue. Other ones?
I'll take a deeper look at this component later, but IMHO, such information on
changes in this release is the most important thing to do to have a rapid
vote.
Regards,
Hervé
[1] http://maven.apache.org/plugin-testing/
[2]
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&version=15988
Le dimanche 20 mai 2012 09:44:16 Igor Fedorenko a écrit :
Heh. I finally got some time to follow up on my proposal to make mvn 3.x
compatible plugin-testing the new trunk and move mvn 2.x code to a
branch [1]. I would like to make plugin-testing 2.0 release now, but not
sure about the release process. Can I just stage a release and call a
vote or there is more to it?
[1]
http://mail-archives.apache.org/mod_mbox/maven-dev/201110.mbox/%3C4E9E3CDF.4
010606%40ifedorenko.com%3E
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
