Sounds good to me. The easier the better.

On Wed, Dec 11, 2013 at 2:06 AM, Lukasz Lenart <lukaszlen...@apache.org>wrote:

> Still thinking how to organise everything, maybe instead common
> /release/2.3.x and so on it'd be better to have something like that:
>
> /docs/latest -> latest development version
> /docs/2.3.x
> /docs/2.2.x
> ...
>
> and
>
> /apidocs/latest -> the same as above
> /apidocs/2.3.x
> /apidocs/2.2.x
> ...
>
> there be no more dedicated S2 subsite, everything will be put on the
> top, also Maven reports will be thrown away.
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/12/10 Lukasz Lenart <lukaszlen...@apache.org>:
> > Starting work on that - it must be resolved before next release comes
> out.
> >
> > My plan is to have two tasks:
> > 1. it will export pages from Confluence and will put them under /docs
> > 2. used after release to update JavaDocs (regenerate from tag) and
> > Docs (copy from /docs to /release/2.3.x/docs)
> >
> > WDYT?
> >
> > https://issues.apache.org/jira/browse/INFRA-6350
> >
> >
> > Regards
> > --
> > Łukasz
> > + 48 606 323 122 http://www.lenart.org.pl/
> >
> > 2013/11/6 Lukasz Lenart <lukaszlen...@apache.org>:
> >> 2013/11/5 Paul Benedict <pbened...@apache.org>:
> >>> I usually find it a life-saver to see the docs of previous versions.
> Not
> >>> everyone upgrades and it's impossible to compare latest syntax and
> features
> >>> to what was before. I think we definitely need to keep the docs of the
> >>> previously published versions around.
> >>
> >> But you meant to have the Draft docs and the latest released version?
> >> Or as it is now, version per branch (2.3, 2.2, 2.1, etc) ?
> >>
> >>> If you don't want to do that, then I think the latest docs need to
> contain
> >>> some sort of history on feature changes/upgrades.
> >>
> >> Hm... I think it's easier to keep few versions ;-)
> >>
> >>
> >> Regards
> >> --
> >> Łukasz
> >> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>


-- 
Cheers,
Paul

Reply via email to