tickets with no milestone

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

tickets with no milestone

Kralidis,Tom [Ontario]
If I check http://trac.osgeo.org/mapserver/roadmap, there shows open
tickets based on milestones.

However, when I check http://trac.osgeo.org/mapserver/report/3, I see a
majority of tickets which are not assigned to any milestone (not even
FUTURE).  Should these be set to FUTURE?

..Tom
Reply | Threaded
Open this post in threaded view
|

Re: tickets with no milestone

Frank Warmerdam
Kralidis,Tom [Burlington] wrote:
> If I check http://trac.osgeo.org/mapserver/roadmap, there shows open
> tickets based on milestones.
>
> However, when I check http://trac.osgeo.org/mapserver/report/3, I see a
> majority of tickets which are not assigned to any milestone (not even
> FUTURE).  Should these be set to FUTURE?

Tom,

I've never been to clear on the meaning of the FUTURE milestone other than
that it indicates we might like to do this but it isn't expected soon.  I'm
not sure how much better that is then just having no milestone set.

I do suspect we need to get better organized at analysing the untargetted
bugs.  For instance, before issuing 5.0.2 I'd like it if a pass was made
through all open bugs (or at least all open recently submitted bugs)
trying to determine if they ought to be acted on in with some priority.

But ... who will do this and who will actually dig into the bugs if they
are classified as high priority!

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, [hidden email]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org
Reply | Threaded
Open this post in threaded view
|

Re: tickets with no milestone

Daniel Morissette
Frank Warmerdam wrote:

> Kralidis,Tom [Burlington] wrote:
>> If I check http://trac.osgeo.org/mapserver/roadmap, there shows open
>> tickets based on milestones.
>>
>> However, when I check http://trac.osgeo.org/mapserver/report/3, I see a
>> majority of tickets which are not assigned to any milestone (not even
>> FUTURE).  Should these be set to FUTURE?
>
> Tom,
>
> I've never been to clear on the meaning of the FUTURE milestone other than
> that it indicates we might like to do this but it isn't expected soon.  I'm
> not sure how much better that is then just having no milestone set.
>

I see the FUTURE milestone as meaning "someone has looked at this and
determined that it's a legit thing we ought to do at some point in the
future... just not sure when". To me this is different from no
milestone. I guess we should review all FUTURE tickets everytime we plan
a new release, but we don't take time to do that at the moment.

Perhaps developers should get in the habit of setting a milestone when
they look at a ticket so that tickets always show up under a proper
milestone (I try to do that as much as possible)... and then a ticket
with no milestone would simply mean that the ticket has not been looked
at yet?

The main problem I see at the moment is that tickets with no milestone
do not show up in Trac's Roadmap page and for this reason we may tend to
ignore them. I wonder if Trac can be configured to display the empty
milestone in that page as well? To solve this issue we could possibly
create a "notset" or "TBD" milestone and make it the default for all new
tickets (I just verified that this seems to be possible in the Trac
admin page).

Daniel
--
Daniel Morissette
http://www.mapgears.com/
Reply | Threaded
Open this post in threaded view
|

Re: tickets with no milestone

Kralidis,Tom [Ontario]
 

> -----Original Message-----
> From: UMN MapServer Developers List
> [mailto:[hidden email]] On Behalf Of Daniel Morissette
> Sent: 23 January, 2008 3:02 PM
> To: [hidden email]
> Subject: Re: [UMN_MAPSERVER-DEV] tickets with no milestone
>
> Frank Warmerdam wrote:
> > Kralidis,Tom [Burlington] wrote:
> >> If I check http://trac.osgeo.org/mapserver/roadmap, there
> shows open
> >> tickets based on milestones.
> >>
> >> However, when I check
> http://trac.osgeo.org/mapserver/report/3, I see
> >> a majority of tickets which are not assigned to any milestone (not
> >> even FUTURE).  Should these be set to FUTURE?
> >
> > Tom,
> >
> > I've never been to clear on the meaning of the FUTURE
> milestone other
> > than that it indicates we might like to do this but it
> isn't expected
> > soon.  I'm not sure how much better that is then just
> having no milestone set.
> >
>
> I see the FUTURE milestone as meaning "someone has looked at
> this and determined that it's a legit thing we ought to do at
> some point in the future... just not sure when". To me this
> is different from no milestone. I guess we should review all
> FUTURE tickets everytime we plan a new release, but we don't
> take time to do that at the moment.
>
> Perhaps developers should get in the habit of setting a
> milestone when they look at a ticket so that tickets always
> show up under a proper milestone (I try to do that as much as
> possible)... and then a ticket with no milestone would simply
> mean that the ticket has not been looked at yet?
>
> The main problem I see at the moment is that tickets with no
> milestone do not show up in Trac's Roadmap page and for this
> reason we may tend to ignore them. I wonder if Trac can be
> configured to display the empty milestone in that page as
> well? To solve this issue we could possibly create a "notset"
> or "TBD" milestone and make it the default for all new
> tickets (I just verified that this seems to be possible in
> the Trac admin page).
>

That would be a great idea.

..Tom