2009/2/3 Stephan Kulow <coolo@novell.com>:
But on that note, when the alpha / beta / rc does come along -- why should it really be replacing the factory download anyway? I really think we should have /developer.html (or rename it to /factory.html) which will always have (or link to) the latest factory snapshots. Actually, once we release betas it's much more welcome if people test them to avoid us hunting bugs that will go away next day due to failed rebuild or something.
So I would simply add a redirect to the developer.html that can be commented out in a second. The wiki page it redirects to can of course stay - just as the automatically updated ISOs will stay.
So would it be possible to have : Factory - experimental packaging, likely broken may work; recommended test by install specific update packages Beta - packages that should work, here for integration testing. Developer rolls back update, that causes "breakage", until a resolution is found (updating additional packages) It appears from https://features.opensuse.org/305634 that zypper dup is technically ready to be supported, so having a "should work" release target, from the last version, would allow upgrade problems to be caught "early and often", rather than in a frantic rush at end of release cycle. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org