From Fedora Project Wiki
(→‎Current status: add approximate Fedora 18 schedule and mark feature as being for Fedora 18)
m (→‎Comments and Discussion: fix "Talk" link)
Line 117: Line 117:


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/Python_3.2]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
* See [[Talk:Features/Python_3.3]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->





Revision as of 00:30, 14 April 2012


Python 3.3

Summary

Update the Python 3 stack in Fedora from 3.2 to 3.3

Owner

  • Email: <dmalcolm@redhat.com>

Current status

  • Targeted release: Fedora 18
  • Last updated: 2012-04-13
  • Percentage of completion: 0%
Month Python 3.3 release schedule) Fedora 18 Schedule Fedora 19 Schedule
March 3.3.0 alpha 1: March 3, 2012
3.3.0 alpha 2: March 31, 2012
April 3.3.0 alpha 3: April 28, 2012
May 3.3.0 alpha 4: May 26, 2012
June 3.3.0 beta 1: June 23, 2012: (No new features beyond this point.)
July 2012-07-12 Feature Submission Deadline
3.3.0 beta 2: July 14, 2012
2012-07-26 Feature Freeze--Planning & Development Ends
3.3.0 candidate 1: July 28, 2012
August 2012-08-02 Software String Freeze
2012-08-02 Alpha Change Deadline
3.3.0 candidate 2: August 11, 2012
2012-08-16 Alpha Release
3.3.0 final: August 18, 2012
2012-08-30 Software Translation Deadline
September 2012-09-06 Beta Change Deadline / Features 100% Complete
2012-09-20 Beta Release
October 2012-10-10 Final Change Deadline
2012-10-11 Compose 'Final' RC
2012-10-25 Fedora 18 Final Release

Note: Fedora 18 schedule not yet available, so I've based the above on the (original) Fedora 16 schedule, offsetting by a year

Detailed Description

Benefit to Fedora

Fedora aims to showcase the latest in free and open source software - we should have the most recent release of Python 3.

Scope

How To Test

Interested testers do not need special hardware. If you have a favorite Python 3 script, module, or application, please test it with Python 3.3 and verify that it still works as you expect.

My own test plan:

  • Smoketest of the interpreter
  • Run the upstream regression test suite (this is done during %check)

User Experience

Users should not notice any difference, other than the availability of the 3.3 interpreter

Dependencies

See notes in "Scope" above.

Contingency Plan

Documentation

Release Notes

Comments and Discussion