As discussed elaborately on email@example.com 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
|Workflow||Default workflow, editable Closed status [ 12565165 ]||jira [ 12586129 ]|
|Workflow||jira [ 12463160 ]||Default workflow, editable Closed status [ 12565165 ]|
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Fixed [ 1 ]|