New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2017.2 advertising 2017.1 as newer release #2682

Closed
squiddy opened this Issue May 17, 2017 · 12 comments

Comments

Projects
None yet
2 participants
@squiddy
Member

squiddy commented May 17, 2017

Just installed Unknown-Horizons-2017.2.147-Setup-VC14-x86.exe on Windows 7 and was greeted with this:

2017-05-17 17_47_21-program manager

There is a newer version (2017.1) available than the one you're currently using (2017.2)

I would expect to not see this message at all. Also, the logfile path seems broken, I'm assuming it has something to do with the formatting.

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald May 17, 2017

Member

It's an error with Web server. Last time Nightraven must update it on server side. I don't know how and where to change it to an new system.

Member

LinuxDonald commented May 17, 2017

It's an error with Web server. Last time Nightraven must update it on server side. I don't know how and where to change it to an new system.

@squiddy

This comment has been minimized.

Show comment
Hide comment
@squiddy

squiddy May 17, 2017

Member

I don't know how and where to change it to an new system.

I haven't put much thought into it, but essentially it's just some static information at a given URL. Probably some JSON with the newest release version and link.

Something we could easily host with GitHub on our new homepage, e.g. http://unknown-horizons.org/release-data.json

Member

squiddy commented May 17, 2017

I don't know how and where to change it to an new system.

I haven't put much thought into it, but essentially it's just some static information at a given URL. Probably some JSON with the newest release version and link.

Something we could easily host with GitHub on our new homepage, e.g. http://unknown-horizons.org/release-data.json

@squiddy

This comment has been minimized.

Show comment
Hide comment
@squiddy

squiddy May 17, 2017

Member

http://updates.unknown-horizons.org/current_version.php is the URL we're calling, the response is simply

2017.1
http://www.unknown-horizons.org

I see no reason why we couldn't update the URL for the new release to http://unknown-horizons.org/current-version.json and host that information statically.

Member

squiddy commented May 17, 2017

http://updates.unknown-horizons.org/current_version.php is the URL we're calling, the response is simply

2017.1
http://www.unknown-horizons.org

I see no reason why we couldn't update the URL for the new release to http://unknown-horizons.org/current-version.json and host that information statically.

@squiddy

This comment has been minimized.

Show comment
Hide comment
@squiddy

squiddy May 17, 2017

Member

@LinuxDonald It would still be good to have the current file be updated, I was quite surprised to see that pop up right after start.

Member

squiddy commented May 17, 2017

@LinuxDonald It would still be good to have the current file be updated, I was quite surprised to see that pop up right after start.

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald May 17, 2017

Member

@squiddy could you maybe add that file? I don't know how to write/ how it must look like.

Member

LinuxDonald commented May 17, 2017

@squiddy could you maybe add that file? I don't know how to write/ how it must look like.

@squiddy

This comment has been minimized.

Show comment
Hide comment
@squiddy

squiddy May 17, 2017

Member

I'm going to open a new issue to track the implementation. We should leave this one open to fix the current version info.

Member

squiddy commented May 17, 2017

I'm going to open a new issue to track the implementation. We should leave this one open to fix the current version info.

@squiddy

This comment has been minimized.

Show comment
Hide comment
@squiddy

squiddy Jun 9, 2017

Member

@LinuxDonald Any news on this? The next release will use the new version check, but this should still be fixed if possible.

Member

squiddy commented Jun 9, 2017

@LinuxDonald Any news on this? The next release will use the new version check, but this should still be fixed if possible.

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald Jun 9, 2017

Member

For an fix we would need an backport. Then we could release an hot fix.

Member

LinuxDonald commented Jun 9, 2017

For an fix we would need an backport. Then we could release an hot fix.

@squiddy

This comment has been minimized.

Show comment
Hide comment
@squiddy

squiddy Jun 9, 2017

Member

Why can't we just change the version on the existing server? You said:

Last time Nightraven must update it on server side.

Why can't we do it now one last time?

Member

squiddy commented Jun 9, 2017

Why can't we just change the version on the existing server? You said:

Last time Nightraven must update it on server side.

Why can't we do it now one last time?

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald Jun 9, 2017

Member

Because its very hard to get into contact with him :( Sometime it takes months

Member

LinuxDonald commented Jun 9, 2017

Because its very hard to get into contact with him :( Sometime it takes months

@squiddy

This comment has been minimized.

Show comment
Hide comment
@squiddy

squiddy Jun 11, 2017

Member

I see. Perhaps a backport is indeed necessary here.

Member

squiddy commented Jun 11, 2017

I see. Perhaps a backport is indeed necessary here.

@squiddy squiddy self-assigned this Jun 11, 2017

@squiddy squiddy added this to the 2017.2.1 milestone Jun 13, 2017

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald Jul 20, 2018

Member

Next release will be 2018.1 not update planed for the old release anymore.

Member

LinuxDonald commented Jul 20, 2018

Next release will be 2018.1 not update planed for the old release anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment