ATM, we can not stage the project b/c codehaus webdav for deployment and mav-stage-plugin is not able to merge 2 webdav repos. ( it can only merge http source to scp target )
At release time, we just deploy the site and for review and hope to release cycle is short. I have seen ppl depoy snapshot site to a private host for review. However, due to lacking of a staging repo, I dont see a reason not to deploy it and have a status page to let user aware what is going on. -D On Sun, Sep 14, 2008 at 3:32 AM, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > Stephen Connolly wrote: >> I'm wondering, >> >> what is the best practice for deploying the site for the next version of >> a plugin on mojo. >> >> I know that is always annoys me when I see the next -SNAPSHOT build as >> the site with some cool new feature and I give it a whirl only to find >> that it does not work (because it's a -SNAPSHOT version and has not been >> pushed to central) >> >> So, while working on some cool new features for versions-maven-plugin, >> what _should_ I do with regard to pushing the site? >> >> This is also really a question when it comes to calling for a vote to >> release the next version as we don't really seem to stage plugin >> releases on mojo (or maybe we do and I just don't know about it)... >> since it would seem that we just blast the current site with the next >> version and if the vote fails we've not really got a good way to roll back. > > It depends a bit on how much documentation you really have. If you're > pre beta/1.0 I would mark all relevant parts of the documentation with > the version they're valid from. I would also remove notes for older > alpha releases as no-one should be using them. When doing the 1.0 > release the entire site should be cleaned up so that only documentation > relevant for 1.0 and up is online. > > -- > Trygve > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
