ReleasePlan/ko

소개
Time-based release trains have been shown to produce the best quality Free software. A time based release is one that does not wait for either features, or bug fixes - but is based (as purely as possible) on time. This enforces discipline in introducing fixes, gives predictability, and allows more regular releasing. It is also the case that we will necessarily release earlier, and then rapidly, incrementally bug fix releases based on the previous stable version. Thus if you have a need for the very highest quality version, it can make sense to defer a move until the first or perhaps second minor point release.


 * 리브레오피스는 연 2회, 예측 가능한 출시를 합니다. 출시는 다른 무료 소프트웨어 프로젝트들(예를들면 Gnome)의 추세에 맞추어 진행됩니다. 그리고 그 출시들은 리눅스 배포출시보다 최소한 한달 먼저 진행됩니다.


 * Synchronizing time-based release schedule with the wider Free Software ecosystem also has huge advantages, by getting our new features, out to users as quickly as possible – with a minimum of distribution cycle lag. In consequence, we aim at six monthly releases, and over time nudge them to align well with the March/September norms.


 * Time-based release trains have been shown to produce the best quality Free software. A time based release is one that does not wait for either features, or bug fixes - but is based (as purely as possible) on time. This enforces discipline in introducing fixes, gives predictability, and allows more regular releasing. It is also the case that we will necessarily release earlier, and then rapidly, incrementally bug fix releases based on the previous stable version. Thus if you have a need for the very highest quality version, it can make sense to defer a move until the first or perhaps second minor point release.


 * There are 2 branches: Fresh (the newest release) and Still (the previous release), which are intended for mainstream feature users and conservative, corporate deployments respectively.


 * 그 결과, 사용자들은 6개월마다 넓은 범위로 새로운 기능, 수정, 그리고 기능이 향상된 버전을 이용할 수 있습니다. 추가로, 순수 버그 수정에 따른 소규모 출시도 많이 이루어집니다. The first X.Y.0 release is intended for early adopters. More conservative users are advised to wait for a later X.Y.Z bugfix release.

Note that the dates mentioned in the schedule might get shifted if there are serious technical or other problems with the release. An extra RC might be needed if the final release candidate does not fit the Release Criteria. Such problem would shift the final release by one week or even more.

The simplified graphic below shows three releases placed on a timeline consisting of 24 months.

Future Fresh Still

7.4 release
See also the detailed schedule and the release notes.

7.3 release
See also the detailed schedule and the release notes.

7.2 release
See also the detailed schedule and the release notes.

7.1 release
See also the detailed schedule and the release notes.

7.0 release
See also the detailed schedule and the release notes.

6.4 release
See also the detailed schedule and the release notes.

6.3 release
See also the detailed schedule and the release notes.

릴리즈 요일
릴리즈는 시간기반이지만 유연성을 위해서 스케쥴은 요일단위가 아니라 주(week) 단위로 이루어집니다. 릴리즈는 버그, 빌드 오류, 기술적 이슈에 의해 몇일정도 연기 될 수 있습니다.

릴리즈는 몇개의 베타버전과 릴리즈 빌드 후보군으로 이루어져있습니다. 각 빌드에 대해서 몇가지 작업이 필요합니다.

이상적인 워크플로우:


 * 월요일: 커밋 기한; reminder is sent to devel, l10n mailing list before it happens
 * 화요일: the tag is created on a commit that builds and passes unit-, subsequent-, and smoke-tests; tag is announced on the devel and qa mailing lists
 * 수요일: builds are uploaded on the early pre-release site; they are announced on the devel and qa mailing lists
 * 목요일: builds are uploaded on mirrors. They are announced via many channels, e.g. mailing lists, twitter
 * 금요일: 빌드들은 공식 사전릴리즈 사이트 에서 열람 가능합니다.

최종 릴리즈는 주로 최종 릴리즈 후보가 나오고 며칠 뒤인 목요일에 공지됩니다.

Note that we are very strict about commits to the final release candidate, so full regression test is not needed. It is used as the final build when it passes the needed tests. It is just renamed on mirrors.

스케쥴
스케쥴은 아래와 같은 규칙을 준수합니다:


 * do the major release every six months and synchronize it (at least one month ahead) with major Linux distributions; it always comes with a wide range of features, fixes, and enhancements
 * do a pure bugfix release every month after the main release until it is good enough even for the most conservative people; do it less frequently afterwards
 * do pure bugfix releases, including security fixes, until the next release is ready for most conservative people
 * do not do two builds the same week.

결과는 아래 템플릿을 따릅니다:

(초)는 해당 월 초, (중)은 해당 월 중순, (말)은 해당 월 말을 의미합니다.

String freeze
The release plans for the first version of each major release indicate a "hard English string & UI freeze". The idea is to make the lives of translators easier. The translators should be able to trust that no new translatable strings are added into the UI or Help files between the period of the string freeze and release.

After the first version of a major release is out, correcting mistakes in the UI and Help strings is fine. Any completely new content should target the next major release.

Version scheme
We do several builds around each release. The following versioning scheme is used:


 * X.Y.0.0.alphaZ - Zth alpha version of the initial release
 * X.Y.0.0.betaZ - Zth beta version of the initial release
 * X.Y.0.Z - Zth release candidate of the initial release, last rc is considered as final and put on the main download page
 * X.Y.1.Z - Zth release candidate of the 1st bugfix release, last rc is considered as final and put on the main download page

It seems to be the best compromise with the following advantages:


 * easy to understand for normal users, alpha, beta flags are known from other projects, so they set reasonable expectations
 * correct alphabetical sorting in RPM, Bugzilla
 * “easy” to parse (alpha/beta strings delimited by dot)

There was a long discussion about this scheme on the mailing list.

Accelerating the release cycle
This acceleration of the release cycle involves some considerable release engineering and QA effort. To reduce the cost of these, we work to provide complete (ie. containing all languages) daily snapshots of the master branch to allow continual testing of code improvements. This works partially already, as can be seen/downloaded from here.

Similarly, we plan to increasingly automate the build process to allow a much lower-touch release flow, and to continue to shrink the footprint of our binaries to allow far more rapid transfer of product-equivalent builds.

End-of-Life Releases
A release normally has a lifetime of around nine months. We consider a release to have reached its End of Life (EOL) one month after the last planned release.

If you want longer term support for a release, you’re encouraged to engage any certified L3 provider who could provide you with the service.

Because of the amount of data, the releases were split out to ReleasePlan/Archive.