Hi All,
I agree with Glenn's concerns. However as Pascal pointed out we were
forced by the Apache board to move to their new website infrastructure.
Clay researched that and came up with the current solution which works
well for the website, but means the releases don't include documentation.
In my mind that is a shame, but I don't know what the solution is.
Someone would need to develop a way to copy the documentation for the
project being built from the new location in SVN into the release
artifacts at build time. I suggest we log a Jira for that so this isn't
forgotten.
Thanks,
Chris
On 07/02/2013 08:19, Pascal Sancho wrote:
Hi,
IIRC, CMS migration was an Apache requirement.
So, I don't think that undoing that is possible.
By the way, we can start a new discussion on how to separate website
Vs product documentation, the latter coming back to product project.
2013/2/6 Glenn Adams gl...@skynav.com:
On Wed, Feb 6, 2013 at 8:43 AM, Pascal Sancho psancho@gmail.com wrote:
Hi,
2013/2/6 Glenn Adams gl...@skynav.com:
On Wed, Feb 6, 2013 at 4:29 AM, Pascal Sancho psancho@gmail.com
wrote:
Hi,
Since XCG website repository includes now all XCG sub-projects, there
should be a Jira entry for that.
By include all do you mean includes all documentation for XCG
sub-projects?
Yes, this is a fact. The whole XCG CMS, with sub-projects parts, is
now in its own SVN project, outside XCG projects sources.
Can these be migrated back into their own original repositories? I don't
recall a discussion of the present organization when we started the move to
CMS.
-
To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: general-h...@xmlgraphics.apache.org
