9 Mar
2007
9 Mar
'07
9:43 p.m.
On Mar 8, 2007, at 10:21 PM, Vincent Massol wrote:
On Mar 8, 2007, at 8:32 PM, Ludovic Dubost wrote:
Another option which I know some project are doing is to create a
version called "Future". That allows to differentiate issues we've
sorted from issues not categorized yet. Of course once everything is
in Future we'll need to look at Future issues and decide to move them
and at that time we won't know which ones we've decided to leave in
Future and which ones have been moved... So we'll need Future2, etc.
and then "back to the Future" ;-) (sorry for this bad joke, I'm too
tired)
-Vincent
Hi,
I've helped it a little by closing a few tasks that were actually
fixed..
This is actually great. I think it shows that we are more active
at reporting bugs. Quite a lot of them seem to come from the
community which shows that XWiki is probably getting more users.
I've seen that there has actually been a big push since February 1st.
Now we will need to find more time to triage the issues that are
reported and also more development power to fix them.
Any contributors wanting to help with either of these ? A first
step is taking all the issues that have no version assigned and
see which one should absolutely be fixed for 1.0
We've done that already and issues for 1.0 are already marked. That
said it's likely we've forgotten some. However we can hardly take
any more if we want to release for mid-April.
So if anyone knows a really important bug that 1.0 absolutely needs
to have or it'll wreak havoc for all users , please raise it so
that we can schedule it! :)
Back to the "no fix for" issue I wonder what we should do. We could
have a strategy saying that no fix for means the bug needs to be
reviewed and that we have to always assign "fix for". Only issue is
that everything will get put in the 1.1 basket (as it already is).
That said it's possible to do this and once we start tackling 1.1
move everything to 1.2, etc., but I don't like it too much. Our
users will think what is marked for 1.1 will get done in 1.1 so I
think it's better to leave issues unassigned and only assign stuff
that we know will be done in the assigned version.
WDYT? Vincent Massol
a écrit :
Hi,
Thanks to Raffaello we also have the JIRA charting plugin (http://
confluence.atlassian.com/display/JIRAEXT/JIRA+Charting+Plugin)
installed now on jira.xwiki.org.
For example go to http://jira.xwiki.org/ and check the chart. I'm
attaching it here too. This is an interesting chart showing
resolved issues vs new issue being created, for the past 90 days.
As you can see in january of this year we've crossed a threshold
where there are more issues created than we can close and this is
increasing... Meaning we need to find a way to deal with this
somehow...
Also when in the navigator you there's now a Chart button that
you can use to display charts of the current filtered issues.
Last you can add several new charting portlets in your dashboards
now.
Thanks
-Vincent
--------------------------------------------------------------------
----
--------------------------------------------------------------------
----
--
You receive this message as a subscriber of the xwiki-
dev(a)objectweb.org mailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page: http://
www.objectweb.org/wws
--
Ludovic Dubost
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost AIM: nvludo Yahoo: ludovic
--
You receive this message as a subscriber of the xwiki-
dev(a)objectweb.org mailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page: http://
www.objectweb.org/wws