947422 - Please create the following 1.3 and 1.4 milestone for Firefox OS and Core

Status: RESOLVED FIXED

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

Description

[Joe Cheng [:jcheng] (please needinfo)]

+++ This bug was initially created as a clone of Bug #920748 +++

Please create the following Target Milestones in Core and Firefox OS.

1.3 C1 (12/20)
1.3 C2 (01/17)
1.3 C3 (01/31)
1.3 C4 (02/14)
1.3 C5 (02/28)
1.3 C6 (03/14)

1.4 Sprint 1 (12/20)
1.4 Sprint 2 (01/17)
1.4 Sprint 3 (01/31)
1.4 Sprint 4 (02/14)
1.4 Sprint 5 (02/28)
1.4 Sprint 6 (03/14)

Comment 1

[Joe Cheng [:jcheng] (please needinfo)]

Hi David, wonder if you are the proper assignee to assist with this bug? I am pinging you as you were the assignee for bug 920748. Thanks

Comment 2

[:glob ✱]

hrm, some those dates are ambiguous and really should be in the format of 20dec, 1jan, etc.

Comment 3

[:glob ✱]

joe,

to match all other milestones (except the last batch), do you have any issues with creating the following instead:

1.3 C1 (20dec)
1.3 C2 (17jan)
1.3 C3 (31jan)
1.3 C4 (14feb)
1.3 C5 (28feb)
1.3 C6 (14mar)

1.4 Sprint 1 (20dec)
1.4 Sprint 2 (17jan)
1.4 Sprint 3 (31jan)
1.4 Sprint 4 (14feb)
1.4 Sprint 5 (28feb)
1.4 Sprint 6 (14mar)

i'll also like to change the milestones from the last batch to match this structure, as currently they are either (sep27) or "mm/dd" which is problematic for non-US people.

Comment 4

[Joe Cheng [:jcheng] (please needinfo)]

Hi Byron,

in order to reduce the number of new selections in target milesetone, let's reduce the new additions to
1.3 C1 / 1.4 S1 (20dec)
1.3 C2 / 1.4 S2 (17jan)
1.3 C3 / 1.4 S3 (31jan)
1.3 C4 / 1.4 S4 (14feb)
1.3 C5 / 1.4 S5 (28feb)
1.3 C6 / 1.4 S6 (14mar)

let's not remove the previous milestones. if changing the date format won't impact any of the existing queries, it's fine to change the format

Thanks!

Comment 5

[:glob ✱]

(In reply to Joe Cheng [:jcheng] from comment #4)
> in order to reduce the number of new selections in target milesetone, let's
> reduce the new additions to

will do
 
> let's not remove the previous milestones. if changing the date format won't
> impact any of the existing queries, it's fine to change the format

ah, it will impact existing queries, so we'll have to leave them alone :(

Comment 6

[:glob ✱]

there's a 20 character limit for milestones, so your latest suggestion won't work.
sorry i didn't catch this earlier.

i experimented with squishing both 1.3 and 1.4 into a single 20 character milestone, but wasn't able to come up with something that resulted in clarity of the versions.

i suspect we'll have to go with the list from comment 3

Comment 7

[Joe Cheng [:jcheng] (please needinfo)]

removing 3 spaces and now each new item is exactly 20 characters? :)

1.3 C1/1.4 S1(20dec)
1.3 C2/1.4 S2(17jan)
1.3 C3/1.4 S3(31jan)
1.3 C4/1.4 S4(14feb)
1.3 C5/1.4 S5(28feb)
1.3 C6/1.4 S6(14mar)

Comment 8

[:glob ✱]

milestones created.

Comment 9

[Kai-Chih Hu [:khu]]

(In reply to Byron Jones ‹:glob› from comment #8)
> milestones created.

Thank you, Byron!