On 01/23/2011 01:16 PM, chemit wrote: > Hi, > > Yesterday I made a commit on the license-m-p and I never saw the commit > on the scm mailing list (rev 13433). > > Note that just after I do a commit on the ci-aggregator and this commit > was send to the scm mailing list (rev 13434). > > Paul made other commits on the module seen on the scm mailing list (rev > 13430 for example). > > Did I miss something ? > > I wonder also if it was normal that the license-m-p still stay with the > MOJO prefixed for his issues ? I noticed that other project had their > own prefix (example MEXEC for exec-m-p). > > Thanks for your replies. >
Hi Tony, Normally a plugin gets it's own jira project the 1.0 release [1]. Let's try to complete the merge this week, and then next week we can call for a 1.0 release and a new jira project. Does that sound good? [1]http://mojo.codehaus.org/development/performing-a-release.html#Preparing_for_the_First_Production_Release --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
