Search results

* Ties into the Fedora Account System for candidate information and verifying voter eligibility. * Able to restrict access to information about who voted for a candidate to privileged users. Normal users can only read the results from the tally

== dist-f14-updates-candidate == == dist-f13-updates-candidate ==

There are fundamentally two different ways to release software. One is time-based, the other is feature-based. ...those are considered to be ''blockers''. A blocker has the power to stop a release or have the schedule adjusted, which happens frequently during the mileston

{{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] The following freeze policies are set for the following significant release milestones:

* [[QA/8/FinalTreeTesting| F8 Release Candidate]] ...abled in F8 Test 1. It is useful to test these specific items in the test release the feature was enabled subsequent test releases to make sure there are no

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Server|release=21|milestone=Beta|compose=TC1}}

...ths (3 weeks during test releases, a month from last test release to final release) during an already tight development cycle (6 months). This is no longer a ...that our CVS is set up we end up blocking developers from working on next release type changes or we wind up with these kind of changes landing in our tree t

Candidate builds during the [[PackageSubmissionQAPolicy| Fedora.us Package Submission ...for an example of us enforcing this policy. You will find packages needing candidate binary testing in the [http://www.fedora.us/PUBLISH PUBLISH Queue] .

= FC5 Final Pre-Release Test Coordination = ...gzilla. The release team will make the call as to whether bugs are a test release blocker or not.

The libpinyin 2.8 will provide phrase suggestion candidate and longer pinyin candidate features. * Targeted release: [https://docs.fedoraproject.org/en-US/releases/f38/ Fedora Linux 38]

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Base|release=21|milestone=Beta|compose=TC1}}

* Be able to build it as PDF to be printable. A good candidate for the FreeMedia program. * Screenshots (avoid need to update them with each release)

...owing [[Elections|elections]] take place at the end of the Fedora Linux 40 release cycle: == Candidate Nominations ==

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Server|release=21|milestone=Beta|compose=TC4}}

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Server|release=21|milestone=Beta|compose=TC2}}

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Server|release=21|milestone=Beta|compose=TC3}}

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Server|release=21|milestone=Beta|compose=RC1}}

...be sure you have been through the [[Preparing the Release Notes for final release]] and you have installed doc-publican-rpm. 1. Check the release notes out of the release git repo

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Final RC5 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Final TC3 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Beta RC2 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Beta TC2 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Final TC4 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Beta RC4 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Beta TC4 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Final TC1 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Beta RC1 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Final RC2 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Final RC4 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Final TC2 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Beta TC3 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res Fedora 21 Final RC1 [[QA:Release validation test plan|release validation]] summary. This page shows the results from all the individual r

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Server|release=21|milestone=Beta|compose=RC2}}

...owing [[Elections|elections]] take place at the end of the Fedora Linux 40 release cycle: == Candidate Nominations ==

...can be submitted to the release || New features must be submitted to next release || [https://fedorahosted.org/fesco/newtplticket Request exception from FESC ...n be submitted for the release || New spins must be submitted for the next release || Request exception from the [[SIGs/Spins | Spins SIG]]

...can be submitted to the release || New features must be submitted to next release || [https://fedorahosted.org/fesco/newtplticket Request exception from FESC ...n be submitted for the release || New spins must be submitted for the next release || Request exception from the [[SIGs/Spins | Spins SIG]]

= Fedora 12 Release Schedule = |rowspan="2"|<strike>2009-05-26</strike><br>2009-06-10||Fedora 11 Release

= Fedora 9 Release Schedule = | style="width:10em;" |8 Nov 2007||Fedora 8 Release--Fedora 9 Planning Begins (Features considered for approval)

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Cloud|release=21|milestone=Beta|compose=TC1}}

...owing [[Elections|elections]] take place at the end of the Fedora Linux 40 release cycle: == Candidate Nominations ==

= Fedora 11 Release Schedule = |rowspan="2"|2008-11-25||Fedora 10 Release

...owing [[Elections|elections]] take place at the end of the Fedora Linux 40 release cycle: == Candidate Nominations ==

...d, reduce the chances of receiving an exception, and potentially delay the release.}} ...he Final Freeze no changes are allowed to any packages except for critical release blocking bug fixes.

= Fedora Release Engineering Meeting :: Monday 2007-09-17 = ...-f8 again after test3 freeze. Builds will auto tag and show up in rawhide/release.

...neering meet to determine if the release criteria are met for a particular release. This meeting is called the: '''Go/No-Go Meeting'''. ...epository or previous releases updates repository. QA does not approve the release if there are any accepted blocker bugs that are unaddressed or if validatio

{{Admon/note | Fedora 13 Schedule | This is the release schedule for Fedora 13. Other schedules are maintained for historical purpo See [[Important_Release_Milestones | important release milestones]] for more details.

Each '''Release Candidate''' version of PHP are build in rawhide, so regressions can be detected as s

The objectives of the Alpha release are to: ...llable media versions of a [[Feature_Freeze_Policy|feature complete]] test release

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Base|release=21|milestone=Beta|compose=TC3}}

== Release Candidate packages == ...epo] available for providing the latest openstack packages irrespective of release freeze scheduling.

The objectives of the Beta release are to: ...ease: Beta is the last widely co-ordinated test release point in any given release cycle

...fairly low since finer-grained control can be applied to specific product/release branches. ...on master. Developers use their best judgment (and get the consent of the release lead for fX) before cherry-picking patches from master and pushing them to

{{Admon/note | Fedora 14 Schedule | This is the release schedule for Fedora 14. Other schedules are maintained for historical purpo <!-- See [[Important_Release_Milestones | important release milestones]] for more details. --><!-- This page is Fedora 13 content, and

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Base|release=21|milestone=Beta|compose=TC4}}

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Base|release=21|milestone=Beta|compose=TC2}}

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Base|release=21|milestone=Beta|compose=RC2}}

!style="width:7em;"|Release: | <code>1.0</code> || <code>1%{?dist}</code> || The first release.

{{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] Every release prior to the Feature Freeze we deprecate all packages that [[FTBFS]]. This

{{Quote|You can't know if you're ready to release unless you know what ''done'' means.<br> ...ogress through the project and up to the final release. Then you can say 'Release it!' with pride.|[http://www.universityalliance.com/info1/whitepapers/villa

The objectives of the Alpha release are to: ...llable media versions of a [[Feature_Freeze_Policy|feature complete]] test release

Update GNOME to the latest upstream release * Targeted release: [[Releases/20 | Fedora 20 ]]

...to be in a different path to allow rawhide to race forward toward the next release. release, instead of the packages in the ever rolling development tree that is rawhi

| 2009-08-25 || Alpha Release | 2009-10-13 || Beta Release

* Either someone with enough free time will start work on packaging pre-release snapshots or the work will start when upstream has tagged the packages. ...s.trolltech.com/blogs/2009/11/17/qt-460-release-candidate-1/ First release candidate of upcoming Qt 4.6 was released].

The objectives of the Beta release are to: ...ease: Beta is the last widely co-ordinated test release point in any given release cycle

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res ...t_plan|validation testing]] test results for the Fedora '''21 Alpha TC1''' release.

...y. If the build is still a candidate for release, then use the appropriate candidate tag. It might be useful to look at the tagging history of the build. For ex ...2 03:42:02 2022 golang-uber-ratelimit-0.2.0-1.fc37 tagged into f37-updates-candidate by mikelo2

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Base|release=21|milestone=Beta|compose=RC1}}

* Release notes owner: TBA * Targeted release: [[Releases/21|Fedora 21]]

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res ...t_plan|validation testing]] test results for the Fedora '''21 Alpha TC7''' release.

...number of blocker bugs identified. The team was able to contribute to the release eventually going ahead with only a one week slip to the Beta schedule and n === Release criteria updates ===

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res ...t_plan|validation testing]] test results for the Fedora '''21 Alpha TC6''' release.

#**# FESCo / Release Engineering #** FESCo / Release Engineering needs presence at the Spin SIG meetings in order to chime in on

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Desktop|release=21|milestone=Beta|compose=TC2}}

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res ...t_plan|validation testing]] test results for the Fedora '''21 Alpha TC5''' release.

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Desktop|release=21|milestone=Beta|compose=TC4}}

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Desktop|release=21|milestone=Beta|compose=TC3}}

The objectives of the Beta release are to: ...ease: Beta is the last widely co-ordinated test release point in any given release cycle

| Fedora 13 Release | [[Fedora_14_Alpha_Release_Criteria|Alpha Release]]

The objective of the Final release is to: # Provide a polished final release suitable for meeting the needs of our ''Target Audience''

...nd fix issues in Fedora so we can get fixes back upstream before the final release. ...ill be rebased in the next Fedora release. Make sure to follow the Fedora release schedule and file the change proposal before the Change Checkpoint.

| 2009-02-03 || Alpha Release | 2009-03-24 || Beta Release

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res ...t_plan|validation testing]] test results for the Fedora '''21 Alpha RC1''' release.

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res {{Release_validation_instructions|testtype=Desktop|release=21|milestone=Beta|compose=TC1}}

...Between releasing a new release and the next release's first alpha release candidate's due date. ...the test plans and test cases from above. For every single release and re-release.

* Targeted release: [[Releases/15 | Fedora 15 ]] ...al release of LibreOffice before the release of Fedora 15 should be 3.4.0 release on 05/02/2011.

...ion_test_plan]]. This page provides guidance on arranging and announcing a release validation test event. For any concerns, please contact the [[QA]] group. {{admon/caution|This process is now automated|The creation of release validation test events is now automated. Wiki pages are created and an anno

|rowspan="2" | 2009-11-17 ||colspan="2"| Fedora 12 Release | 2010-03-02 ||colspan="2"| Alpha Release

...his means that one update candidate cannot be built against another update candidate without rel-eng interaction. That interaction is to tag a build for an "ov $ for release in {12..13}; do ./clean-overrides.py dist-f$release-{override,updates}; done

...inations. The current members of FLSCo will continue to serve for one more release. ...each voter as many votes as there are open seats. They may vote for each candidate only one time, and can use as many or few of their votes as they wish.

The objectives of the Beta release are to: ...ease: Beta is the last widely co-ordinated test release point in any given release cycle

The objective of the Final release is to: # Provide a polished final release suitable for meeting the needs of our ''Target Audience''

The objectives of the Alpha release are to: ...llable media versions of a [[Feature_Freeze_Policy|feature complete]] test release

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res ...t_plan|validation testing]] test results for the Fedora '''21 Alpha TC7''' release.

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res ...t_plan|validation testing]] test results for the Fedora '''21 Alpha TC1''' release.

|Lock dist-fc5-updates-candidate collection in internal build system||JesseKeating||'''DONE''' [[Category:Release Engineering]]

== Fedora 8 Pre-Release Test Coordination == The current public release candidate is RC3, which is available on http://torrent.fedoraproject.org/.

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res ...t_plan|validation testing]] test results for the Fedora '''21 Alpha TC5''' release.

{{admon/important|No longer current|This candidate is no longer the current milestone. For the latest results, see [[Test_Res ...t_plan|validation testing]] test results for the Fedora '''21 Alpha TC6''' release.

* Targeted release: [[Releases/17 | Fedora 17 ]] ...nterface for OpenStack, and will be a core component of the next OpenStack release scheduled for April 2012. Horizon provides graphical means for users to sta