You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-dev@james.apache.org by Stefano Bagnara <ap...@bago.org> on 2006/07/27 12:44:24 UTC
How to support multiple server releases on the website
I still have to study how to correctly publish multiple james versions
(2.2, 2.3, trunk) and how to backport site generation stuff to 2.2 and
2.3 in order to generate correct reports for them.
Maybe I should create a branch for the creation of "Server 2.2" and I
should upgrade the 2.3 branch with the current trunk work about the site
(pom + site folder)
Furthermore what would be the better navigation for this stuff?
I identified this options:
1) Add them in the top bar so that we have:
JAMES Project | Server 2.2 | Server 2.3 | Server Trunk | jSPF | Mime4J
| JSieve
2) Add them in the Server page adding a common menu at the top of the
left column:
http://james.apache.org/server/index.html
Add a menu named "Releases" and including:
"Server 2.2.0"
"Server 2.3.0"
"Server Trunk"
I'm not satisfied by this 2 solutions, because the first is too much
intrusive and in the second it will not be so clear which version you
are browsing.
Maybe I should also create version specific Logos for the server
projects so that the logo will make it more clear.
Any feedback is welcome as I really don't know how to proceed.
Stefano
PS: the reports of the currently deployed 2.3B version are the one from
trunk and not from the 2.3 branch.
RE: How to support multiple server releases on the website
Posted by "Noel J. Bergman" <no...@devtech.com>.
Danny Angus wrote:
> I think we should just distribute the docs with the code for all
> versions and only publish the current stable version's docs and
> publish reports for the trunk
I think that it is better to have the docs online, similar to the HTTP
Server's approach. Let's google find them, gives us content to be searched
(and ranked), allows users to more easily find what they want for whichever
version(s).
--- Noel
Re: How to support multiple server releases on the website
Posted by Stefano Bagnara <ap...@bago.org>.
I agree with you, but IIRC we didn't bundle docs with 2.2.0 and we are
not including docs in the current 2.3.0RC1.
Are we ready to remove the whole 2.2.0 references as soon as we publish
2.3.0 final?
I think we can't support too many versions so I would be happy with
this, and I also think that the trunk site generation could be part of a
continuos integration configuration and could be published even outside
from the official site (e.g: people.apache.org).
What do other thinks about this?
Danny Angus wrote:
> I think we should just distribute the docs with the code for all
> versions and only publish the current stable version's docs and
> publish reports for the trunk
>
> d.
>
> On 27/07/06, Stefano Bagnara <ap...@bago.org> wrote:
>> I still have to study how to correctly publish multiple james versions
>> (2.2, 2.3, trunk) and how to backport site generation stuff to 2.2 and
>> 2.3 in order to generate correct reports for them.
>>
>> Maybe I should create a branch for the creation of "Server 2.2" and I
>> should upgrade the 2.3 branch with the current trunk work about the site
>> (pom + site folder)
>>
>> Furthermore what would be the better navigation for this stuff?
>>
>> I identified this options:
>> 1) Add them in the top bar so that we have:
>> JAMES Project | Server 2.2 | Server 2.3 | Server Trunk | jSPF | Mime4J
>> | JSieve
>>
>> 2) Add them in the Server page adding a common menu at the top of the
>> left column:
>> http://james.apache.org/server/index.html
>> Add a menu named "Releases" and including:
>> "Server 2.2.0"
>> "Server 2.3.0"
>> "Server Trunk"
>>
>> I'm not satisfied by this 2 solutions, because the first is too much
>> intrusive and in the second it will not be so clear which version you
>> are browsing.
>>
>> Maybe I should also create version specific Logos for the server
>> projects so that the logo will make it more clear.
>>
>>
>> Any feedback is welcome as I really don't know how to proceed.
>>
>> Stefano
>>
>> PS: the reports of the currently deployed 2.3B version are the one from
>> trunk and not from the 2.3 branch.
Re: How to support multiple server releases on the website
Posted by Norman Maurer <nm...@byteaction.de>.
Am Donnerstag, den 27.07.2006, 14:24 +0200 schrieb Stefano Bagnara:
> ould be part of a
> continuos integration configuration and could be published even
> outside
> from the official site (e.g: people.apache.org).
>
> What do other thinks about this?
Re: How to support multiple server releases on the website
Posted by Norman Maurer <nm...@byteaction.de>.
Am Donnerstag, den 27.07.2006, 14:24 +0200 schrieb Stefano Bagnara:
> I agree with you, but IIRC we didn't bundle docs with 2.2.0 and we are
> not including docs in the current 2.3.0RC1.
We should include the javadocs in the src for sure.. At the moment the
docs are stored under the www folder in the src dist. I think we should
"correct" the directory name
>
> Are we ready to remove the whole 2.2.0 references as soon as we publish
> 2.3.0 final?
+1
>
> I think we can't support too many versions so I would be happy with
> this, and I also think that the trunk site generation could be part of a
> continuos integration configuration and could be published even outside
> from the official site (e.g: people.apache.org).
>
> What do other thinks about this?
+1 Such a "automatic" generation whould allow us to easly been up to
date with the site..
>
> Danny Angus wrote:
> > I think we should just distribute the docs with the code for all
> > versions and only publish the current stable version's docs and
> > publish reports for the trunk
> >
> > d.
> >
> > On 27/07/06, Stefano Bagnara <ap...@bago.org> wrote:
> >> I still have to study how to correctly publish multiple james versions
> >> (2.2, 2.3, trunk) and how to backport site generation stuff to 2.2 and
> >> 2.3 in order to generate correct reports for them.
> >>
> >> Maybe I should create a branch for the creation of "Server 2.2" and I
> >> should upgrade the 2.3 branch with the current trunk work about the site
> >> (pom + site folder)
> >>
> >> Furthermore what would be the better navigation for this stuff?
> >>
> >> I identified this options:
> >> 1) Add them in the top bar so that we have:
> >> JAMES Project | Server 2.2 | Server 2.3 | Server Trunk | jSPF | Mime4J
> >> | JSieve
> >>
> >> 2) Add them in the Server page adding a common menu at the top of the
> >> left column:
> >> http://james.apache.org/server/index.html
> >> Add a menu named "Releases" and including:
> >> "Server 2.2.0"
> >> "Server 2.3.0"
> >> "Server Trunk"
> >>
> >> I'm not satisfied by this 2 solutions, because the first is too much
> >> intrusive and in the second it will not be so clear which version you
> >> are browsing.
> >>
> >> Maybe I should also create version specific Logos for the server
> >> projects so that the logo will make it more clear.
> >>
> >>
> >> Any feedback is welcome as I really don't know how to proceed.
> >>
> >> Stefano
> >>
> >> PS: the reports of the currently deployed 2.3B version are the one from
> >> trunk and not from the 2.3 branch.
>
> !EXCUBATOR:1,44c8b0af43382746719482!
bye
Norman
Re: How to support multiple server releases on the website
Posted by Danny Angus <da...@gmail.com>.
I think we should just distribute the docs with the code for all
versions and only publish the current stable version's docs and
publish reports for the trunk
d.
On 27/07/06, Stefano Bagnara <ap...@bago.org> wrote:
> I still have to study how to correctly publish multiple james versions
> (2.2, 2.3, trunk) and how to backport site generation stuff to 2.2 and
> 2.3 in order to generate correct reports for them.
>
> Maybe I should create a branch for the creation of "Server 2.2" and I
> should upgrade the 2.3 branch with the current trunk work about the site
> (pom + site folder)
>
> Furthermore what would be the better navigation for this stuff?
>
> I identified this options:
> 1) Add them in the top bar so that we have:
> JAMES Project | Server 2.2 | Server 2.3 | Server Trunk | jSPF | Mime4J
> | JSieve
>
> 2) Add them in the Server page adding a common menu at the top of the
> left column:
> http://james.apache.org/server/index.html
> Add a menu named "Releases" and including:
> "Server 2.2.0"
> "Server 2.3.0"
> "Server Trunk"
>
> I'm not satisfied by this 2 solutions, because the first is too much
> intrusive and in the second it will not be so clear which version you
> are browsing.
>
> Maybe I should also create version specific Logos for the server
> projects so that the logo will make it more clear.
>
>
> Any feedback is welcome as I really don't know how to proceed.
>
> Stefano
>
> PS: the reports of the currently deployed 2.3B version are the one from
> trunk and not from the 2.3 branch.
>
>
RE: How to support multiple server releases on the website
Posted by "Noel J. Bergman" <no...@devtech.com>.
Danny Angus wrote:
> a) we go for even more web-site bloat, and risk discrepancies between
> docs and users' versions by having three versions of docs, namely
> 1 current HEAD
> 2 current stable
> 3 previous stable
I'd go for this one. At least the first two.
> b) we bundle the docs using up everyones bandwidth, mirrors' storage
> and have to solve the build problem of versions, repositories and
> diretory structures.
Worst case, I suppose that we can reference the docs online via SVN, e.g.,
http://svn.apache.org/repos/asf/james/site/trunk/www/index.html,
particularly if we fix all of the intra-project URLs to be relative.
--- Noel
Re: How to support multiple server releases on the website
Posted by Danny Angus <da...@gmail.com>.
On 28/07/06, Noel J. Bergman <no...@devtech.com> wrote:
...all that stuff I just snipped...
Ok, to bring two threads together the choice is...
a) we go for even more web-site bloat, and risk discrepancies between
docs and users' versions by having three versions of docs, namely
1 current HEAD
2 current stable
3 previous stable
or
b) we bundle the docs using up everyones bandwidth, mirrors' storage
and have to solve the build problem of versions, repositories and
diretory structures.
I can see benefits (yes I can!) in both and also drawbacks, what do you think?
d
RE: How to support multiple server releases on the website
Posted by "Noel J. Bergman" <no...@devtech.com>.
Stefano Bagnara wrote:
> I still have to study how to correctly publish multiple james versions
> (2.2, 2.3, trunk) and how to backport site generation stuff to 2.2 and
> 2.3 in order to generate correct reports for them.
Suggestion: ${component}/docs/${rev}/
That would match httpd.apache.org/docs/{1.3, 2.0, 2.2, trunk}, and is what I
believe we want.
> dd a menu named "Releases" and including:
> "Server 2.2.0"
> "Server 2.3.0"
> "Server Trunk"
+1
See the HTTP Server site, which does it.
--- Noel