From Fedora Project Wiki
< Changes
(Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To re...") |
m (→Owner) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<!-- Self Contained or System Wide Change Proposal? | <!-- Self Contained or System Wide Change Proposal? | ||
Use this guide to determine to which category your proposed change belongs to. | Use this guide to determine to which category your proposed change belongs to. | ||
| Line 36: | Line 34: | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
* Email: spot@fedoraproject.org | * Email: spot@fedoraproject.org | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->[mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]]) | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
| Line 46: | Line 44: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/24 | Fedora 24 ]] | * Targeted release: [[Releases/24/ChangeSet | Fedora 24 ]] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 56: | Line 54: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1255786 #1255786] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 124: | Line 122: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: (What to do? Who will do it?) Roll back to texlive-2014 packages. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency mechanism: (What to do? Who will do it?) Roll back to texlive-2014 packages. spot or rel-eng can do this. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: Beta freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: Beta freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 144: | Line 142: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF24]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 21:17, 22 April 2016
TeXLive 2015
Summary
Update Fedora TeXLive packaging to 2015.
Owner
- Name: Tom Callaway
- Email: spot@fedoraproject.org
- Release notes owner: Simon Clark (sclark)
Current status
Detailed Description
Fedora's core latex support comes from TeXLive. We've been on 2014 for a while now, and 2015 is out. Time to upgrade! Since lots of things use latex to generate documentation, the scope of this update is wide.
Benefit to Fedora
TeXLive fixes a large number of bugs and adds new components with every new release. Various upstreams will eventually expect to be able to take advantage of these, not to mention the TeX power users. I'm sure there are a few still alive. ;)
Scope
- Proposal owners: Actually update texlive package to 2015 sources. Ideally, have a mass rebuild in the 24 release cycle to catch any odd breakage cases, if no mass rebuild, identify packages with BR on texlive* and manually rebuild.
- Other developers: If your package depends on latex/TeXLive, rebuild to make sure that everything works properly and renders correctly.
- Release engineering: Mass rebuild would be ideal, however, if this is the only thing that needs it, we can do a targeted rebuild of packages that BR: texlive*
- Policies and guidelines: No new policy/guideline changes required.
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
Upgrade tested. No manual config/data migration needed. Behavior should be consistent.
How To Test
Rebuild documentation that generates with latex/texlive. Compare it to docs generated with old texlive 2014 packages. They should be identical (or in very few cases, actually better with 2015).
User Experience
Bugs fixed in some tex components, additional tex components/libraries/tools available.
Dependencies
As previously stated, lots of packages have texlive (or "tex(foo)") BuildRequires, but it is very unlikely that any other changes would block this one.
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) Roll back to texlive-2014 packages. spot or rel-eng can do this.
- Contingency deadline: Beta freeze
- Blocks release? No
- Blocks product? No
Documentation
https://www.tug.org/texlive/doc/texlive-en/texlive-en.html#news