Hi,
Throughout Linaro we are looking at ways to better coordinate the deliverables that come from Linaro's Working Groups and Platform teams. The idea of Monthly Component releases, a fixed date in the month where each team would release their latest work fits well with what we do and to that end a wiki page proposing the exact dates has been produced at:
https://wiki.linaro.org/Releases/MonthlyMilestones
You will notice that the dates are fixed, always the third Thursday in the month promoting a unified consistency across the teams. Please note that the Linaro Ubuntu Evaluation Builds do not follow this schedule and will continue to be closely coupled with the Ubuntu schedule.
Please take a look at the dates and highlight any problems that could arise from them. If there is positive feedback we can make these dates 'official' very soon meaning teams could start using this format next month.
Regards, Jamie. -- Linaro Release Manager | Platform Project Manager
W dniu 01.03.2011 16:49, Jamie Bennett pisze:
Please take a look at the dates and highlight any problems that could arise from them. If there is positive feedback we can make these dates 'official' very soon meaning teams could start using this format next month.
Sice having no planned releases is worse than having hardcoded release pattern I'm all for having monthly pulse that synchronizes all of Linaro outputs (speaking for my point of view in the validation team)
Even if initially it would not be any more productive I'm sure it would help us align in few months. If anything we could plan features so that they make more sense in context (having an option to do A then B we can choose at random or have a look at what would be released next month by other teams and if A or B would fit better in context).
Thanks ZK
On Tue, Mar 1, 2011 at 9:49 AM, Jamie Bennett jamie.bennett@linaro.org wrote:
Hi,
Throughout Linaro we are looking at ways to better coordinate the deliverables that come from Linaro's Working Groups and Platform teams. The idea of Monthly Component releases, a fixed date in the month where each team would release their latest work fits well with what we do and to that end a wiki page proposing the exact dates has been produced at:
It makes sense and I like the concept.
Will there be some method for groups to state their goals for what they plan to contribute to various releases? Wiki page? Blueprint? Something else?
You will notice that the dates are fixed, always the third Thursday in the month promoting a unified consistency across the teams. Please note that the Linaro Ubuntu Evaluation Builds do not follow this schedule and will continue to be closely coupled with the Ubuntu schedule.
Please take a look at the dates and highlight any problems that could arise from them. If there is positive feedback we can make these dates 'official' very soon meaning teams could start using this format next month.
I think this is a good idea. It gives individuals and teams something to drive towards.
I imagine that as new things are thrown into the pot in anticipation of these dates it might also cause some "chaos" around these days but I view that as a positive side effect. Integration bugs happen.
Regards, Tom Developer Platforms, Linaro
On 01/03/11 at 01:25pm, Tom Gall wrote:
On Tue, Mar 1, 2011 at 9:49 AM, Jamie Bennett jamie.bennett@linaro.org wrote:
Hi,
Throughout Linaro we are looking at ways to better coordinate the deliverables that come from Linaro's Working Groups and Platform teams. The idea of Monthly Component releases, a fixed date in the month where each team would release their latest work fits well with what we do and to that end a wiki page proposing the exact dates has been produced at:
It makes sense and I like the concept.
Will there be some method for groups to state their goals for what they plan to contribute to various releases? Wiki page? Blueprint? Something else?
If agreed I would propose that all projects use the milestone names and dates in the above link in their launchpad projects. Blueprints and work items can then target these milestones and because all projects will have a common naming scheme we can agregate this out to http://status.linaro.org to get a Linaro wide picture of what is delivered, when.
Regards, Tom
Regards, Jamie.
On 1 March 2011 20:45, Jamie Bennett jamie.bennett@linaro.org wrote:
On 01/03/11 at 01:25pm, Tom Gall wrote:
On Tue, Mar 1, 2011 at 9:49 AM, Jamie Bennett jamie.bennett@linaro.org wrote:
If agreed I would propose that all projects use the milestone names and dates in the above link in their launchpad projects. Blueprints and work items can then target these milestones
That would be an annoying format change for toolchain group releases, which are already on a monthly schedule and currently use "2011.03" for milestone names, and "2011.03-0" (-1, -2 ...) for release versions. Is anybody actually currently using the milestone names in the wiki page above? If not, wouldn't it make more sense to standardise on the format we're already using? (Plus, two digit years? Very retro...)
-- PMM
On Wed, Mar 2, 2011 at 10:04 AM, Peter Maydell peter.maydell@linaro.org wrote:
On 1 March 2011 20:45, Jamie Bennett jamie.bennett@linaro.org wrote:
On 01/03/11 at 01:25pm, Tom Gall wrote:
On Tue, Mar 1, 2011 at 9:49 AM, Jamie Bennett jamie.bennett@linaro.org wrote:
If agreed I would propose that all projects use the milestone names and dates in the above link in their launchpad projects. Blueprints and work items can then target these milestones
That would be an annoying format change for toolchain group releases, which are already on a monthly schedule and currently use "2011.03" for milestone names, and "2011.03-0" (-1, -2 ...) for release versions. Is anybody actually currently using the milestone names in the wiki page above? If not, wouldn't it make more sense to standardise on the format we're already using? (Plus, two digit years? Very retro...)
Hi Peter. We'll keep the 2011.xx-y names for the products. Each project has product series and a planning series. The product series are ones like '4.5' or '4.4' for gcc-linaro, and 'trunk' for qemu-linaro, and these then have milestones like '2011.03'. The planning series are named after the planning cycle such as '11.05' and have milestones like '11.05-final', '11.05-alpha2', and so on.
The planning series names and dates are consistent across all of Linaro and let the PM people collapse the data into a whole of Linaro view. Every blueprint we plan to complete this cycle should be accepted for the 11.05 series and at least targeted at the 11.05-final milestone.
There is a wart though - say we plan to finish blueprint 'x' by the March release. Do we assign it to the product 2011.03 milestone or the otherwise identical planning 11.05-foo milestone?
-- Michael
On 2 March 2011 01:33, Michael Hope michael.hope@linaro.org wrote:
On Wed, Mar 2, 2011 at 10:04 AM, Peter Maydell peter.maydell@linaro.org wrote:
That would be an annoying format change for toolchain group releases, which are already on a monthly schedule and currently use "2011.03" for milestone names, and "2011.03-0" (-1, -2 ...) for release versions.
Hi Peter. We'll keep the 2011.xx-y names for the products. Each project has product series and a planning series. The product series are ones like '4.5' or '4.4' for gcc-linaro, and 'trunk' for qemu-linaro, and these then have milestones like '2011.03'.
Is this a proposal to vary the proposed new milestone names, or a suggestion that the toolchain group should continue as it is and not worry about the inconsistency with other groups?
-- PMM
On Wed, Mar 2, 2011 at 9:48 PM, Peter Maydell peter.maydell@linaro.org wrote:
On 2 March 2011 01:33, Michael Hope michael.hope@linaro.org wrote:
On Wed, Mar 2, 2011 at 10:04 AM, Peter Maydell peter.maydell@linaro.org wrote:
That would be an annoying format change for toolchain group releases, which are already on a monthly schedule and currently use "2011.03" for milestone names, and "2011.03-0" (-1, -2 ...) for release versions.
Hi Peter. We'll keep the 2011.xx-y names for the products. Each project has product series and a planning series. The product series are ones like '4.5' or '4.4' for gcc-linaro, and 'trunk' for qemu-linaro, and these then have milestones like '2011.03'.
Is this a proposal to vary the proposed new milestone names, or a suggestion that the toolchain group should continue as it is and not worry about the inconsistency with other groups?
There's no change from our product series/milestone naming point of view. The dates will change to the end of the month to sync up across Linaro. There will be a parallel and, unfortunately, largely identical planning series with milestones as well.
-- Michael
On 02/03/11 at 09:52pm, Michael Hope wrote:
On Wed, Mar 2, 2011 at 9:48 PM, Peter Maydell peter.maydell@linaro.org wrote:
On 2 March 2011 01:33, Michael Hope michael.hope@linaro.org wrote:
On Wed, Mar 2, 2011 at 10:04 AM, Peter Maydell peter.maydell@linaro.org wrote:
That would be an annoying format change for toolchain group releases, which are already on a monthly schedule and currently use "2011.03" for milestone names, and "2011.03-0" (-1, -2 ...) for release versions.
Hi Peter. We'll keep the 2011.xx-y names for the products. Each project has product series and a planning series. The product series are ones like '4.5' or '4.4' for gcc-linaro, and 'trunk' for qemu-linaro, and these then have milestones like '2011.03'.
Is this a proposal to vary the proposed new milestone names, or a suggestion that the toolchain group should continue as it is and not worry about the inconsistency with other groups?
There's no change from our product series/milestone naming point of view. The dates will change to the end of the month to sync up across Linaro. There will be a parallel and, unfortunately, largely identical planning series with milestones as well.
For status.linaro.org to correctly track your Blueprints and Work Items together with the rest of Linaro's outputs they must be targeted to a milestone named like in the wiki page. Status will group all projects together with the same milestone to get a picture of what is due for that date. Targeting Work Items or Blueprints to another milestone will mean they won't show up.
-- Michael
Regards, Jamie.
On 2 Mar 2011, at 08:52, Michael Hope wrote:
On Wed, Mar 2, 2011 at 9:48 PM, Peter Maydell peter.maydell@linaro.org wrote:
On 2 March 2011 01:33, Michael Hope michael.hope@linaro.org wrote:
On Wed, Mar 2, 2011 at 10:04 AM, Peter Maydell peter.maydell@linaro.org wrote:
That would be an annoying format change for toolchain group releases, which are already on a monthly schedule and currently use "2011.03" for milestone names, and "2011.03-0" (-1, -2 ...) for release versions.
Hi Peter. We'll keep the 2011.xx-y names for the products. Each project has product series and a planning series. The product series are ones like '4.5' or '4.4' for gcc-linaro, and 'trunk' for qemu-linaro, and these then have milestones like '2011.03'.
Is this a proposal to vary the proposed new milestone names, or a suggestion that the toolchain group should continue as it is and not worry about the inconsistency with other groups?
There's no change from our product series/milestone naming point of view. The dates will change to the end of the month to sync up across Linaro. There will be a parallel and, unfortunately, largely identical planning series with milestones as well.
We talked more about this tonight and the takeaway was that we need to investigate the best possible way of tracking deliverables with the existing tools we use. This may not explicitly be dependant on a specific milestone name, rather its date but this is still in progress. I'll reply back when I have more information.
-- Michael
Regards, Jamie.
-
Jamie Bennett -
Michael Hope -
Peter Maydell -
Tom Gall -
Zygmunt Krynicki