Closed Bug 712323 Opened 12 years ago Closed 12 years ago

Add Target Milestone, Version, and tracking flags to Fennec Native product

Categories

(bugzilla.mozilla.org :: Administration, task)

Production
All
Android
task
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: mbrubeck, Assigned: dkl)

References

Details

(Keywords: mobile)

Can you please add/change the following fields in the "Fennec Native" product?

Bug fields:
* Target Milestone
* Version

Bug flags:
* status-firefox*
* tracking-firefox*
* tracking-fennec

Attachment flags:
* approval-mozilla-aurora
* approval-mozilla-beta
* approval-mozilla-release

The values and flag names should match the ones from the existing "Fennec" or "Firefox" products.

Thanks!
(In reply to Matt Brubeck (:mbrubeck) from comment #0)
> Can you please add/change the following fields in the "Fennec Native"
> product?
> 
> Bug fields:
> * Target Milestone
> * Version

as we have to manually create each entry for milestones and versions, is there a minimal list you'd be happy with?

> Bug flags:
> * status-firefox*
> * tracking-firefox*
> * tracking-fennec

these changes will require code changes and a production push.  bmo is normally updated early thursday.
 
> Attachment flags:
> * approval-mozilla-aurora
> * approval-mozilla-beta
> * approval-mozilla-release

normally not a problem.  however in trying to do so i encountered a problem with a recently added extension, which we'll have to fix first :(
Depends on: 712327
The first release for Fennec Native is 11.
(In reply to Byron Jones ‹:glob› from comment #1)
> (In reply to Matt Brubeck (:mbrubeck) from comment #0)
> > Can you please add/change the following fields in the "Fennec Native"
> > product?
> > 
> > Bug fields:
> > * Target Milestone
> > * Version
> 
> as we have to manually create each entry for milestones and versions, is
> there a minimal list you'd be happy with?

If you can provide the minimal list as glob mentioned I can go ahead and get these added for you now. I assume for versions, you would need to start off with Firefox 11,12, and trunk. As well for target milestones, Firefox 11,12,13,14 and Future?

> > Bug flags:
> > * status-firefox*
> > * tracking-firefox*
> > * tracking-fennec
> 
> these changes will require code changes and a production push.  bmo is
> normally updated early thursday.

I have committed the needed changes to allow these fields to show up for Fennec Native. Should be live with the next code push this week.

>  
> > Attachment flags:
> > * approval-mozilla-aurora
> > * approval-mozilla-beta
> > * approval-mozilla-release
> 
> normally not a problem.  however in trying to do so i encountered a problem
> with a recently added extension, which we'll have to fix first :(

We will also add these flags once the code push has happened this week.

dkl
Assignee: nobody → dkl
Status: NEW → ASSIGNED
(In reply to David Lawrence [:dkl] from comment #3)

> > > Bug fields:
> > > * Target Milestone
> > > * Version
> > 
> > as we have to manually create each entry for milestones and versions, is
> > there a minimal list you'd be happy with?
> 
> If you can provide the minimal list as glob mentioned I can go ahead and get
> these added for you now. I assume for versions, you would need to start off
> with Firefox 11,12, and trunk. As well for target milestones, Firefox
> 11,12,13,14 and Future?

Yes, these will work fine. Thank you.
(In reply to Mark Finkle (:mfinkle) from comment #4)
> > If you can provide the minimal list as glob mentioned I can go ahead and get
> > these added for you now. I assume for versions, you would need to start off
> > with Firefox 11,12, and trunk. As well for target milestones, Firefox
> > 11,12,13,14 and Future?
> 
> Yes, these will work fine. Thank you.

This part is done.

dkl
David: Doug Turner pinged me about the attachment extensions today - I see there is a problem adding them manually - do we have an ETA on when the code push will happen? Thanks.
I can see if we can do a push today if IT has the time slot. Normally they schedule these for thursdays.

dkl
the changes are now live.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.