[Yanel-dev] [Fwd: [suggestion] making documentation management
more lightweight]
Michael Wechner
michael.wechner at wyona.com
Sat May 5 23:30:24 CEST 2007
Michael Wechner wrote:
> Leo Simons proposed the following workflow for documentation on the
> incubator project. Maybe we can help with Yulup and Yanel. WDYT?
I guess we would have to get started here
http://incubator.apache.org/guides/website.html
and see how we could make a realm out of this and also see if we would need
special resource re Anakia and Velocity.
Cheers
Michi
>
> -------- Original Message --------
> Subject: [suggestion] making documentation management more
> lightweight
> Date: Sat, 5 May 2007 17:10:40 +0200
> From: Leo Simons <mail at leosimons.com>
> Reply-To: general at incubator.apache.org
> To: general at incubator.apache.org
>
>
>
> Jo!
>
> The whole jira-patch-commit workflow for the documentation seems
> annoying. At least it annoys me -- in particular the patches don't
> show up in my email so I have to visit jira which I try and avoid as
> much as possible :-).
>
> Suggestions:
>
> 1) create
>
> http://svn.apache.org/repos/asf/incubator/public/staging
>
> writeable by *all* committers
>
> svn cp http://svn.apache.org/repos/asf/incubator/public/trunk \
> http://svn.apache.org/repos/asf/incubator/public/staging
> vi infrastructure/trunk/subversion/authorization/asf-authorization
> svn commit infrastructure/trunk/subversion/authorization/asf-
> authorization
>
> 2) create an svn:externals on
>
> http://svn.apache.org/repos/asf/incubator/public/trunk/site- publish
>
> like this
>
> website-staging http://svn.apache.org/repos/asf/incubator/
> public/staging/site-publish
>
> so that you can see the work-in-progress at
>
> http://incubator.apache.org/website-staging/
>
> 3) instead of sending documentation patches, people who are helping
> with the documentation work on the staging branch
>
> 4) set up svnmerge.py for staging/ and trunk/
> * see http://www.orcaware.com/svn/wiki/Svnmerge.py
> * make sure to block the revision from step #2!
>
> 5) propose documentation changes on the mailing list
> * get diffs
>
> cd incubator/trunk
> svnmerge.py --bidirectional diff > ~/staging-diffs.txt
> # or use -r to get only a few revisions
>
> * send diff to mailing list for discussion and lazy
> consensus approval
>
> 6) merge
>
> cd incubator/trunk
> svnmerge.py --bidirectional avail
> svnmerge.py --bidirectional # or use -r12345,...
> svn commit -F svnmerge-commit-message.txt
> cd ../staging
> svnmerge.py
> svn commit -F svnmerge-commit-message.txt
>
> 7) rejoice at the lightweight workflow, which also survives Robert's
> laptop sinking to the bottom of the sea!
>
>
> cheers,
>
>
> Leo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe at incubator.apache.org
> For additional commands, e-mail: general-help at incubator.apache.org
>
>
>
>
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner at wyona.com michi at apache.org
+41 44 272 91 61
More information about the Yanel-development
mailing list