Harmonogram¶

Fazy rozwoju¶

In the development phase, developers work on adding new features for the next release. Early adopters can use the nightly builds we have for all major platforms to see the development progress, do preliminary testing and provide bug reports and their thoughts to help with development.

Zamrożenie¶

In the feature freeze phase, new features are not allowed in anymore and the focus of everyone moves from enhancing QGIS to stabilizing it. This also turns the nightly builds effectively into prereleases.

Użytkownicy powinni zacząć intensywne testowanie wydań wstępnych w swoich środowiskach, aby zweryfikować, że nie ma błędów, których nie chcieliby widzieć w kolejnym wydaniu. Wszystkie takie błędy należy zgłaszać (zobacz Błędy, funkcje i problemy). Wszystko co nie zostanie zauważone, wyląduje również w kolejnym wydanie. Backporty do wcześniejszego wydania mają miejsce tylko w przypadku poważnych problemów. Z tego powodu testowanie wydań wstępnych i zgłaszanie błędów jest niezmiernie ważne.

In the feature freeze, developers monitor the bugtracker and start working on fixing the reported issues and update the visual changelog with the features they added.

With the start of the feature freeze, the translation files will be updated so that translators can start their work. Note that this might be an incremental process as although the features are frozen, bug fixes might still introduce translation string changes.

Two weeks before the release, a hard freeze is initiated after which only fixes to severe problems and regressions introduced after the feature freeze are allowed in.

The release manager announces this on feature freeze.

Wydanie¶

On major and minor release dates, the release branch is created and the release is tagged and tar balls are prepared. Point releases are just tagged and tar balls are created.

The packagers are notified that packaging can begin.

Once some packages are available the release can be announced and the website is updated accordingly.

Harmonogram wydań¶

The schedule is aligned to produce roughly the same dates for each year given our four monthly releases with LTRs entering the LTR repo in late february.

Począwszy od okresu po wydaniu 2.12, faza rozwoju zajmuje zawsze 12 tygodni, a faza zamrożenia co najmniej 5 tygodni. Pozostały czas jest przeznaczony na wydłużenie zamrożenia przy wydaniach LTR.

Point releases will happen every month on the latest release branch branch, if there are backports. Beginning with the 3.28 release point releases are only done with new latest releases.

In the first four months after its release, a new LTR is also the current LR. In this phase, the new LTR doesn’t replace the previous LTR in the LTR repositories. This happens as soon as a new LR is released.

This schedule is also available as „iCalendar”.

Położenie wydań wstępnych / conocnych kompilacji¶