30 Jan
2014
30 Jan
'14
3:08 p.m.
See below
On 30 Jan 2014 at 14:57:48, Clemens Klein-Robbenhaar
(c.robbenhaar@espresto.com(mailto:c.robbenhaar@espresto.com)) wrote:
Hi,
I’m not against it, it’s just that I don’t see what there would be to do and I don’t think
there’s enough for everyone. At best you can run this once and it’s over in half a day.
Personally I’m doing this almost every day already…
Or do you mean that this day would be about *testing* all extensions and grade them as
working/not working/etc? If so we would need the ratings system in place on e.x.o first
IMO because we’ll need some way to record what we find.
So you’d need to specify more precisely what this day would be made of I think.
Thanks
-Vincent
Note that there are still 357 opened bugs which
were created since the beginning of the project.
I guess the trouble with the remaining bugs is that they are the hard ones that cannot be
fixed in a single day.
It looks more like something like a dedicated "bug crunching week" for that
would be necessary; at last they seem to need a similar attention as new features might
need.
My feeling is that it’s hard to keep the
sustained pace we’ve set on the BFD days and I think we need a bit of fresh air.
Also now that we’ve caught up with bugs I believe the most important part is to just try
to contain the bug ratio so that we’re about even in term of number of new bugs vs umber
of bugs we close. If we can achieve this it would already be a very nice success.
So what I’m proposing for the 6.x cycle is this:
- one week out of 2 we continue doing a BFD
- the other week we do a rolling XWiki Day on another activity
Here’s a list of other activities we could do (first mentioned in this thread:
http://markmail.org/message/a5ew5ilbgxvf67lu ):
A) Doc Fixing Day: improve xwiki.org
B) Deprecation Fixing Day: reduce # of deprecated calls and move code to legacy
C) Violation Fixing Dy: reduce # of violations. 12K right now on platform for ex (see
http://sonar.xwiki.org/drilldown/issues/org.xwiki.platform:xwiki-platform)
D) Javadoc Improvement Day: Add missing javadocs in our code and remove checkstyle
excludes
E) Code Coverage Day: Add as many tests as possible (unit and functional) to increase the
TPC
F) Broken Links Day: fix as many broken links as possible on xwiki.org. To find them is
easy: we just need to enable the IRC Link Checker botlet and wait on IRC to get them
listed!
G) Others you would consider interesting?
On 01/30/2014 10:37 AM, Ecaterina Moraru (Valica) wrote:
G.1) Improvements issues closing day
I agree this would be important, too. Especially with user interfaces often a
"small" improvement helps a lot improving user experience.
G.4) e.x.o cleaning day (marking old extensions
as deprecated, writing
documentation, specifying what version the extension is working on, etc. )
On 01/30/2014 10:40 AM, vincent(a)massol.net wrote:
This one could be part of the Documentation
Fixing Day IMO.
Unless if one finds out that an extension does not longer work and instead of making it
as deprecated just fixes it.
I feel allocation some time to keep extensions up to date and running would be a good
thing, because:
* most people who start developing code for XWiki start with getting some extension /
code snippet etc. and tweak the a little
* the code they see there are thus the one that gives them the first impression "how
to do things" - if that is outdated code
e.g. using deprecated API, this will cause that kind of "old" code to spread
around in the user base
* if at least some selected part is marked as "up to date" this also gives
users who install extensions a better impression about XWiki in general
* and aside of that, unlike fixing core bugs, updating extensions is something that even
I feel I can do without having my head spin too much. ;)
The only downside I see with that is that folks might prefer to update code, however
remotely useful, to update the documentation ;)
Just for that reason it maybe might be better to distinguish between "xwiki.org Doc
fixing" and "extensions cleaning" day. The only
constraint for defining a day is that it contains small elements that can be fixed quickly
which is the case for the proposals listed above.
So what I propose to be precise:
- one week out of 2 we do a BFD
- the other week we do one of each (A through F). Then once we’ve done a full round we
decide which ones are the best for the project, which ones we want to drop and which ones
we want to repeat more often than others.
I also propose that the 6th and 13th we still do a BFD and on the 20th of Feb we start
doing A, then BFD, then B, etc.
WDYT? Any other proposal or better idea?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs