Hi, First of all, congrats to everyone.
It would be great if we have a "Testing day" and a "Localization day", because, for example, in Romanian the localization is not really great. Andreea On Thu, Jan 30, 2014 at 11:20 AM, [email protected] <[email protected]>wrote: > Hi devs, > > We've done one year of BFD on the 5.x cycle and this has allowed us to > reach a greater goal: one of having caught up with the number of open bugs. > We've first succeeded in closing more bugs than there has been created bugs > over a year, then over 2 years, then over 3 years, then over 4 years and > we're very close to succeed for the last 1600 days (ie 4.4 years)! :) > > I'd like to congratulate everyone on this achievement which is really > awesome. I don't know a lot of other projects who've had this kind of > success so we can be proud of ourselves! > > Current result can be seen at: > http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 > > Note that there are still 357 opened bugs which were created since the > beginning of the project. > > 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? > > 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 > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
