I don't see objections so I think we can start with that :-) 2014/1/9 Lukasz Lenart <lukaszlen...@apache.org>: > Infra doesn't have time to answer my questions [1] and it's a bit > annoying to wait with everything for them. So to not be dependent on > Infra I think we should move / create a user guide under website and > left Confluence / Wiki as a reference with more detailed informations. > Then the release process will only export the user guide which will be > included in packages. > > And to move things forward the best will be if we convert > https://cwiki.apache.org/confluence/display/WW/Getting+Started into > the user guide. > > [1] https://issues.apache.org/jira/browse/INFRA-6350 > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > 2013/12/16 Paul Benedict <pbened...@apache.org>: >> Years in the making. WOW! The Wiki documentation finally looks readable! >> >> >> On Mon, Dec 16, 2013 at 3:33 PM, Lukasz Lenart >> <lukaszlen...@apache.org>wrote: >> >>> I have removed custom css, the space looks better now :-) >>> >>> https://cwiki.apache.org/confluence/display/WW/Home >>> >>> >>> Regards >>> -- >>> Łukasz >>> + 48 606 323 122 http://www.lenart.org.pl/ >>> >>> 2013/12/16 Lukasz Lenart <lukaszlen...@apache.org>: >>> > FYI >>> > >>> > Confluence was upgraded to version 5 and there are some problems with >>> > editing pages. >>> > >>> > >>> > Regards >>> > -- >>> > Łukasz >>> > + 48 606 323 122 http://www.lenart.org.pl/ >>> > >>> > 2013/12/11 Lukasz Lenart <lukaszlen...@apache.org>: >>> >> One more thing: everything editable will be moved to struts-site (i.e. >>> >> the new plugin.md) to don't mess with things generated by Maven >>> >> >>> >> So the project source code will contain only source code and JavaDocs, >>> >> the rest will be outside it. >>> >> >>> >> >>> >> Regards >>> >> -- >>> >> Łukasz >>> >> + 48 606 323 122 http://www.lenart.org.pl/ >>> >> >>> >> 2013/12/11 Paul Benedict <pbened...@apache.org>: >>> >>> 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 >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >>> For additional commands, e-mail: dev-h...@struts.apache.org >>> >>> >> >> >> -- >> Cheers, >> Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
