On Wed, 2008-08-20 at 10:58 +0200, Stefano Bagnara wrote:
> Oleg Kalnichevski ha scritto:
> > Folks
> > 
> > It appears you have the entire project web site checked into the SVN
> > repository including Maven generated reports
> > 
> > http://svn.apache.org/repos/asf/james/site/trunk/www/mime4j/
> > 
> > The idea of storing javadocs, xrefs and similar seems somewhat bizarre
> > to me. I somehow fail to see any tangible benefits of doing so.
> 
> > Anyways,
> > I'll follow the standard procedure without asking too many questions.
> 
> I totally agree. On my turn I made questions.
> 
> Noel was the champion for this idea. From a recent discussion in infra I 
> understand that this was a requirement when people.a.o was not 
> backupped, but infra team agreed that this can be relaxed now.
> 
> I think we'll need a proposal/vote in order to change the current 
> practice, but I'm 100% +1 on a similar change.
> 

Does this really take a formal vote if no one raises any objections? 

> Committing generated html to svn seems to me a waste of time and svn 
> resources too!
> 
> > However I need to know how I should go about updating the content of the
> > web site in SVN? Am I supposed to svn del the outdated content and add
> > the new one or shall I try to commit diffs only? Given the fact that the
> > package structure has changed a lot this is likely to get quite messy.
> 
> I usually delete all of the content tree but .svn folders and then put 
> the new generated content there.
> The svn client usually automatically recognize the new/updated/missing 
> content and commit the add/delete/diff according to this.
> 
> BTW I see no big issues if you simply delete the old structure and 
> commit a full new tree. Change tracking is already done in the source xdocs.
> 

OK. Given the magnitude of changes in the package structure I guess it
is going to be easier to just svn del old reports and commit new ones in
their place.

Oleg


> When I add new content to the svn/www I also take care of using the 
> appropriate mime types so that the website preview will work directly by 
> browsing the svn server (before running the "svn up" on people).
> 
> Just ask if you need help,
> Stefano
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to