On 2011-08-13, Gavin McDonald wrote: >> -----Original Message----- >> From: Stefan Bodewig [mailto:[email protected]] >> Sent: Sunday, 14 August 2011 12:29 AM
>> On 2011-08-13, Gavin McDonald wrote: >>> Remember that ci.apache.org is great for building the site within a >>> few minutes of your commits and is therefore a great staging/preview >>> tool, but one should then run mvn site-deploy locally to update the >>> main website with these new improvements. >> I had deliberately not done that since much of what I have added only >> applies to trunk and not to any released version of RAT. My plan was to >> deploy the site after the 0.8 release. > Aha, of course, but then I see an issue. I had my own changes to the website > and wanted to get them up right away. How can I mvn deploy on my changes > whilst leaving your changes unpublished? I can't as far as I can tell. This is true. For one I didn't expect anybody else to have updates as well - it's not as if we had been changing the site regularly - and second I thought the next release would be pretty close when I made those changes. I don't think any harm has been done. The Antlib has gone from completely undocumented to docs that contain things not available in any released version but marked with "since RAT 0.8". People will figure this out. > What we should have perhaps is like httpd project and others, an area for > documentation of the current release; and an area where we can add docs > for trunk. We should do so if this (having docs for trunk that don't apply to a release) happens more often. Right now I suspect it's a one time issue. Stefan
