Hi Olivier,
Can you help with me with the following points :
- release procedure (stage the mojo somewhere ?)
Rather easy going here:
http://mojo.codehaus.org/development/performing-a-release.html
We usually just deploy up-to-date snapshots and the site and have others
take a look. To get some more impressions about releasing here, just
browse the mail archives for "[VOTE]" topics.
- release number ? (As there are a lot of changes I prefer to call it
1.1-beta-1 or 2.0-beta-1 due to merge of the code with the plugin from
code.google).
That's most probably something Nicolas can best answer as he worked
lately on the plugin.
If the current codebase isn't in a stable condition to cut a fine
release, another option might be to create a branch from the last
release tag, merge in the bugfix, release the maintenance release and
delete the branch once trunk is ready again.
Benjamin
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
