keep older versions on the update site

[carchrae]

The update site contains only the latest version. If a new version is broken, then there is no easy way to roll back. (eg, see #149 )

[vote539]

+1

[paulvi]

I believe if new version is broken, issues should be raised and fixed ASAP.

-1

[carchrae]

Sure, that as well.

Breaking it for any users in the meantime is no good. You'll probably say
those users should patch and fix the problem.

Also, it is worth noting that supporting an older version of eclipse takes
more time.
On 12 Apr 2014 08:58, "Paul Verest" notifications@github.com wrote:

I believe if new version is broken, issues should be raised and fixed ASAP.

-1

Reply to this email directly or view it on GitHubhttps://github.com//issues/152#issuecomment-40284164
.

[paulvi]

Looking closer at the case #163 (0.13 now requires 4.x), yes, 0.12 should have been available too.

+1

[fhd]

0.13 requiring 4.x is certainly not intentional, but I'll add 0.12 back to the update site in the mean time - there's no real reason not to keep old versions there I guess.

[henriquedesousa]

Yes there are. It's crashing my RAD which is based on Eclipse 3.6, so I'd like to try the older versions.