On Mon, Mar 28, 2011 at 8:11 PM, Alexandre Franke <alexandre.fra...@gmail.com> wrote: > Hi, > > On Sun, Mar 27, 2011 at 11:25 AM, Rune Morling <e...@foresightlinux.org> > wrote: >> <doniphon> fl:2-devel -> fl:2-qa -> fl:2-2.5 <- fl:2 > […] >>> And people have agreed to do a release this Sunday with fl:2-qa >>> images. The final 2.5 release would be several weeks later while >>> people work out how to do the transitional fl:2-2.5 label. > > Here's how I understand current situation. Tell me if I'm wrong. > Now 2.5 is out. The isos are built on fl:2-qa. > Next step is to push to a newly created fl:2.5 label from fl:2-qa, > have some updates and release FL 2.5.1 with isos built from fl:2.5. > Then, with some group migration script, we'll move people who are > currently on fl:2 to fl:2.5. > > The thing that is unclear to me is what we'll do for people who just > installed 2.5. They'll be on fl:2-qa and I guess we don't want to have > migration scripts that move all people on fl:2-qa to fl:2.5. >
I would think that with a system model setup, migrating is as easy as changing your search labels and doing a conary sync IIRC. Shouldn't be a big issue, especially not when fl:2-qa is by definition the same as fl:2.5 if we freeze 2-qa for some period after the 2.5.1 group promote from fl:2-qa to fl:2.5 (to give users time to make the transition). But I've been wrong before. ermo _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
