13 May
2007
13 May
'07
7:54 a.m.
I totally agree.
+1
On 5/12/07, Vincent Massol <vincent(a)massol.net> wrote:
I don't think I ever received any comment/input on
this proposal.
Does it mean everyone agrees with it? :)
Barring any negative input I'll start implementing these next week.
Thanks
-Vincent
On Apr 24, 2007, at 2:12 PM, Vincent Massol wrote:
Sergiu
--
http://purl.org/net/sergiu
Hi,
We need to organize a bit better the different JIRA projects. Right
now there are:
- XWiki
- XWiki Applications
- XWiki Clients
We need to clean the XWiki Applications and XWiki Clients projects.
For this we need to define a strategy for where to put xwiki
plugins, applications, etc.
Here are some facts:
* A JIRA project has the same versions for all components. This
means one JIRA project per release lifecycle.
And here's my proposal in term of JIRA projects:
* "XWiki":
- We put everything here that is tied to the XWiki Core release
(1.0 RC2, 1.1 B1, etc). Right now there are several plugins that
are still tied to the XWiki release (all the core plugins). So they
should go in there for now. When we'll move out the plugins later
on, we will then move their JIRA issues.
* "XWiki Applications":
- We remove this JIRA project
* "XWiki Default Wiki":
- We create this new JIRA project. Corresponds to xwiki-
applications/wikis/default.
- We move all issues from current XWiki JIRA project that have a
"Default Wiki" component to it.
- We define a version scheme for it. I propose to use the same
versions as for XWiki core for now. But in the future it'll be
possible to release the default wiki independently of XWiki Core.
- We create components for the various XWiki applications that we
haven't separated from the xwiki-applications/wikis/default yet
(i.e. all except the Panels which has been moved out)
* "XWiki Panels Application":
- We create this JIRA project. Corresponds to xwiki-applications/
xarlets/panels
- We define a version scheme for it. I propose to use the same
versions as for XWiki core for now. But in the future it'll be
possible to release the default wiki independently of XWiki Core.
- We release the panels application on the forge instead of just
releasing it as an attachment to http://www.xwiki.org/xwiki/bin/
view/Code/PanelsApplication. We'll continue to reference the
download from that page but it'll point to OW's forge. We ensure
it's also referenced from the main Download page on xwiki.org
* "XWiki Selenium Application":
- We create this JIRA project. Corresponds to xwiki-applications/
xarlets/selenium
- We define a version scheme for it. I propose to start at 0.1 as
it's still early stuff
- Release it as 0.1 on the forge and, as above, modify xwiki.org
to point to it (from the code zone).
* "XWiki <plugin name> Plugin":
- Where <plugin name> is: "Adwords", "Alexa", "Email
Notification", "IP Resolver", "Laszlo", "Task
Manager", "Terraserver"
- The strategy is that once a plugin is moved out of the core to
the xwiki-plugins/ dir, we create a JIRA project for it
- We define a version scheme for them. I propose to start at 0.1
as we haven't released them yet. We shouldn't release any of them
until we've tested it works with the latest version of XWiki Core.
* "XWiki Clients":
- We remove this JIRA project and move all current clients to the
sandbox. Namely they are: "foxwiki", "anyedit", "p2pxwiki",
"wiked"
Others:
* I'm not entirely sure what to do with these projects in xwiki-
tools: build tools, package and cryptpasswords.
* I think they're too small and not well-defined enough to warrant
a JIRA project each. I'm proposing to create a Tools component in
the main XWiki JIRA project for now to see how they develop in the
future.
WDYT?
If you're ok I'm proposing to do the reorganization work.
Thanks
-Vincent