16 Sep
2008
16 Sep
'08
4:12 p.m.
On Sep 16, 2008, at 2:57 PM, Jerome Velociter wrote:
Vincent Massol wrote:
That's going to be... a lot of fun :)
What do we do with issues that concerns a module (for example URL),
but
at the time of the issue (or even currently), concerned code is not
actually located in that module (but is in xwiki-core instead) ?
Move it
to the component url anyway ? Leave it in "other" ?
I'm not proposing that we move closed issues and not even opened
issues...
I'm only proposing that we remove deprecated components and move
issues in the new components as a whole.
Ex1: Issues in Templates components are moved to the web-standard
component
Ex2: Issues about URL that are currently in "core" stay there.
-Vincent
On Sep 16, 2008, at 2:18 PM, Jerome Velociter
wrote:
Yes, better this way.
Hello everybody,
Discussing we Vincent we agreed that currently XWiki Core components
on
JIRA are very scattered and do not make very much sense. We
propose to
reorganize the project and have one component per module in platform
core and web, which would be :
* action
* cache
* component
* containers
* context
* xwiki-core
I'd call this one "other" actually since all the other modules are
core too so it's a bit misleading. And when we create new modules out
of it we create the new jira component. * observation
* patchservice
* plexus
* rendering
* url
* velocity
* xml
* xmlrpc
* web-standard
* web-exo
* web-gwt
* web-wysiwyg
+1 for that.
A question now I have is : since it will be quite a big refactoring,
do
we move all issues ? or only open issues ?
Move the issues. >
> +1 in general.
>
> Thanks
> -Vincent