On Fri, 2010-07-02 at 13:38 +0200, Martin Bähr wrote: > won't that cause problems with people wanting to switch from qa to > stable once it is updated? on debian and ubuntu this works well, because > each testing version eventually transforms into the stable version, all > the users need to do is _not_ switch to the next testing version but > stay where they are.
It's all valid concerns. But my reasoning is that, even we are pulling down stable releases and publishing qa images, we are not actually promoting them to end users. It's just a interim and 'use-at-your-own-risk' product. To some degree, this potential failure when switching from qa to stable is part of the risk. (And it can be minimized if we make some test before the new official release.) And, I don't think there will be many new users picking up foresight (atm)(especially with the big 'at-your-own-risk' warning). And there will be even less 'end users' among them. So with the qa images, these somewhat 'advanced' users can get a feeling about how foresight is like, and it will be somewhat easier to help them transfer to stable again. Yes, I think the main purpose of most people who are trying foresight atm is to see how it is like, not seriously switching to it from other OS. IOM publishing QA images is far better than presenting an outdated version of our product. Besides, people can know from it how our development is going and the difficulty we are facing. Jesse _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
