m (→Owner) |
|||
| Line 34: | 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> | ||
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