From Fedora Project Wiki

(RPM 4.12)
Line 35: Line 35:
  
 
See the [http://rpm.org/wiki/Releases/4.12.0 RPM 4.12 Release Notes] for a full list of changes.
 
See the [http://rpm.org/wiki/Releases/4.12.0 RPM 4.12 Release Notes] for a full list of changes.
 +
 +
== TCL/TK ==
 +
 +
In Fedora 21, '''TCL/TK''' has been upgraded to version 8.6.1, which includes numerous bug fixes and enhancements. Some of the notable features include:
 +
 +
'''TCL 8.6'''
 +
 +
* Support for IPv6 networking for both client and server sockets
 +
 +
* Support for SQL Database - The bundled tdbc package which contains the Tcl DataBase Connectivity interface now enables writing SQL database-powered scripts decoupled from any particular database engine. The bundled sqlite3 and tdbc::sqlite3 packages supply a powerful and popular SQL database engine ready to use.
 +
 +
* Support for Object Oriented Programming - The commands of the TclOO package are now part of the TCL language itself. This gives TCL a built-in fully dynamic, class-based object system and also includes advanced features such as meta-classes, filters, and mixins. A new version 4 of the popular package Itcl (also known as "incr TCL") is also included, now built on a TclOO foundation, granting support for some traditional Object Oriented TCL programming out of the box as well.
 +
'''
 +
'''TK 8.6'''
 +
 +
* PNG Image Support - Photo images now support read/write in the PNG format, with the ability to set the alpha channel.
 +
 +
For the full list of changes, see the [http://www.tcl.tk/software/tcltk/8.6.html TCL/TK Release Notes].
 +
  
 
{{admon/important|Important|Using some of the new features will break forward compatibility. Packages using these features will not be able be built or be installed on older Fedora versions. Backward compatibility is expected to be maintained.}}
 
{{admon/important|Important|Using some of the new features will break forward compatibility. Packages using these features will not be able be built or be installed on older Fedora versions. Backward compatibility is expected to be maintained.}}

Revision as of 22:29, 18 August 2014

DocsProject Header docTeam1.png
Note.png
Beat is open
This beat is now ready to have Fedora 25 content added by the beat writer


Python 3.4

https://fedoraproject.org/wiki/Changes/Python_3.4

Ruby 2.1

Ruby 2.1 is the latest stable version of Ruby, and brings major increases in speed, memory efficiency, and reliability.

The update brings a soname bump. Therefore, Ruby packages which use binary extensions should be rebuilt. Nevertheless, since upstream payed great attention to source compatibility, no changes to your code should be needed. Additionally, RubyGems with binary extensions need to be updated to conform to the recent package guidelines to ensure compatibility with the new RubyGems release.

Also note that starting with this release, Ruby is adopting semantic versioning.

You can find a full list of changes in Ruby 2.1 in the changelog. Full documentation is available at the Ruby documentation page.

Review Board 2.0

Fedora now provides Review Board 2.0, a powerful, web-based patch review and management tool.

Version 2.0 adds the ability to post committed changes from a branch directly from the web UI, adds review of text file attachments, greatly extends the capabilities of the public API and extension framework, and offers significant performance improvements, usability enhancements, and visual cleanups.

Significant enhancements have been made to the diff viewer, as well as adding support for reviews on non-code files (such as binary file formats).

Documentation for Review Board 2.0 is available at the Review Board Manual website.

Important.png
Important
Upgrading to Review Board 2.0 from a previous release will modify your database schema. The migration will be performed when you restart Apache for the first time after the upgrade, and the process is irreversible. Back up your database before upgrading.

RPM 4.12

The RPM package manager has been updated to version 4.12, which brings Fedora in line with the latest upstream version.

This update brings a number of improvements, including:

  • Ability to package files larger than 4 GB.
  • Support for weak dependencies. (Note that this does not automatically mean Fedora packages and other tools support this feature.)
  • API users will be able to access file data more cleanly.
  • Payload data is now accessible over the API.
  • A new tool, rpm2archive, will allow converting rpm packages to tar files instead of the outdated cpio format. The new tool will work with files larger than 4 GB, while cpio (and rpm2cpio) does not.

See the RPM 4.12 Release Notes for a full list of changes.

TCL/TK

In Fedora 21, TCL/TK has been upgraded to version 8.6.1, which includes numerous bug fixes and enhancements. Some of the notable features include:

TCL 8.6

  • Support for IPv6 networking for both client and server sockets
  • Support for SQL Database - The bundled tdbc package which contains the Tcl DataBase Connectivity interface now enables writing SQL database-powered scripts decoupled from any particular database engine. The bundled sqlite3 and tdbc::sqlite3 packages supply a powerful and popular SQL database engine ready to use.
  • Support for Object Oriented Programming - The commands of the TclOO package are now part of the TCL language itself. This gives TCL a built-in fully dynamic, class-based object system and also includes advanced features such as meta-classes, filters, and mixins. A new version 4 of the popular package Itcl (also known as "incr TCL") is also included, now built on a TclOO foundation, granting support for some traditional Object Oriented TCL programming out of the box as well.

TK 8.6

  • PNG Image Support - Photo images now support read/write in the PNG format, with the ability to set the alpha channel.

For the full list of changes, see the TCL/TK Release Notes.


Important.png
Important
Using some of the new features will break forward compatibility. Packages using these features will not be able be built or be installed on older Fedora versions. Backward compatibility is expected to be maintained.