Release cycle sr CS

Ciklus izdanja

ASF koristi opšte C# verzije sa 4 broja, napisane kao A.B.C.D. Data verzija je uvijek zaleđena, što znači da je tim označen izvorni kod iz kojeg je ista napravljena (upakovan zajedno sa izdanjem). Mi ne brišemo prethodno izdate verzije, sve dok naš hosting provajder (GitHub) nema ništa protiv njihovog arhiviranja za budućnost, i zbog toga možete se sigurno vratiti bilo kojoj verziji bez potrebe da i vi pravite lične kopije.

Opšte, u pogledu ASF verzija, mi dajemo sve od sebe da pratimo semver način označavanja verzija koristeći šemu GLAVNO.SPOREDNO.POPRAVKA označavajući ih sa 3 najmanje značajna broja - B.C.D. Ova tri broja su direktno povezana sa ASF kodom. The most significant A number indicates changes with a scope that goes beyond ASF codebase itself, usually directly affecting the foundation of the program.

ASF as a project is aiming to have more or less one feature release per month, indicated by a bump of C number. In order to make such release possible, we have smaller pre-releases dedicated to advanced users, which serve as smaller milestones of changes that are released on as-needed basis when there will be enough of changes since the last pre-release to focus on. Eventually, when a final pre-release will be determined to be stable and mature enough with no known critical regressions that should be corrected compared to previous stable release, it'll be marked as the new stable release, at the same time opening a new monthly cycle for the next one.

While we're doing our best to ensure that even our pre-releases are relatively stable, it should be noted that pre-releases aren't supposed to be used in any production environment. Pre-releases might have critical bugs and otherwise broken functionality, which is exactly why we're releasing them to begin with - so we can avoid all of that mess in our stable builds and offer reliable software. If you're unwilling to accept higher risk that comes from using potentially unstable software, please avoid using our pre-release builds and stick with our latest stable build instead, which is more appropriate for majority of users.

Depending on amount of changes in the cycle, usually there will be a single C version bump (from previous stable), and D bumps for every pre-release. However, when introducing changes with far bigger scope, especially breaking changes, the cycle might start from (or switch in the middle) to B or even A bump - such switch indicates that current release cycle has a potential to be more unstable than usual, and should be tested carefully. Keep in mind that semver changes we're making relate only to previously released stable version, we do not track versioning across pre-releases in a cycle themselves, which means that version 1.0.1.2 might have a new feature that 1.0.1.1 didn't have, as long as the previously marked stable release is from 1.0.0 family. Likewise, there could be major breaking changes even across two pre-releases from the same cycle, which is especially true when we're still deciding about the final shape of newly-introduced functionality or similar.

Verzija	Semver	Sadržaj promjena
A		Major .NET runtime changes, foundation changes, breaking changes that are beyond ASF's codebase
B	Glavno	Minor .NET runtime changes, breaking changes in ASF codebase, major code edits that go beyond minor classification
C	Sporedno	New monthly cycles, usually introducing new functionalities, commands, configuration properties or other changes that do not break the existing setups
D	Popravka	New pre-releases that are part of existing cycle (indicated by more significant number), critical bugfixes that introduce no code changes beyond necessary

Please note that newly introduced features and changes may be undocumented (e.g. on the wiki) until some time later, as documentation is usually written once final code of given feature is ready (to save us time rewriting documentation each time we decide to modify the feature we're currently working on). Due to the fact that pre-release may contain work-in-progress code that doesn't have a final form yet, documentation may arrive at later stage of the development. Same thing applies to general changelog that may be unavailable for given pre-release until some time later. Therefore if you decide to use pre-release then be prepared for looking inside ASF commits from time to time. Of course, lack of documentation applies only to pre-releases - each stable version must always have a complete changelog and documentation on the wiki the moment it's being released.

The precise changelog that compares one version to another is always available on GitHub - through commits and code changes. In release we tend to document only changes we consider important between last stable and current release. Such brief changelog is never a complete one, so if you'd like to see every change that happened between one version and another - please use GitHub for that.

ASF project is powered by our continuous integration process. Every build is supposed to be reproducible, therefore it should not be a problem to grab source (included in the release) of given version and compile yourself receiving the same result as the one available through our precompiled binaries. We typically avoid compiling releases ourselves, the released binaries come directly from our CI process.