Bug 450 - Alpha and Beta versions should get their update channel set accordingly
Summary: Alpha and Beta versions should get their update channel set accordingly
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8 Alpha 2
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-08-25 16:35 UTC by Andreia Gaita
Modified: 2011-10-13 08:43 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Andreia Gaita 2011-08-25 16:35:08 UTC
Alpha and beta versions should have the "Install unstable developer updates" checkbox set automatically, with the corresponding update channel set by default. This ensures that people trying unstable versions will get the appropriate updates and won't get offered downgrades by default.

Also, some notes:
The update process from alpha to beta to stable and from one major version to a higher one should go something like this:

- An alpha release of track 2.8 should be offered alphas, betas and release versions of that track.
- If we start shipping 2.10 alphas, the 2.8 alphas shouldn't be offering those as an update, they should always prefer 2.8-something. The same thing for betas.
- Only stable versions should offer alphas or betas of a higher track (2.8 stable to a 2.10 alpha or beta), if the user selects the checkbox for the unstable releases.

This way, if you start with an alpha or beta, you'll eventually stabilize and you won't get offered downgrades when you're testing unstable software unless you really want to.
Comment 1 Lluis Sanchez 2011-10-13 08:43:06 UTC
I'm not sure how that happened in the past, but MD currently will never offer downgrades. We don't really plan to have to maintain several simultaneous beta tracks again. We won't release any 2.X alpha or beta until 2.X-1 is stable. So the above scenario should not happen anymore.