Salut mon ami! > > For the specific case of OnamiSuite, I wonder if I would only commit the > doc but not publish the site and wait the release. >
we never discussed about a site publication policy, but I agree with you that, once a component has been released (like test, in that case), site re-deployment makes sense only when releasing a new version. Feel free to cut a new RC for test if you want, I'd be more than pleased to adopt the "release early and often" practice!!! :) A très bientôt, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Mar 15, 2013 at 11:36 AM, Eric Charles <e...@apache.org> wrote: > Thx Simo, > > For the specific case of OnamiSuite, I wonder if I would only commit the > doc but not publish the site and wait the release. > > I guess the latter is preferable. > > Can you confirm? > > Thx, Eric > > On 14/03/2013 19:37, Simone Tripodi wrote: >> Salut mon ami, >> >>> @Simo >>> >>> Any other doc than [1] to use the scm-plugin? >>> >>> I must have missed something, if I remember well a few months ago, we were >>> not using the maven-scm-publish-plugin? >> >> everybody has enough karma to publish the sites, just run >> >> `mvn site-deploy -Dusername=<LDAP.username> -Dpassword=<LDAP.password>` >> >> if you have a multi-module project, instead, run >> >> `sh deploySite.sh -Dusername=<LDAP.username> -Dpassword=<LDAP.password>` >> >> it should be already included in the `release how to` page - please >> let me know if it works for you! >> >> HTH, à très bientôt, >> -Simo >> >> http://people.apache.org/~simonetripodi/ >> http://simonetripodi.livejournal.com/ >> http://twitter.com/simonetripodi >> http://www.99soft.org/ >>
