3 ms·
> kudos for not just picking a day a month and doing monthly updates like most, that tends to seem more arbitrary unlike 4 weeks Planning feature development a
by cpeterso 7y ago
> kudos for not just picking a day a month and doing monthly updates like most, that tends to seem more arbitrary unlike 4 weeks
Planning feature development and rollout is more difficult if you always have to refer to a calendar to find future release dates. I would prefer to be able to say a feature can land in Firefox Nightly in January, ship to Firefox Beta on February 1, and Release channel users on March 1.
Mozilla has a long wiki page of past and future release dates:
https://wiki.mozilla.org/RapidRelease/Calendar https://wiki.mozilla.org/RapidRelease/Calendar
- re4ctor 7y agoThe problem there is February 1st isn't always a good release day, say if it's a Saturday. So you'd ship on the 2nd or 3rd sometimes... or sometimes that's a holiday, or there are validate reasons to avoid a period (like the first ~week of July or September). You could try to pick something like the "2nd Wednesday" of the month, but there are still occasions for mid-week holidays and other timing problems related to marketing or external events (other announcements, or world events that would clobber your marketing push). Inevitably you have to plan it anyway, so you might as well do that from the start.