[Grok-dev] reviving the bug tracker

Todd todd at infrae.com
Mon Dec 15 06:05:51 EST 2008

Martijn Faassen wrote:
> Hi there,
> On Mon, Dec 15, 2008 at 10:02 AM, Todd <todd at infrae.com> wrote:
>> Martijn Faassen wrote:
> [snip]
>> If you target a bug to a release, that is the way you can start funneling
>> bugs to a specific series. I can start moving them now.
> Go ahead. Be bold. :) We can, presumably, always retarget a bug for a
> later release.
>>> We also have a 'trunk' series and the role of this I'm not entirely clear
>>> about.
>> I'm not certain what the grok community wants to do with this. From what
>> I've seen so far the concept of a trunk shouldn't apply to organizing series
>> and milestones within series. I suppose the latest series and latest
>> milestone should be working from a trunk.
> I think therefore we should get rid of the 'trunk' series to avoid
> future confusion. Could you look into that?
Alright, I think we should make it obsolete but before doing so we can 
add more details to our series like supplying urls to documentation and 
svn trunk/tags (trunk for the latest active series/milestone, and tags 
for released series/milestones, I'm not sure how branches relate to 
series and milestones).
> It'd be good if you could produce a short document with a few
> scenarios in it and how we're to use launchpad in each case. How do we
> assign bugs to milestones, when to make a bug affect a milestone, when
> do we target it for release, when are we to set "fix released" how do
> we make sure the bug is closed when a bug fix is released. it's all
> slowly coming together for me but a clear procedure would help us
> define it better. The goal is that we can clearly bugs to milestones
> and that after we've fixed the bug and released a new version, the
> bugs are indeed not showing up anymore as open in launchpad.
> Regards,
> Martijn

More information about the Grok-dev mailing list