Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Juno aggregation builds are ready, and Indigo has moved to 'maintenance'

Not sure if you are saying there is a typo in the table, or if my description was puzzling. In case of the latter, the previous, initially proposed table (from a month or two ago) had 6 weeks for M6 and 8 weeks for M7. So, we "balanced" them to each be 7 weeks, M6 lasting one week longer, and M7 starting a week later. This complication occurred this year, mostly, because we actually have a "53 week" development year, instead of 52, just given the way the "fourth Wednesday" falls, for the Release date. So, in my initial haste to make the first table, I just plopped the extra week into M7. In case you meant typo ... I'm just not seeing it, so you may need to spell it out to me.

Hope that helps. If not, or if there is a typo, let us know.


From:        Ed Willink <ed@xxxxxxxxxxxxx>
To:        cross-project-issues-dev@xxxxxxxxxxx
Date:        08/10/2011 03:19 PM
Subject:        Re: [cross-project-issues-dev] Juno aggregation builds are ready, and Indigo has moved to 'maintenance'
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

Hi David

Speaking of dates, the Planning Council has finalized the milestone dates for Juno, as documented at

I'm puzzled. Did you update the span but not the End Dates?


       Ed Willink
cross-project-issues-dev mailing list

Back to the top