You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Oleg Kalnichevski <ol...@apache.org> on 2008/08/19 23:06:19 UTC
Publishing updates to the project web site
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.
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.
Please advise.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Publishing updates to the project web site
Posted by Stefano Bagnara <ap...@bago.org>.
Robert Burrell Donkin ha scritto:
> On Thu, Aug 21, 2008 at 8:28 AM, Stefano Bagnara <ap...@bago.org> wrote:
>> Oleg Kalnichevski ha scritto:
>>> 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?
>> No. History proved that my "formal ways" don't work here, so you have for
>> sure better chance using any different way ;-)
>
> do infrastructure now guarantee that /www/james.apache.org/ is backed up?
Read the recent "Automating parts of the web site publishing process" on
infrastructure@a.o list.
Jukka asked to relax the point that generated content must be committed
to svn, Joes replied that we now have good backups and the requirement
can be relaxed.
From my understanding the requirement is now that what we publish is
generated from svn committed content so that we review any change.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Publishing updates to the project web site
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Thu, Aug 21, 2008 at 8:28 AM, Stefano Bagnara <ap...@bago.org> wrote:
> Oleg Kalnichevski ha scritto:
>>
>> 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?
>
> No. History proved that my "formal ways" don't work here, so you have for
> sure better chance using any different way ;-)
do infrastructure now guarantee that /www/james.apache.org/ is backed up?
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Publishing updates to the project web site
Posted by Stefano Bagnara <ap...@bago.org>.
Oleg Kalnichevski ha scritto:
> 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?
No. History proved that my "formal ways" don't work here, so you have
for sure better chance using any different way ;-)
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Publishing updates to the project web site
Posted by Oleg Kalnichevski <ol...@apache.org>.
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: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Publishing updates to the project web site
Posted by Stefano Bagnara <ap...@bago.org>.
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.
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.
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org