[planters]

Would you please continue to make the weekly experimental releases available as discrete downloads rather than an automatic update.Thankyou.
Also how can we get them the archived page gives a 404 error.

[cjakeman]

 planters, on 23 July 2014 - 08:40 AM, said:

Would you please continue to make the weekly experimental releases available as discrete downloads rather than an automatic update.

The weekly releases are available from this webpage.



You need the download button on the right (the Supporters' Download) and the date of the release is given underneath.

Hope that helps,

[Lindsayts]

The experimental version of OR is also availible from James Ross's web site. This version is updated each time the code base is updated. As I understand the experimental version on the main web site is the one from James site built on fridays.

I have not given James web address, it can readily be found on google search.

I have been running the versions from James site now for ages and have never had any trouble with them.

Lindsay

[Rogue]

Hi,

got an additional question: on the old website, there was this list where every build had a short description about the change which has been made.
I'm missing this on the new website.
Is this information placed elsewhere ?

[James Ross]

 Rogue, on 24 July 2014 - 12:25 AM, said:

Hi,

got an additional question: on the old website, there was this list where every build had a short description about the change which has been made.
I'm missing this on the new website.
Is this information placed elsewhere ?

There is a similar set of information on one of my sites but it's not identical (it's not meant to be). I don't know if we want that information on the official website.

[markus_GE]

Personally, I´d say, if you offer downloads for supporters on the homepage, you should also provide them with information about recent changes which they might want to take a look at regarding how they work. IE, I also miss the recent changes info.

Cheers, Markus

[James Ross]

Given that it updates (semi-)automatically, it would seem better to see the information in the menu before/after applying the update. Would you agree?

[markus_GE]

We seem to be talking about two different thing.

I´m speaking about seeing a list of the changes made since the weekly release published before the current one on the website (I´m still of the old-fashioned "download-and-install-manually" attitude, in order to keep a library of a few (IE, currently about 100) older working copies of ORTS, so I can go back t an older one if something doesnßt work in a newer one).

You are, AFAICT, talking about showing said information also when using the auto updater.

Both ideas are essentially the same, and would be great to have, but they concern different "areas" of the program and it´s supporting network.

Cheers, Markus

[James Ross]

 markus_GE, on 24 July 2014 - 01:44 AM, said:

We seem to be talking about two different thing.

No, we're both talking about where we would like to see the list of changes to the experimental builds. Unless you believe a significant portion of people update experimental builds via the website (I don't, even if you personally do), that doesn't seem like the best place to put the information (people coming to the website will be going from the last stable, 0.9, to experimental, or new to OR).

[markus_GE]

That´s a way I´ve not seen it before. Point for you. Nevertheless, I think it would be good to have the chagelog easily accesible form the X release page, as sort of a backup should the auto-updater fail, or just if you want to look something up, but don´t have SVN-Tortoise installed. Might simply be done by putting the link you posted here on that page.

Cheers, Markus