I propose we change the policy and start to assign tickes to the version they
appeared into: in trac you have ticket version and milestone. You can set the
version to Campsite version that has that bug and the milestone will be set to
the version that will fix the bug. In mantis we didn't have this so we used to
set the version to the 'milestone', meaning when we'll fix the bug and this
does not give you accurate information.
Mugur
--- Paul Baranowski wrote:
> The conversion from Mantis to Trac is complete!
>
> From now on, please enter your bugs/issues/features here:
> http://code.campware.org/projects/campsite/
>
> Trac offers much greater visibility into the current state of the
> project. You can see what's happening on a daily basis, what's been
> fixed, and any new issues that have come up. It really gives you a good
> sense of how much is going on in a project. (And usually there is a lot
> going on, but it wasnt so visible using mantis!)
>
> Want to see what's been happening recently? Look at the "Timeline" page:
> http://code.campware.org/projects/campsite/timeline
>
> Want to see how far we are along on a release? Look at the "Roadmap"
> (click on "Show All Milestones" at the top to see completed milestones):
> http://code.campware.org/projects/campsite/roadmap
>
> Want to see a (very detailed) plan for coming releases?
> http://code.campware.org/projects/campsite/report/3
>
> We'll be updating our links on campware.org to make sure everyone gets
> to the new site when they want to submit a bug.
>
> - Paul
>
>
> Paul Baranowski wrote:
> > Today, I will be converting all the mantis bugs to trac (using an
> > automated script). Therefore, as of now, you will not find the campsite
> > project on mantis. However, DO NOT enter any issues into trac until you
> > receive another email from me saying that it is OK to do so. If you
> > enter in any issues in the meantime, they will be lost.
> >
> > - Paul
> >
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
------------------------------------------
Posted to Phorum via PhorumMail
I propose we change the policy and start to assign tickes to the version
they
appeared into: in trac you have ticket version and milestone. You can set
the
version to Campsite version that has that bug and the milestone will be
set to
the version that will fix the bug. In mantis we didn't have this so we
used to
set the version to the 'milestone', meaning when we'll fix the bug and
this
does not give you accurate information.
Mugur
--- Paul Baranowski wrote:
> The conversion from Mantis to Trac is complete!
>
> From now on, please enter your bugs/issues/features here:
> http://code.campware.org/projects/campsite/
>
> Trac offers much greater visibility into the current state of the
> project. You can see what's happening on a daily basis, what's been
> fixed, and any new issues that have come up. It really gives you a good
> sense of how much is going on in a project. (And usually there is a lot
> going on, but it wasnt so visible using mantis!)
>
> Want to see what's been happening recently? Look at the "Timeline"
page:
> http://code.campware.org/projects/campsite/timeline
>
> Want to see how far we are along on a release? Look at the "Roadmap"
> (click on "Show All Milestones" at the top to see completed milestones):
> http://code.campware.org/projects/campsite/roadmap
>
> Want to see a (very detailed) plan for coming releases?
> http://code.campware.org/projects/campsite/report/3
>
> We'll be updating our links on campware.org to make sure everyone gets
> to the new site when they want to submit a bug.
>
> - Paul
>
>
> Paul Baranowski wrote:
> > Today, I will be converting all the mantis bugs to trac (using an
> > automated script). Therefore, as of now, you will not find the
campsite
> > project on mantis. However, DO NOT enter any issues into trac until
you
> > receive another email from me saying that it is OK to do so. If you
> > enter in any issues in the meantime, they will be lost.
> >
> > - Paul
> >
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Just BTW:
This feature /does/ exist in Mantis. When you resolve a bug there's a
"fixed in version" box. Advanced view.
JP
Mugur Rus wrote:
>I propose we change the policy and start to assign tickes to the version they
>appeared into: in trac you have ticket version and milestone. You can set the
>version to Campsite version that has that bug and the milestone will be set to
>the version that will fix the bug. In mantis we didn't have this so we used to
>set the version to the 'milestone', meaning when we'll fix the bug and this
>does not give you accurate information.
>
>Mugur
>
>--- Paul Baranowski wrote:
>
>
>>The conversion from Mantis to Trac is complete!
>>
>>From now on, please enter your bugs/issues/features here:
>>http://code.campware.org/projects/campsite/
>>
>>Trac offers much greater visibility into the current state of the
>>project. You can see what's happening on a daily basis, what's been
>>fixed, and any new issues that have come up. It really gives you a good
>>sense of how much is going on in a project. (And usually there is a lot
>>going on, but it wasnt so visible using mantis!)
>>
>>Want to see what's been happening recently? Look at the "Timeline" page:
>>http://code.campware.org/projects/campsite/timeline
>>
>>Want to see how far we are along on a release? Look at the "Roadmap"
>>(click on "Show All Milestones" at the top to see completed milestones):
>>http://code.campware.org/projects/campsite/roadmap
>>
>>Want to see a (very detailed) plan for coming releases?
>>http://code.campware.org/projects/campsite/report/3
>>
>>We'll be updating our links on campware.org to make sure everyone gets
>>to the new site when they want to submit a bug.
>>
>>- Paul
>>
>>
>>Paul Baranowski wrote:
>>
>>
>>>Today, I will be converting all the mantis bugs to trac (using an
>>>automated script). Therefore, as of now, you will not find the campsite
>>>project on mantis. However, DO NOT enter any issues into trac until you
>>>receive another email from me saying that it is OK to do so. If you
>>>enter in any issues in the meantime, they will be lost.
>>>
>>>- Paul
>>>
>>>
>>>
>>
>>
>
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam? Yahoo! Mail has the best spam protection around
>http://mail.yahoo.com
>
>
>
------------------------------------------
Posted to Phorum via PhorumMail
After entering a few tickets into Trac I gotta say that it is vastly
inferior to Mantis. Search functionality is very limited, the default
views are unhelpful and if you change the view to the one you want, it
gets forgotten next time you return to the page. Every time you enter
the bug system you have to decide which view you want. The default
things for new tickets are not helpful either.
Trac doesn't highlight source code and doesn't have a two-column diff.
It's painful to view revisions to files that are a part of a large
changeset becuase all the files are listed above the diff.
If we're not going to use Trac's Wiki for the user documentation, and
the bug tracker is second-rate, and the source code viewer is inferior
to ViewCVS (ViewSVN), then we are only using it for that one nice
feature: the timeline.
Is anyone else having these doubts? Am I just set in my ways???
JP
John Pye wrote:
>Just BTW:
>This feature /does/ exist in Mantis. When you resolve a bug there's a
>"fixed in version" box. Advanced view.
>JP
>
>Mugur Rus wrote:
>
>
>
>>I propose we change the policy and start to assign tickes to the version they
>>appeared into: in trac you have ticket version and milestone. You can set the
>>version to Campsite version that has that bug and the milestone will be set to
>>the version that will fix the bug. In mantis we didn't have this so we used to
>>set the version to the 'milestone', meaning when we'll fix the bug and this
>>does not give you accurate information.
>>
>>Mugur
>>
>>--- Paul Baranowski wrote:
>>
>>
>>
>>
>>>The conversion from Mantis to Trac is complete!
>>>
>>>
>>>
>>>From now on, please enter your bugs/issues/features here:
>>
>>
>>>http://code.campware.org/projects/campsite/
>>>
>>>Trac offers much greater visibility into the current state of the
>>>project. You can see what's happening on a daily basis, what's been
>>>fixed, and any new issues that have come up. It really gives you a good
>>>sense of how much is going on in a project. (And usually there is a lot
>>>going on, but it wasnt so visible using mantis!)
>>>
>>>Want to see what's been happening recently? Look at the "Timeline" page:
>>>http://code.campware.org/projects/campsite/timeline
>>>
>>>Want to see how far we are along on a release? Look at the "Roadmap"
>>>(click on "Show All Milestones" at the top to see completed milestones):
>>>http://code.campware.org/projects/campsite/roadmap
>>>
>>>Want to see a (very detailed) plan for coming releases?
>>>http://code.campware.org/projects/campsite/report/3
>>>
>>>We'll be updating our links on campware.org to make sure everyone gets
>>>to the new site when they want to submit a bug.
>>>
>>>- Paul
>>>
>>>
>>>Paul Baranowski wrote:
>>>
>>>
>>>
>>>
>>>>Today, I will be converting all the mantis bugs to trac (using an
>>>>automated script). Therefore, as of now, you will not find the campsite
>>>>project on mantis. However, DO NOT enter any issues into trac until you
>>>>receive another email from me saying that it is OK to do so. If you
>>>>enter in any issues in the meantime, they will be lost.
>>>>
>>>>- Paul
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>__________________________________________________
>>Do You Yahoo!?
>>Tired of spam? Yahoo! Mail has the best spam protection around
>>http://mail.yahoo.com
>>
>>
>>
>>
>>
>
>
>
>
------------------------------------------
Posted to Phorum via PhorumMail
Yes, in mantis you can set the version that fixed the bug at the moment you
resolve the it BUT you can't schedule a bug to be fixed in a certain version.
For example, 2.2.2 has bug xxxx, I want to schedule it for 2.2.3 and I want to
be able to see what bugs were scheduled for 2.2.3 BEFORE they were fixed. This
is not possible in Mantis.
Mugur
--- John Pye wrote:
> Just BTW:
> This feature /does/ exist in Mantis. When you resolve a bug there's a
> "fixed in version" box. Advanced view.
> JP
>
> Mugur Rus wrote:
>
> >I propose we change the policy and start to assign tickes to the version
> they
> >appeared into: in trac you have ticket version and milestone. You can set
> the
> >version to Campsite version that has that bug and the milestone will be set
> to
> >the version that will fix the bug. In mantis we didn't have this so we used
> to
> >set the version to the 'milestone', meaning when we'll fix the bug and this
> >does not give you accurate information.
> >
> >Mugur
> >
> >--- Paul Baranowski wrote:
> >
> >
> >>The conversion from Mantis to Trac is complete!
> >>
> >>From now on, please enter your bugs/issues/features here:
> >>http://code.campware.org/projects/campsite/
> >>
> >>Trac offers much greater visibility into the current state of the
> >>project. You can see what's happening on a daily basis, what's been
> >>fixed, and any new issues that have come up. It really gives you a good
> >>sense of how much is going on in a project. (And usually there is a lot
> >>going on, but it wasnt so visible using mantis!)
> >>
> >>Want to see what's been happening recently? Look at the "Timeline" page:
> >>http://code.campware.org/projects/campsite/timeline
> >>
> >>Want to see how far we are along on a release? Look at the "Roadmap"
> >>(click on "Show All Milestones" at the top to see completed milestones):
> >>http://code.campware.org/projects/campsite/roadmap
> >>
> >>Want to see a (very detailed) plan for coming releases?
> >>http://code.campware.org/projects/campsite/report/3
> >>
> >>We'll be updating our links on campware.org to make sure everyone gets
> >>to the new site when they want to submit a bug.
> >>
> >>- Paul
> >>
> >>
> >>Paul Baranowski wrote:
> >>
> >>
> >>>Today, I will be converting all the mantis bugs to trac (using an
> >>>automated script). Therefore, as of now, you will not find the campsite
> >>>project on mantis. However, DO NOT enter any issues into trac until you
> >>>receive another email from me saying that it is OK to do so. If you
> >>>enter in any issues in the meantime, they will be lost.
> >>>
> >>>- Paul
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Tired of spam? Yahoo! Mail has the best spam protection around
> >http://mail.yahoo.com
> >
> >
> >
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
------------------------------------------
Posted to Phorum via PhorumMail
Sorry, I see what you mean there. Whenever I was using Campsite Mantis,
I was filling in the bug's version as 2.2.2, meaning that that was the
version which showed the bug. I realise that I was doing it wrong.
About the "milestone version" field that you're talking about, Mantis
does have a facility for custom fields that could be used for project
planning. You would have to write a little external application to
generate the milestone reports though.
Might be worth sending them a feature request. I'll do it.
JP
Mugur Rus wrote:
>Yes, in mantis you can set the version that fixed the bug at the moment you
>resolve the it BUT you can't schedule a bug to be fixed in a certain version.
>For example, 2.2.2 has bug xxxx, I want to schedule it for 2.2.3 and I want to
>be able to see what bugs were scheduled for 2.2.3 BEFORE they were fixed. This
>is not possible in Mantis.
>
>Mugur
>
>--- John Pye wrote:
>
>
>>Just BTW:
>>This feature /does/ exist in Mantis. When you resolve a bug there's a
>>"fixed in version" box. Advanced view.
>>JP
>>
>>Mugur Rus wrote:
>>
>>
>>
>>>I propose we change the policy and start to assign tickes to the version
>>>
>>>
>>they
>>
>>
>>>appeared into: in trac you have ticket version and milestone. You can set
>>>
>>>
>>the
>>
>>
>>>version to Campsite version that has that bug and the milestone will be set
>>>
>>>
>>to
>>
>>
>>>the version that will fix the bug. In mantis we didn't have this so we used
>>>
>>>
>>to
>>
>>
>>>set the version to the 'milestone', meaning when we'll fix the bug and this
>>>does not give you accurate information.
>>>
>>>Mugur
>>>
>>>--- Paul Baranowski wrote:
>>>
>>>
>>>
>>>
>>>>The conversion from Mantis to Trac is complete!
>>>>
>>>>
>>>>
>>>>From now on, please enter your bugs/issues/features here:
>>>
>>>
>>>>http://code.campware.org/projects/campsite/
>>>>
>>>>Trac offers much greater visibility into the current state of the
>>>>project. You can see what's happening on a daily basis, what's been
>>>>fixed, and any new issues that have come up. It really gives you a good
>>>>sense of how much is going on in a project. (And usually there is a lot
>>>>going on, but it wasnt so visible using mantis!)
>>>>
>>>>Want to see what's been happening recently? Look at the "Timeline" page:
>>>>http://code.campware.org/projects/campsite/timeline
>>>>
>>>>Want to see how far we are along on a release? Look at the "Roadmap"
>>>>(click on "Show All Milestones" at the top to see completed milestones):
>>>>http://code.campware.org/projects/campsite/roadmap
>>>>
>>>>Want to see a (very detailed) plan for coming releases?
>>>>http://code.campware.org/projects/campsite/report/3
>>>>
>>>>We'll be updating our links on campware.org to make sure everyone gets
>>>>to the new site when they want to submit a bug.
>>>>
>>>>- Paul
>>>>
>>>>
>>>>Paul Baranowski wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>Today, I will be converting all the mantis bugs to trac (using an
>>>>>automated script). Therefore, as of now, you will not find the campsite
>>>>>project on mantis. However, DO NOT enter any issues into trac until you
>>>>>receive another email from me saying that it is OK to do so. If you
>>>>>enter in any issues in the meantime, they will be lost.
>>>>>
>>>>>- Paul
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>__________________________________________________
>>>Do You Yahoo!?
>>>Tired of spam? Yahoo! Mail has the best spam protection around
>>>http://mail.yahoo.com
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam? Yahoo! Mail has the best spam protection around
>http://mail.yahoo.com
>
>
>
------------------------------------------
Posted to Phorum via PhorumMail
Just remembered how they do this "milestone version" stuff with
Bugzilla... they set up 'group bugs' which they assign a whole bunch of
child bugs to. So if you want to make a new release and you want to have
a particular set of bugs fixed for that version, then you make all of
those bugs 'children' of the 'version bug'. Then, you can't resolve the
version bug, ie release your new version, until you've fixed all the
child bugs.
This is flexible, and works fine with Mantis as well. So there's no need
to any extra code etc.
JP
John Pye wrote:
>Sorry, I see what you mean there. Whenever I was using Campsite Mantis,
>I was filling in the bug's version as 2.2.2, meaning that that was the
>version which showed the bug. I realise that I was doing it wrong.
>
>About the "milestone version" field that you're talking about, Mantis
>does have a facility for custom fields that could be used for project
>planning. You would have to write a little external application to
>generate the milestone reports though.
>
>Might be worth sending them a feature request. I'll do it.
>
>JP
>
>Mugur Rus wrote:
>
>
>
>>Yes, in mantis you can set the version that fixed the bug at the moment you
>>resolve the it BUT you can't schedule a bug to be fixed in a certain version.
>>For example, 2.2.2 has bug xxxx, I want to schedule it for 2.2.3 and I want to
>>be able to see what bugs were scheduled for 2.2.3 BEFORE they were fixed. This
>>is not possible in Mantis.
>>
>>Mugur
>>
>>--- John Pye wrote:
>>
>>
>>
>>
>>>Just BTW:
>>>This feature /does/ exist in Mantis. When you resolve a bug there's a
>>>"fixed in version" box. Advanced view.
>>>JP
>>>
>>>Mugur Rus wrote:
>>>
>>>
>>>
>>>
>>>
>>>>I propose we change the policy and start to assign tickes to the version
>>>>
>>>>
>>>>
>>>>
>>>they
>>>
>>>
>>>
>>>
>>>>appeared into: in trac you have ticket version and milestone. You can set
>>>>
>>>>
>>>>
>>>>
>>>the
>>>
>>>
>>>
>>>
>>>>version to Campsite version that has that bug and the milestone will be set
>>>>
>>>>
>>>>
>>>>
>>>to
>>>
>>>
>>>
>>>
>>>>the version that will fix the bug. In mantis we didn't have this so we used
>>>>
>>>>
>>>>
>>>>
>>>to
>>>
>>>
>>>
>>>
>>>>set the version to the 'milestone', meaning when we'll fix the bug and this
>>>>does not give you accurate information.
>>>>
>>>>Mugur
>>>>
>>>>--- Paul Baranowski wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>The conversion from Mantis to Trac is complete!
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>From now on, please enter your bugs/issues/features here:
>>>>
>>>>
>>>>
>>>>
>>>>>http://code.campware.org/projects/campsite/
>>>>>
>>>>>Trac offers much greater visibility into the current state of the
>>>>>project. You can see what's happening on a daily basis, what's been
>>>>>fixed, and any new issues that have come up. It really gives you a good
>>>>>sense of how much is going on in a project. (And usually there is a lot
>>>>>going on, but it wasnt so visible using mantis!)
>>>>>
>>>>>Want to see what's been happening recently? Look at the "Timeline" page:
>>>>>http://code.campware.org/projects/campsite/timeline
>>>>>
>>>>>Want to see how far we are along on a release? Look at the "Roadmap"
>>>>>(click on "Show All Milestones" at the top to see completed milestones):
>>>>>http://code.campware.org/projects/campsite/roadmap
>>>>>
>>>>>Want to see a (very detailed) plan for coming releases?
>>>>>http://code.campware.org/projects/campsite/report/3
>>>>>
>>>>>We'll be updating our links on campware.org to make sure everyone gets
>>>>>to the new site when they want to submit a bug.
>>>>>
>>>>>- Paul
>>>>>
>>>>>
>>>>>Paul Baranowski wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Today, I will be converting all the mantis bugs to trac (using an
>>>>>>automated script). Therefore, as of now, you will not find the campsite
>>>>>>project on mantis. However, DO NOT enter any issues into trac until you
>>>>>>receive another email from me saying that it is OK to do so. If you
>>>>>>enter in any issues in the meantime, they will be lost.
>>>>>>
>>>>>>- Paul
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>__________________________________________________
>>>>Do You Yahoo!?
>>>>Tired of spam? Yahoo! Mail has the best spam protection around
>>>>http://mail.yahoo.com
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>__________________________________________________
>>Do You Yahoo!?
>>Tired of spam? Yahoo! Mail has the best spam protection around
>>http://mail.yahoo.com
>>
>>
>>
>>
>>
>
>
>
>
------------------------------------------
Posted to Phorum via PhorumMail
--- John Pye wrote:
> Just remembered how they do this "milestone version" stuff with
> Bugzilla... they set up 'group bugs' which they assign a whole bunch of
> child bugs to. So if you want to make a new release and you want to have
> a particular set of bugs fixed for that version, then you make all of
> those bugs 'children' of the 'version bug'. Then, you can't resolve the
> version bug, ie release your new version, until you've fixed all the
> child bugs.
Yes, but this is a workaround, requires more work and it's based on convention.
In trac you can use this feature directly, no workarounds, no conventions.
Plus, trac reports do give you the information you need quickly, it's much
easier to navigate in trac and get useful information. In mantis I had to make
so many clicks to get what I want...
Mugur
> This is flexible, and works fine with Mantis as well. So there's no need
> to any extra code etc.
>
> JP
>
> John Pye wrote:
>
> >Sorry, I see what you mean there. Whenever I was using Campsite Mantis,
> >I was filling in the bug's version as 2.2.2, meaning that that was the
> >version which showed the bug. I realise that I was doing it wrong.
> >
> >About the "milestone version" field that you're talking about, Mantis
> >does have a facility for custom fields that could be used for project
> >planning. You would have to write a little external application to
> >generate the milestone reports though.
> >
> >Might be worth sending them a feature request. I'll do it.
> >
> >JP
> >
> >Mugur Rus wrote:
> >
> >
> >
> >>Yes, in mantis you can set the version that fixed the bug at the moment you
> >>resolve the it BUT you can't schedule a bug to be fixed in a certain
> version.
> >>For example, 2.2.2 has bug xxxx, I want to schedule it for 2.2.3 and I want
> to
> >>be able to see what bugs were scheduled for 2.2.3 BEFORE they were fixed.
> This
> >>is not possible in Mantis.
> >>
> >>Mugur
> >>
> >>--- John Pye wrote:
> >>
> >>
> >>
> >>
> >>>Just BTW:
> >>>This feature /does/ exist in Mantis. When you resolve a bug there's a
> >>>"fixed in version" box. Advanced view.
> >>>JP
> >>>
> >>>Mugur Rus wrote:
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>>I propose we change the policy and start to assign tickes to the version
> >>>>
> >>>>
> >>>>
> >>>>
> >>>they
> >>>
> >>>
> >>>
> >>>
> >>>>appeared into: in trac you have ticket version and milestone. You can set
> >>>>
> >>>>
> >>>>
> >>>>
> >>>the
> >>>
> >>>
> >>>
> >>>
> >>>>version to Campsite version that has that bug and the milestone will be
> set
> >>>>
> >>>>
> >>>>
> >>>>
> >>>to
> >>>
> >>>
> >>>
> >>>
> >>>>the version that will fix the bug. In mantis we didn't have this so we
> used
> >>>>
> >>>>
> >>>>
> >>>>
> >>>to
> >>>
> >>>
> >>>
> >>>
> >>>>set the version to the 'milestone', meaning when we'll fix the bug and
> this
> >>>>does not give you accurate information.
> >>>>
> >>>>Mugur
> >>>>
> >>>>--- Paul Baranowski wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>The conversion from Mantis to Trac is complete!
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>From now on, please enter your bugs/issues/features here:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>http://code.campware.org/projects/campsite/
> >>>>>
> >>>>>Trac offers much greater visibility into the current state of the
> >>>>>project. You can see what's happening on a daily basis, what's been
> >>>>>fixed, and any new issues that have come up. It really gives you a good
> >>>>>sense of how much is going on in a project. (And usually there is a lot
> >>>>>going on, but it wasnt so visible using mantis!)
> >>>>>
> >>>>>Want to see what's been happening recently? Look at the "Timeline"
> page:
> >>>>>http://code.campware.org/projects/campsite/timeline
> >>>>>
> >>>>>Want to see how far we are along on a release? Look at the "Roadmap"
> >>>>>(click on "Show All Milestones" at the top to see completed milestones):
> >>>>>http://code.campware.org/projects/campsite/roadmap
> >>>>>
> >>>>>Want to see a (very detailed) plan for coming releases?
> >>>>>http://code.campware.org/projects/campsite/report/3
> >>>>>
> >>>>>We'll be updating our links on campware.org to make sure everyone gets
> >>>>>to the new site when they want to submit a bug.
> >>>>>
> >>>>>- Paul
> >>>>>
> >>>>>
> >>>>>Paul Baranowski wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Today, I will be converting all the mantis bugs to trac (using an
> >>>>>>automated script). Therefore, as of now, you will not find the
> campsite
> >>>>>>project on mantis. However, DO NOT enter any issues into trac until
> you
> >>>>>>receive another email from me saying that it is OK to do so. If you
> >>>>>>enter in any issues in the meantime, they will be lost.
> >>>>>>
> >>>>>>- Paul
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>__________________________________________________
> >>>>Do You Yahoo!?
> >>>>Tired of spam? Yahoo! Mail has the best spam protection around
> >>>>http://mail.yahoo.com
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>__________________________________________________
> >>Do You Yahoo!?
> >>Tired of spam? Yahoo! Mail has the best spam protection around
> >>http://mail.yahoo.com
> >>
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
------------------------------------------
Posted to Phorum via PhorumMail
I agree that the milestone thing is a nice feature in Trac.
But trac is much less powerful. The filtering system requires you to
enter stuff every time - Mantis remembers your filters and lets you save
filters with a simple click. Trac gives me no information on how to save
new reports, and in doesn't 'remember where I was' before, either.
For example, how do I quickly see a list of the last couple of bugs
which I filed?
I have to click "view tickets" -> "active tickets" -> "ticket" (column
heading) -> "ticket" (column heading again).
To do that in mantis, I would just click "My View".
To show a list of all bugs due for fixing in a particular version, I
could create a saved filter in a couple of minutes that would show all
bugs dependent on a a given ID.
Trac has no system for relationships between bugs, or even for saying
that a given bug is a duplicate of another one.
It has no system for showing what recent changes to a bug have been
made, exept via the Timeline (along with all the other bugs, in one big
view)
JP
Mugur Rus wrote:
>--- John Pye wrote:
>
>
>>Just remembered how they do this "milestone version" stuff with
>>Bugzilla... they set up 'group bugs' which they assign a whole bunch of
>>child bugs to. So if you want to make a new release and you want to have
>>a particular set of bugs fixed for that version, then you make all of
>>those bugs 'children' of the 'version bug'. Then, you can't resolve the
>>version bug, ie release your new version, until you've fixed all the
>>child bugs.
>>
>>
>Yes, but this is a workaround, requires more work and it's based on convention.
>In trac you can use this feature directly, no workarounds, no conventions.
>Plus, trac reports do give you the information you need quickly, it's much
>easier to navigate in trac and get useful information. In mantis I had to make
>so many clicks to get what I want...
>
>Mugur
>
>
>
>>This is flexible, and works fine with Mantis as well. So there's no need
>>to any extra code etc.
>>
>>JP
>>
>>John Pye wrote:
>>
>>
>>
>>>Sorry, I see what you mean there. Whenever I was using Campsite Mantis,
>>>I was filling in the bug's version as 2.2.2, meaning that that was the
>>>version which showed the bug. I realise that I was doing it wrong.
>>>
>>>About the "milestone version" field that you're talking about, Mantis
>>>does have a facility for custom fields that could be used for project
>>>planning. You would have to write a little external application to
>>>generate the milestone reports though.
>>>
>>>Might be worth sending them a feature request. I'll do it.
>>>
>>>JP
>>>
>>>Mugur Rus wrote:
>>>
>>>
>>>
>>>
>>>
>>>>Yes, in mantis you can set the version that fixed the bug at the moment you
>>>>resolve the it BUT you can't schedule a bug to be fixed in a certain
>>>>
>>>>
>>version.
>>
>>
>>>>For example, 2.2.2 has bug xxxx, I want to schedule it for 2.2.3 and I want
>>>>
>>>>
>>to
>>
>>
>>>>be able to see what bugs were scheduled for 2.2.3 BEFORE they were fixed.
>>>>
>>>>
>>This
>>
>>
>>>>is not possible in Mantis.
>>>>
>>>>Mugur
>>>>
>>>>--- John Pye wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Just BTW:
>>>>>This feature /does/ exist in Mantis. When you resolve a bug there's a
>>>>>"fixed in version" box. Advanced view.
>>>>>JP
>>>>>
>>>>>Mugur Rus wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>I propose we change the policy and start to assign tickes to the version
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>they
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>appeared into: in trac you have ticket version and milestone. You can set
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>the
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>version to Campsite version that has that bug and the milestone will be
>>>>>>
>>>>>>
>>set
>>
>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>to
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>the version that will fix the bug. In mantis we didn't have this so we
>>>>>>
>>>>>>
>>used
>>
>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>to
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>set the version to the 'milestone', meaning when we'll fix the bug and
>>>>>>
>>>>>>
>>this
>>
>>
>>>>>>does not give you accurate information.
>>>>>>
>>>>>>Mugur
>>>>>>
>>>>>>--- Paul Baranowski wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>The conversion from Mantis to Trac is complete!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>From now on, please enter your bugs/issues/features here:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>http://code.campware.org/projects/campsite/
>>>>>>>
>>>>>>>Trac offers much greater visibility into the current state of the
>>>>>>>project. You can see what's happening on a daily basis, what's been
>>>>>>>fixed, and any new issues that have come up. It really gives you a good
>>>>>>>sense of how much is going on in a project. (And usually there is a lot
>>>>>>>going on, but it wasnt so visible using mantis!)
>>>>>>>
>>>>>>>Want to see what's been happening recently? Look at the "Timeline"
>>>>>>>
>>>>>>>
>>page:
>>
>>
>>>>>>>http://code.campware.org/projects/campsite/timeline
>>>>>>>
>>>>>>>Want to see how far we are along on a release? Look at the "Roadmap"
>>>>>>>(click on "Show All Milestones" at the top to see completed milestones):
>>>>>>>http://code.campware.org/projects/campsite/roadmap
>>>>>>>
>>>>>>>Want to see a (very detailed) plan for coming releases?
>>>>>>>http://code.campware.org/projects/campsite/report/3
>>>>>>>
>>>>>>>We'll be updating our links on campware.org to make sure everyone gets
>>>>>>>to the new site when they want to submit a bug.
>>>>>>>
>>>>>>>- Paul
>>>>>>>
>>>>>>>
>>>>>>>Paul Baranowski wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Today, I will be converting all the mantis bugs to trac (using an
>>>>>>>>automated script). Therefore, as of now, you will not find the
>>>>>>>>
>>>>>>>>
>>campsite
>>
>>
>>>>>>>>project on mantis. However, DO NOT enter any issues into trac until
>>>>>>>>
>>>>>>>>
>>you
>>
>>
>>>>>>>>receive another email from me saying that it is OK to do so. If you
>>>>>>>>enter in any issues in the meantime, they will be lost.
>>>>>>>>
>>>>>>>>- Paul
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>__________________________________________________
>>>>>>Do You Yahoo!?
>>>>>>Tired of spam? Yahoo! Mail has the best spam protection around
>>>>>>http://mail.yahoo.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>__________________________________________________
>>>>Do You Yahoo!?
>>>>Tired of spam? Yahoo! Mail has the best spam protection around
>>>>http://mail.yahoo.com
>>>>
>>>>
>>>>
>=== message truncated ===
>
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam? Yahoo! Mail has the best spam protection around
>http://mail.yahoo.com
>
>
>
------------------------------------------
Posted to Phorum via PhorumMail