Re: [Banshee-List] making and maintaining a roadmap?

[Michael Martin-Smucker <mlmartin13 gmail com>]

Since you Banshee devs probably don't have much else going on today - I mean,
it's *just* a beta release ;) - I thought this would be a good time for me
to finally get around to putting up that roadmap that I've been promising.

What I ended up doing:
It's a couple simple tables grouped into broad release categories (right now
this only includes 1.6 and Future).  Each row lists a feature/fix, a more
specific target release if one is available ("Beta 5" for example), and a
status (Committed, Branched, Patched, Planned).

What still needs to be done:
Tomorrow I plan on adding links to relevant resources like bug reports, git
branches, or blog entries so that interested users can find more details on
any particular feature.  I also plan to add a short paragraph explaining the
purpose of the roadmap - it should be clear that this is a resource for
curious users more than a blueprint for developers - and a key to explain
the "status" options for users who aren't familiar with commits, branches,
and patches.

This may seem like a strange time to publish a roadmap since many of the
items will become obsolete with the release later today.  I chose to work on
this now, though, because I figured it would be easy to use the NEWS section
from the 1.5.4 release to fill the content.  Now that the framework is up, I
definitely don't mind keeping things up to date more regularly.  There are
probably already features that are planned for 1.5.5 that I don't know about
(or long-term features that I've forgotten to include), so if anyone notices
anything missing, it would be helpful if you'd chime in here on the mailing
list.

I'll stop by #banshee tomorrow to talk about some specifics; for now I need
some sleep.


gabaug wrote:
> 
> On Fri, Feb 12, 2010 at 7:23 AM, Michael Martin-Smucker
> <mlmartin13 gmail com> wrote:
>> -What had we said about odd-point/beta releases?  Should the roadmap be
>> detailed enough to include all the unstable releases between now and 1.6?
>> Similarly, should the roadmap to 1.6 include features that have already
>> been
>> released in unstable releases like 1.5.2 and 1.5.3?  Actually, now that I
>> think about it, it might be nice to have a broad 1.6 category that
>> contains
>> 1.5.x sub-categories.  This would help group new features by
>> progress/completeness.
> 
> I think the roadmap should contain two categories of items:
> 1) Fixes and features that are in master but not yet released (beta or
> otherwise)
> 2) Features and fixes being worked on (eg in branches, or patches in
> BGO) but that we don't know when they'll land
> 
>> -What about bug fixes?  Should the roadmap include only new features, or
>> do
>> important bug fixes count as well?  Would something like "iPod support
>> for
>> distributions using devicekit-disks" belong on the roadmap?  How
>> technical
>> would we want the wording to be?
> 
> Definitely include important bug fixes.  I think the DeviceKit fix
> would belong on the roadmap, except it's already released (in 1.5.2).
> 
>> -Are there any features/fixes targeted for 1.8?
> 
> No.
> 
>> Right now the categories
>> are basically "1.6" and a generic "future."
> 
> Yeah, exactly.
> 
> Thanks!
> 
> Gabriel
> _______________________________________________
> banshee-list mailing list
> banshee-list gnome org
> http://mail.gnome.org/mailman/listinfo/banshee-list  (unsubscribe here)
> 

-- 
View this message in context: http://old.nabble.com/making-and-maintaining-a-roadmap--tp27329569p27714131.html
Sent from the Banshee mailing list archive at Nabble.com.