All 3.3 test participants: For any newly-discovered bugs during testing, please continue to use the tracker to report them, but use "Fedora trunk" as the "Affects Version" if the issue was not present in the prior release (3.2.1). Combined with the 3.3 Test Plan page, this should give us an easy way to keep track of any fixes that MUST be completed before release day.
Relevant JIRA search: (Blockers are the only items that will hold up release if not fixed) https://fedora-commons.org/jira/secure/IssueNavigator.jspa?reset=true&&type=1&pid=10051&resolution=-1&version=10170&sorter/field=issuekey&sorter/order=DESC&sorter/field=priority&sorter/order=DESC Thanks, Chris Background: How "Fedora trunk" is used in JIRA: Affects Version: Fedora trunk Normally when issues get opened, they're reported only against the released versions of Fedora to which they apply. But it's useful to keep track of problems that have been introduced after the latest release. For this purpose, please use "Fedora trunk" as the sole "Affects Version" value. When a release against trunk is completed, any still-open items with "Fedora trunk" as their "Affects Version" will be modified to refer to the current released version. Fixed For: Fedora trunk Often, just after a release, we aren't sure what the next released version will be. In these cases, if the fix goes in before we know, please use "Fedora trunk" as the "Fixed For" value. When we know what the next version will be, these can be bulk-modified to use that version. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
