65383 - Clean up milestone prefs - curmilestone and nummilestones are obsolete.

Status: RESOLVED FIXED

(Bugzilla :: Administration, task, P4)

Description

[Matthew Tuck [:CodeMachine]]

It looks like currmilestone and nummilestones are obsolete.

nummilestones should be removed, and currmilestone should be made per-product.

I will put deps for some bugs that would find this useful.

Comment 1

[Dave Miller [:justdave]]

Moving to real milestones...

Comment 2

[Hixie (not reading bugmail)]

Taking all Bugzilla 3.0 bugs -- congratulations to MattyT for the triage, it
really was spot on. Note: I may end up pushing some of these bugs back to 3.2,
we'll see. However, I believe all these bugs should just fall out of the 
redesign. Let's hope I'm right!

(Note: I'm also resetting the priority field to "---" so that I can retriage any
that I consider important or likely to be dropped.)

Comment 3

[Dave Miller [:justdave]]

The Bugzilla 3 component is going away.  We're going to depend on the Milestones 
for this.  At the time this component was created, we didn't have milestones for 
Bugzilla.

Comment 4

[Dave Miller [:justdave]]

We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.

Comment 5

[Vlad Dascalu]

*** Bug 210375 has been marked as a duplicate of this bug. ***

Comment 6

[Vlad Dascalu]

I've grep the source and defparams.pl is the only place where those have remained.

Comment 7

[Vlad Dascalu]

Attachment: Patch. Applied, tested, behaves like expected.

Comment 8

[Christian Reis]

Comment on attachment 128421 [details] [diff] [review]
Patch. Applied, tested, behaves like expected.

r=kiko (though I wonder if we have to do something in checksetup to disable
these params from previous -- okay, checked with justdave, it's not. cool)

Comment 9

[Dave Miller [:justdave]]

Note one of the goals of this bug (and the prerequisite for bug 41651 and bug
65388) was to make the current milestone be a field on each product.  It makes
well enough sense to separate the tasks though since the existing params are
already useless.  Please file a new bug to add current milestone as a
product-level setting, and move the dependencies.

Comment 10

[Dave Miller [:justdave]]

Vlad: see comment 9

Checking in defparams.pl;
/cvsroot/mozilla/webtools/bugzilla/defparams.pl,v  <--  defparams.pl
new revision: 1.119; previous revision: 1.118
done

Comment 11

[Vlad Dascalu]

Bug 218036 has been filled addressing this issue. The dependencies have been
updated.

Comment 12

[Dave Miller [:justdave]]

*** Bug 234241 has been marked as a duplicate of this bug. ***

Comment 13

[Dave Miller [:justdave]]

correcting summary to make dupe searches easier

Comment 14

[Nourdine]

Hello Every Body, I want to know what is exactely the role of mileStones on bugzilla System. is not the same thing as redmine, trac bug trackers .



I need more information of this options, there is no roadmap, user must enter manualy the value of mileStone to each product.

Please  more clarifications