Search results

There is a need to handle post-release tags in a similar fashion to pre-release tags. Post-release packages: Packages released after a "final" version.

* 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

...re 6 release did not need to be rebuilt for the Red Hat Enterprise Linux 5 release. ...507 total that have the .fc6 tag. The Server version of that same release candidate has 252 packages with the .fc6 tag out of 2108.

== 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

...on Deadline||Development Freeze||Preview Release||Release Candidate||Final Release||Update Testing | 2009-02-03 || Alpha Release

{{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] .

...meet pre-defined quality standards. You can find the requirements for each release in the [[Fedora_Release_Criteria]]. ...sktop validation testing. These test cases are designed to ensure that the release under testing complies with the [[Fedora_Release_Criteria]]: the test cases

...e to work around the bug and complete this test and discover no artwork or release identification issues, you may still report a 'pass' for this test. If the ...lease candidate, there should nothing that identifies the release as a pre-release of any kind.

= 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.

## RELEASE NOTES: ## Preview - PR-22: Freeze wiki release notes, make snapshots of all Beats

...der to be released to the general public, the {{{prerelease|PRE-RELEASE}}} Candidate (RC) must meet all of the following criteria. This is intended to make the ...nt to determine whether or not the issue should be considered to block the release. They should consider the number of users likely to be affected by the issu

|rowspan="2"|<strike>2009-05-26</strike><br>2009-06-10||Fedora 11 Release | <strike>2009-08-18</strike><br>2009-08-25 || Alpha Release

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]

...m they get appended to what would be the classical Release tag, i.e. ''the Release tag gets suffixed with a disttag''. ...instance. It is composed out of the abbreviated distribution name and the release's version.

{{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}}