2018.1 Release ToDos #2700

Open
LinuxDonald opened this Issue Jun 2, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@LinuxDonald
Member

LinuxDonald commented Jun 2, 2017

Fife 0.4.2 Release Date: XX.XX.2018
Fifechan 0.1.5 Release Date: XX.XX.2018
UH 2018.1 Release Date: XX.XX.2018

Issues Open for UH 2018.1:
https://github.com/unknown-horizons/unknown-horizons/milestone/29

Open Muliplayer Issues:
https://github.com/unknown-horizons/unknown-horizons/milestone/30

Multiplayer should fixed for this Release.

Changelog must be updated.

@MarkusHackspacher

This comment has been minimized.

Show comment
Hide comment
@MarkusHackspacher

MarkusHackspacher Jun 5, 2017

Contributor

Other Idea, let call UH2017 for all Version with python 2. If fix a fault in 2017.2 call it 2017.3.
And for the base with python 3 call it UH2018 and to make a release with the actual code base UH2018 beta 1.
It is because the linux distributions like Debian have a stable and a testing branch, in the moment is UH2017.1 in Debian testing, goes at 17. June in the stable branch for the next two years.
So go only bugfixs the 2017.x and the distributions have a stable version.
And to call UH2018 beta 1 to get a greater attention in the social media, so that it is also visible to the outside that it goes on. And attracts a larger number of users to which also write a bugreport

Contributor

MarkusHackspacher commented Jun 5, 2017

Other Idea, let call UH2017 for all Version with python 2. If fix a fault in 2017.2 call it 2017.3.
And for the base with python 3 call it UH2018 and to make a release with the actual code base UH2018 beta 1.
It is because the linux distributions like Debian have a stable and a testing branch, in the moment is UH2017.1 in Debian testing, goes at 17. June in the stable branch for the next two years.
So go only bugfixs the 2017.x and the distributions have a stable version.
And to call UH2018 beta 1 to get a greater attention in the social media, so that it is also visible to the outside that it goes on. And attracts a larger number of users to which also write a bugreport

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald Jun 5, 2017

Member

we dont have any bug fixes for 2017.2 Version. All changes are python3 based.

Member

LinuxDonald commented Jun 5, 2017

we dont have any bug fixes for 2017.2 Version. All changes are python3 based.

@MarkusHackspacher

This comment has been minimized.

Show comment
Hide comment
@MarkusHackspacher

MarkusHackspacher Jun 5, 2017

Contributor

Ok, if one day a bugfix goes into 2017.2 than call it 2017.2.1.
But I mean use not 2017 for the python 3 code base. In my opinion it is better to call it 2018.x. Or now 2018 beta 1.

Contributor

MarkusHackspacher commented Jun 5, 2017

Ok, if one day a bugfix goes into 2017.2 than call it 2017.2.1.
But I mean use not 2017 for the python 3 code base. In my opinion it is better to call it 2018.x. Or now 2018 beta 1.

@LinuxDonald LinuxDonald added this to the 2017.3 milestone Jun 10, 2017

@LinuxDonald LinuxDonald changed the title from 2017.3 Release ToDos to 2018.31 Release ToDos Jun 27, 2018

@LinuxDonald LinuxDonald changed the title from 2018.31 Release ToDos to 2018.1 Release ToDos Jun 27, 2018

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