Hi,
On Mon, Jan 26, 2009 at 6:50 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi,
In order to better organize our SVN/JIRA I propose to implement the
following refactoring:
1) Release all platform modules simultaneously. Rationale: make it
easy to release and to ensure all versions work together.
2) Remove notion of core. Keep only notion of platform. It's up the
products/projects to hand pick whatever components they need from the
platform.
3) Move in SVN platform/core/* to platform/components/ except for
platform/core/xwiki-core which is moved to platform/xwiki-core/ (while
waiting to be split into components)
4) in JIRA create a new category named "XWiki Platform Components" and
have one jira project for each top level module in platform/
components/. Move the "XWiki Core" jira project from the "XWiki Core
&
Products" category to the "XWiki Platform Components" category.
5) In JIRA rename "XWiki Core & Products" to "XWiki Top Level
Projects"
6) Create some tools on
dev.xwiki.org to help with releases (using
swizzle jira). Namely:
- a tool to automatically add a version to a set of jira projects
(we'll need to do that to manipulate all jira projects in "XWiki
Platform Components" all together). Same to release a version
WDYT?
Note that I've tried imagining keeping all platform modules under the
same jira project but I've ruled it out since that doesn't work well
for several reasons:
* there's no notion of sub-components in jira which would mean
creating hundreds of jira components...
* we already have some modules in separate jira projects
* it may happen that we may want to occasionally release a module
separately in the future for some reason
Sounds good. I have this small question about /platform, why only some sub
dirs use "xwiki-" prefix? like xwiki-applications, xwiki-plugins and
xwiki-tools while the rest is simply core, gwt, pom, skins and web? I'm just
curious....
Thanks.
- Asiri