search

CitiesSkylinesMods / TMPE

Cities: Skylines Traffic Manager: President Edition
https://steamcommunity.com/sharedfiles/filedetails/?id=1637663252
MIT License
571 stars 85 forks source link

Change title of LABS version of the mod #164

Closed originalfoo closed 5 years ago

originalfoo commented 5 years ago

To help differentiate which version of the mod a user has active, could we append "LABS" to the mod name for the upcoming labs branch?

I've no idea how to make that work consistently, other than perhaps a conditional based on workshop id?

Also, what are we going to do about milestone names in github?

AllegedlyLuca commented 5 years ago

I think perhaps a new versioning system should be adopted as well, to reflect which version of TMPE the experimental/beta version is based from (or to indicate the latest prior stable release).

Currently, TMPE is 1.10.14, while this experimental version is 1.10.16. I'd propose 1.10.14.X or 1.10.14.Xb with the lowercase b standing for beta.

originalfoo commented 5 years ago

That would work for milestone names in github as well @krzychu124 ?

VictorPhilipp commented 5 years ago

IMO we could remove the "1." prefix entirely.

Just increment major build number for every new feature version, and increment minor build number for every fix (11.0, 11.1, ... , 12.0, 12.1, 12.2, ...). If we plan to implement a strict migration scheme (I would suggest that) such that each labs version will eventually become stable then we don't need the "b" suffix. Labs would then always be exactly one major version ahead of stable.

Proposed process: New features are rolled out first on labs (say v12.0) while stable remains on the previous version (v11.0) for some time. If a bug is found and fixed, all affected live versions are updated, such that stable becomes v11.1 and labs becomes v12.1 if both are affected. When a feature is ready for stable, the current labs version (v12.1) becomes the new stable and the new labs version is incremented (v13.0). A bugfix for stable OR labs only increments the corresponding minor version.

krzychu124 commented 5 years ago

I like this idea and I think that it is possible to create one more project in Appveyor for easier version managing. I'll check that later.

originalfoo commented 5 years ago

Can we also ensure auto-build numbering in the AssemblyInfo.cs? (if it's not already there - would check but I currently have about 40 browser tabs and 30+ VS2017 tb open and my brain is thinking of herding mountain goats again)

VictorPhilipp commented 5 years ago

Auto-build numbering is already active