From 303eb0702fe24a9d2c5d8aa4024cd62abe513dda Mon Sep 17 00:00:00 2001 From: Gary Oberbrunner Date: Sat, 2 Mar 2013 14:17:25 -0500 Subject: Final auto updates for 2.3.0 release. --- ReleaseConfig | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'ReleaseConfig') diff --git a/ReleaseConfig b/ReleaseConfig index c7943a1c..b64ebc04 100644 --- a/ReleaseConfig +++ b/ReleaseConfig @@ -24,21 +24,22 @@ __revision__ = "__FILE__ __REVISION__ __DATE__ __DEVELOPER__" # # After updating this file, run bin/update-release-info.py . -# +# # The version tuple that will be used for the release. The fields are # (major, minor, micro, type, patchlevel). The release level is one of # 'alpha', 'beta', 'candidate', or 'final'. If the release type is not # 'final', the patchlevel is set to the release date. This value is -# manatory and must be present in this file. -version_tuple = (2, 2, 0, 'final', 0) +# mandatory and must be present in this file. +#version_tuple = (2, 2, 0, 'final', 0) +version_tuple = (2, 3, 0) # Python versions prior to unsupported_python_version cause a fatal error # when that version is used. Python versions prior to deprecate_python_version # cause a warning to be issued (assuming it's not disabled). These values are # mandatory and must be present in the configuration file. unsupported_python_version = (2, 3, 0) -deprecated_python_version = (2, 4, 0) +deprecated_python_version = (2, 7, 0) # If release_date is (yyyy, mm, dd, hh, mm, ss), that is used as the release # date and time. If release_date is (yyyy, mm, dd), it is used for the -- cgit v1.2.1