Post by Admin on Jan 2, 2017 20:32:32 GMT
As some of you may have noticed, the Stable released as 2.0, is a departure from our previous versioning system. This is a reflection of our new development strategy, which, while slightly more complicated, will result in a better experience for users.
Common practice in the past when someone came to the forum and asked for help because they couldn't get the toolset to work was to tell them to download the latest developer release and see if that fixed it. This should no longer happen. The average user, who is using the toolset to install mods, should never be directed to the Beta releases; they should stick with the current Stable. If there is a critical bug in the latest Stable, then the Stable will be updated.
The Beta releases are now a separate branch, and the only people who should be using them are advanced users (mod creators) who want the bleeding edge changes and are prepared to deal with (and report) bugs.
So, in light of this, the new versioning system will work like this:
The first Beta release, 2.0.1, is already up.
Related to this, a special announcement regarding kfreon 's tools: Texplorer, TPF Tools, and ModMaker. Kfreon has forked his tools from the rest of the toolset in preparation for a total re-write. Any changes to these tools will exist outside of the toolset until the re-write is complete, and the toolset are tested and verified as stable. From there they will be merged back in.
This means that bugs for these tools should not be reported on the toolset's GitHub. These tools are in archival state as far as the toolset is concerned. They will not be modified.
Rules regarding bug reports to K's own GitHub fork are as follows:
DO report
DON'T report
These rules are due to things that are going to be completely rewritten e.g. the UI, so reporting "this button breaks" is pointless since that button won't even exist in its current form.
Common practice in the past when someone came to the forum and asked for help because they couldn't get the toolset to work was to tell them to download the latest developer release and see if that fixed it. This should no longer happen. The average user, who is using the toolset to install mods, should never be directed to the Beta releases; they should stick with the current Stable. If there is a critical bug in the latest Stable, then the Stable will be updated.
The Beta releases are now a separate branch, and the only people who should be using them are advanced users (mod creators) who want the bleeding edge changes and are prepared to deal with (and report) bugs.
So, in light of this, the new versioning system will work like this:
- Stable releases will be 2.0, 2.1, 2.2, .... 3.0 and so forth
- Beta releases will be whatever the current stable is plus a third number: 2.0.1, 2.0.2, etc
The first Beta release, 2.0.1, is already up.
Related to this, a special announcement regarding kfreon 's tools: Texplorer, TPF Tools, and ModMaker. Kfreon has forked his tools from the rest of the toolset in preparation for a total re-write. Any changes to these tools will exist outside of the toolset until the re-write is complete, and the toolset are tested and verified as stable. From there they will be merged back in.
This means that bugs for these tools should not be reported on the toolset's GitHub. These tools are in archival state as far as the toolset is concerned. They will not be modified.
Rules regarding bug reports to K's own GitHub fork are as follows:
DO report
- Texture issues: Things like colours being wrong, image files not loading in the IMAGE ENGINE tool.
- UI improvements: Things like, search bar should do something else, a button that does this, a new panel that shows these things.
- unctionality enhancements: explain what it offers that isn't already there, and a brief example of what kind of thing you're thinking of
DON'T report
- UI issues: animations not working, things staying deselected, thumbnails not generating, breaking when you click a button.
- Poor performance
- Image files not loading through TPFTools or Texplorer but working in ImageEngine
- Autofix/scan issues
- Format detection issues
These rules are due to things that are going to be completely rewritten e.g. the UI, so reporting "this button breaks" is pointless since that button won't even exist in its current form.