On 5/5/07, Leo Simons <[EMAIL PROTECTED]> wrote:
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) cr
Leo Simons wrote:
On May 5, 2007, at 7:55 PM, Michael Wechner wrote:
what about a CMS with a workflow, which would sit on top SVN
accessing both branches (staging resp. draft and live) and hence
would allow devs still accessing it through other SVN clients and
also allow updating the live
On May 5, 2007, at 7:55 PM, Michael Wechner wrote:
what about a CMS with a workflow, which would sit on top SVN
accessing both branches (staging resp. draft and live) and hence
would allow devs still accessing it through other SVN clients and
also allow updating the live site as static SVN u
Leo Simons wrote:
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.apa
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/in
