Changes between Version 1 and Version 2 of 1.3/TracChangeLog

Timestamp:

Nov 11, 2016, 7:57:22 PM (7 years ago)

Author:

Christian Boos

Comment:

lay out plans for early 1.3.x releases

1.3/TracChangeLog

@@ -7 +7 @@
 == 1.3.x Releases
 
-//Forthcoming//.
+This series of releases correspond to the development branch ([source:trunk], in preparation for the future 1.4 stable releases.
+
+// ** No guarantees of feature and API compatibility is made from one 1.1.x release to the next. //
+
+For more information see the [trac:wiki:TracDev/ApiChanges/1.3 API changes] and the detailed
+release notes for [[trac:wiki:TracDev/ReleaseNotes/1.3#DevelopmentReleases | 1.3]].
+
+=== 1.3.3 
+
+//(???, 2016)//
+
+Trac 1.3.3 will be the first release to feature [[Python3]] compatibility.
+
+=== 1.3.2 
+
+//(November 30, 2016)//
+
+Trac 1.3.2 will be the first release to feature [[Jinja2]] as the new template engine.
+
+
+=== 1.3.1
+
+//(November 12, 2016)//
+
+Trac 1.3.1 is the last release before the switch of the development branch to [[Jinja2]].
+
+It is in sync with the version 1.2, and as such contains all its fixes and enhancements as well.
+
+Highlights of the changes since 1.2:
+
+* Modernized the code to support Python 2.7 idioms (earlier versions are no longer supported)
+  (#12046, #12148, #12558, #12569)
+* Removed lots of backward compatibility APIs from pre-1.0 days; 
+  in particular, the database API is now exclusively based on the [[TracDev/ApiChanges/1.1#DatabaseAPIChanges|context managers]] (#9612, #11901)
+* Ticket changes can be used to format the subject template (#12205)
+
+[trac:source:/tags/trac-1.3.1rc1 View Tag] | [trac:milestone:1.3.1 View Milestone]
+
 
 == 1.2.x Releases