Move Pluto site project structure outside trunk to a new sub site project of
the main Portals site project
----------------------------------------------------------------------------------------------------------
Key: PLUTO-563
URL: https://issues.apache.org/jira/browse/PLUTO-563
Project: Pluto
Issue Type: Task
Components: documentation
Affects Versions: 2.0.0
Reporter: Ate Douma
Assignee: Carsten Ziegeler
Fix For: 2.0.0
As discussed elaborately on [email protected] and in further detail
described in PORTALS-10 and partly repeated here:
For Jetspeed, we've already discussed and decided to move *all* our project
documentation outside the release cycle and thus outside the
trunk/tags/branches structure for each version.
[...] project documentation isn't "frozen" when a release is done: usually
the documentation trails behind (a bit or a bit more) and additional
improvements
will come in for an *released* version as well as for latest/trunk based
development.
The plan is to provide one master portals site folder with each subproject
having its own site module (or independent) folder underneath.
The project specific site module/project(s) can extend the main portals site
project and thereby automatically inherit the main developers information
and/or extend this specifically for the project if wished for.
Based upon the above, the proposal is moving the Pluto site project structure
(actually, there are currently 2, see also PLUTO-492) to /portals/site/pluto.
Once moved, the current site then probably best be split up in two sub sites:
/portals/site/pluto/pluto-1 and /portals/site/pluto/pluto-2 as the current
content is still mostly Pluto 1.x based and needs extensive updating for Pluto
2.x
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
