On Monday 20 April 2009 02:18:39 xor wrote: > > Hi, > > I just noticed that our bugtracker has a very nice feature which we do not > use: The "Roadmap": > > If you assign a "Target Version" to bugs then you get a nice progress bar > for each product version which the system has stored so you can see how > "far" you are. To see what it looks like, choose WoT as project and go to > Roadmap, I have assigned a target version for most of the issues.
Target Version appears to have been added *after* we added a "milestone" field. Therefore a lot more bugs have a milestone assigned than have a Target Version. It would make sense to migrate the bugs with a milestone to have a Target Version. > > *Of course* this will not make the work which we have to do less, yet having > a *overview* of work helps managing it and also helps motivating yourself: > Everyone should know the effect of breaking stuff down into small pieces, it > feels like it is less work if you can continously solve small pieces / tasks > and mark them as finished. If you get a progress bar you can motivate > yourself even more. > > Further, I think one thing which the Freenet project is struggling with is a > general lack of concentration on ESSENTIAL TODOs. Everyone is just > implementing new features all the time and old issues do not get fixed. And > we do not have an overview of what needs to be done before we can release a > new version. This generates the atmosphere of PRESSURE: Insane amounts of > work which nobody knows about how much it is and donations running out, etc. You may have a point here. > > Therefore I suggest that we decide what the next officially released > versions will be and assign a target version for all bugs/issues in the > tracker to decide what will be in the next version, in the version after > that, etc. > > An easy point to start at would be the "0.7.1 priorities" issue in the > tracker: Clearly all bugs which are "related" to that issue should be > actually configured to have target version 0.7.1. I would have assigned them > the target version right now but there are two issues: There are lots of bugs linked from 0.7.1 that are definitely not essential for the actual 0.8 release. The release is as always driven by deadlines and running out of money. I have outlined what I consider to be essential for 0.8.0-beta1 in the status update email. > > 1. Everyone has been talking about 0.8.0 being our next major release, is > this true? Yes. > I would vote for skipping 0.7.1 because in the next major release > we can bundle WoT/Freetalk and therefore the version number should suggest > major changes, which "0.7.1" does not. Yes. Although 0.7.0 had Frost bundled IIRC. > > 2. The bugtracker does not show the "Update Issue" button to me at closed > issues for Freenet, only for WoT, so I guess that I am lacking the > permissions ;) Closed issues should of course also be updated, otherwise we > will start at 0%. Hmmm that's odd. You have developer rights on Freenet, Freetalk and WoT. > > Further, there is one important thing to be mentioned: The target version is > probably not set on any issues because in the default configuration of > mantis you just do not see that setting when reporting/editing issues, you > need to go to advanced mode first. I suggest everyone to enable it by > default: Go to "My Account", then to "Preferences", then check "Advanced > Report", "Advanced View", "Advanced Update". Any idea how to enable this globally? > > ... so I suggest we now use the bugtracker to really decide what needs to be > done and what not, create a compact yet suffcient roadmap for 0.8.0 and > implement it. > > Greetings, xor -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 835 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20090420/9ea016d6/attachment.pgp>
