On Tue, Apr 5, 2011 at 14:07, Thomas Mortagne <[email protected]> wrote:
On Tue, Apr 5, 2011 at 14:02, Vincent Massol <[email protected]> wrote:
On Apr 5, 2011, at 1:52 PM, Thomas Mortagne wrote:
On Tue, Apr 5, 2011 at 12:51, Vincent Massol <[email protected]> wrote:
On Apr 4, 2011, at 3:04 PM, Vincent Massol wrote:
Hi,
After brainstorming with Thomas, Sergiu and Fabio we came to the following idea:
Proposal =======
* Don't have top level extension git repositories and instead put all extensions/modules in the top level platform repository * This means releasing all modules/extensions under the *same* version (the platform version)
^^^^^^^^ This is the important part!
Pros ====
* Much simpler release process * Much simpler JIRA organization (1 project instead of 50 or so) * Much simpler for the user: simpler to log a new issue in jira + they'll know what version of a module they're using vs having to guess that XE 3.0 uses the Lucene plugin v 1.45) and for contributors
Directory org ==========
platform/ |_ modules/ |_ xwiki-platform-search/ |_ xwiki-platform-search-lucene/ |_ xwiki-platform-search-application/ |_ xwiki-platform-url/ |_ xwiki-platform-skin-colibri/ |_ xwiki-platform-wysiwyg/ |_ ... |_ tools/ |_ distribution/
Details:
* Modules contains a flat list of directories, each directory representing a "feature". Everything corresponding to a feature is under that feature's directory, independently of the underlying technologies used (be it plugins, components, xar, etc) * Maven modules previously located in platform/web are moved in platform/modules. Except platform/web/standard which goes in platform/distribution. wysiwyg modules go in xwiki-platform-wysiwyg/ (we need to decide if gwt-dom and gwt-user modules go in there too or if we want to have a xwiki-platform-gwt module - Marius?)
To be more specific (thanks to Anca's question), I'm proposing:
platform/modules/ |_ xwiki-platform-templates/ |_ xwiki-platform-resources/ |_ xwiki-platform-distribution/ <-- generate the WAR
The reason for having xwiki-platform-distribution inside modules is because it should be released together with all modules. If we don't do this we need an additional directory level, for example:
I don't understand this argument actually, I tough the whole repository was released at once, tools included since in git branches and tags are at the whole repository level. If tools don't have the same version then they should have their own repository each.
Yes my bad you're right.
Tools have their own git repo and so does xwiki-platform-modules.
Now the question is whether we want a special repo for distribution or should we put inside xwiki-platform-modules and thus consider it as a module.
WDYT?
1 for same repo
s/1/+1/
I'm open to both although having a repo for 1 file sounds maybe a bit too much... ;)
Thanks -Vincent
platform/ |_ core |_ modules |_ distribution |_ tools
which is not very nice at all.
The other option is to move out tools but there's no better place than platform since it's related to plartform.
WDYT?
Thanks -Vincent
Migration details =============
* Change the current org in git * Move several jira projects to retired * Modify platform jira project to have one jira component per feature (ie per platform/modules module). Note that since the old xwiki-core contains lots of stuff I propose to have one jira components for each "feature" it contains. For example for anything related to the model it would go in the "model" jira component. For things going in the user management it would go in a "user and group" component, etc. I'll make a proposal for the full list of jira components later on if this vote is passed. * Future: decide if we keep extensions.xwiki.org and if so what we put in there (maybe just user extensions and move platform features in platform.xwiki.org).
Here's my +1 (meaning I'll help perform this move)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne