Dear All In order to align with the new 1.2 release plan, I would like propose to add a new value "1.2.0" in "MeeGo Release" field to track 1.2.0 update bugs. So in "MeeGo Release" field, "1.2.0" will mean this bug is for 1.2.0 update and "1.2" means this bug is for 1.2 trunk/1.2.1.
In this case, if user wants to report bugs for 1.2.0 0519 release or 1.2.0 update, he/she can report it to "1.2.0" release field; if user wants to report bugs for 1.2.1 branch, he/she can report it to "1.2" release field. For 1.2.0 update release, we can only focus on field = "1.2.0" bug fix and verification. Your comments are welcome. Thanks Daniel -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Selbak, Rolla N Sent: Thursday, June 09, 2011 5:19 AM To: Shane Bryan; Collaboration list for Release Engineering and QA teams (moderated discussion list) Subject: Re: [meego-releases] [update] 1.2 Release plan (1.2.0, 1.2.1) On 6/8/11 1:29 PM, "Shane Bryan" <[email protected]> wrote: >On Wed, 8 Jun 2011 13:16:50 -0700 >"Selbak, Rolla N" <[email protected]> wrote: > >> On 6/7/11 10:42 PM, "Marko Saukko" <[email protected]> wrote: >> >> >On 06/08/2011 03:45 AM, Selbak, Rolla N wrote: >> >> Hey all, >> >> >> >> Just fyi, I have updated the wiki with the latest plans for >> >> 1.2.0-Update and 1.2.1. >> >> >> >> http://wiki.meego.com/Release_Engineering/Plans/1.2 >> >> >> >> Thanks, >> >> Release Engineering >> >> >> >> _______________________________________________ >> >> MeeGo-releases mailing list >> >> [email protected] >> >> http://lists.meego.com/listinfo/meego-releases >> > >> >Hi, >> > >> >Do I understand this right that there will be two update 'releases' >> >1.2.0-Update AND 1.2.1 release? I though 1.2.1 was 1.2.0 update :/ So >> >there will be multiple different 1.2 branches alive as well? >> >> 1.2.0 is a release (5/19) >> 1.2.0-Update is the update branch for 1.2.0 >> >> 1.2.1 is a release (9/1) >> 1.2.1-Update will be the update branch for 1.2.1 >> > >Thanks for the clarification so far Rolla. Np > >> Yes, there will be different update branches for 1.2.0 and 1.2.1. > >I think this is different than how things were planned for 1.1, so that >could be contributing to the confusion. You're right, this is a newer way of doing things compared to our previous releases. > >> Both update repos will be located here: >> >> http://repo.meego.com/MeeGo/updates > >The remaining outstanding question that I'm not quite understanding is, >will there be official images produced for 1.2.1 (and 1.2.X for any >other such releases)? Yes. 1.2.0 - Netbook and IVI official images have already been release (5/19) 1.2.1 - Tablet official images will be releases (~9/1) > >To ask this another way... > >Is there an update/upgrade path from 1.2.0 to 1.2.1? No :( Originally, I was trying to plan it so there would be an update/upgrade path from 1.2.0 to 1.2.1, however the vertical dependencies were not cooperating...namely that IVI and Tablet use the same Meego UX, and are currently in different stages of UX development (e.g. bug-fixes that Tablet needs sometimes break IVI all over the place, etc.) > >As it appears from this thread, I'm guessing not. At least not a >"supported" one, as it would seemingly require end users to modify >their /etc/zypp/repos.d/*.repo files manually to reference the 1.2.1 >update repos. Right. And even that would be at the user's own risk, since since bug-fixes for 1.2.0-Updates are cherry-picked carefully for Netbook and IVI (meaning that if a Netbook or IVI user installed a 1.2.0 release image, then pointed to the 1.2.1 repos (instead of the 1.2.0-Update repos), and updated their machines that way, they don't have guaranteed results. > >Thanks for taking the time to clear things up. No problem at all. rs > >Shane... _______________________________________________ MeeGo-releases mailing list [email protected] http://lists.meego.com/listinfo/meego-releases _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
