藍圖¶

開發階段¶

在開發階段，開發者致力於新版本中添加新功能。先期使用者可以使用我們為所有主要平台提供的夜間建構版來查詢開發進度，進行初步測試、提供錯誤報告與想法供開發使用。

功能凍結¶

在功能凍結期間，新功能無法再新增會將重點轉向提高QGIS的穩定性。這也有效使每夜建構版轉為 預先發行版。

Users should start extensive testing of these prereleases in their environment to verify that there are no issues, they wouldn't want to see in the upcoming release. All such issues should be reported (see Bugs, Features and Issues). Everything that goes unnoticed, will also end up in the next release. Only in case of serious problems backports to a latest release will occur. Therefore testing of the prereleases and reporting issues is very important.

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.

發布管理員於功能凍結時宣布此事

釋出¶

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.

發布日程表¶

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.

2.12版本起，版本開發週期皆固定為12周而凍結期至少為5周。其餘時間則用於延長長期發行版發布的凍結期。

如果軟體有進行向後移植 (backport) 進行舊版本修補的動作，則每個月會在最新發布的分支上發布小數點版本。自3.28版本後，僅有最新版本可發布小數點版本。

版本發行後的首四個月，新的長期發行版即為固定發行版。 在此期間，新的長期發行版不會取代長期發行版資料庫中舊的長期發行版。一旦新版本的固定發行版發布後，就會發生資料庫取代的情況。

此期程表亦可在`"iCalendar" </schedule.ics>`_中獲取

預備發行版/每夜建構版安裝檔位置¶