Bump version to 3.0.11

6 files changed, 50 insertions, 47 deletions

diff --git a/ANNOUNCE b/ANNOUNCE
index 5fec2f40e..53c5bbc59 100644
--- a/ANNOUNCE
+++ b/ANNOUNCE
@@ -1,8 +1,8 @@
-*** ANNOUNCE: SWIG 3.0.10 (12 Jun 2016) ***
+*** ANNOUNCE: SWIG 3.0.11 (in progress) ***
 
 http://www.swig.org
 
-We're pleased to announce SWIG-3.0.10, the latest SWIG release.
+We're pleased to announce SWIG-3.0.11, the latest SWIG release.
 
 What is SWIG?
 =============
@@ -27,11 +27,11 @@ Availability
 ============
 The release is available for download on Sourceforge at
 
-     http://prdownloads.sourceforge.net/swig/swig-3.0.10.tar.gz
+     http://prdownloads.sourceforge.net/swig/swig-3.0.11.tar.gz
 
 A Windows version is also available at
 
-     http://prdownloads.sourceforge.net/swig/swigwin-3.0.10.zip
+     http://prdownloads.sourceforge.net/swig/swigwin-3.0.11.zip
 
 Please report problems with this release to the swig-devel mailing list,
 details at http://www.swig.org/mail.html.
diff --git a/CHANGES b/CHANGES
index d6e1d291c..0146ac7ac 100644
--- a/CHANGES
+++ b/CHANGES
@@ -3,6 +3,48 @@ SWIG (Simplified Wrapper and Interface Generator)
 See the CHANGES.current file for changes in the current version.
 See the RELEASENOTES file for a summary of changes in each release.
 
+Version 3.0.10 (12 Jun 2016)
+============================
+
+2016-06-06: mromberg
+            [Python] Patch #698. Add support for -relativeimport for python 2.7, so -py3 is no
+            longer also required for relative import support.
+
+2016-06-05: mromberg
+            [Python] Patch #694 - Fix package import regressions introduced in swig-3.0.9.
+
+            1) The code in 3.0.9 did not fall back to 'import _foo' if 'import bar._foo' failed
+            (assuming bar.foo was the main module). Every place _foo is imported now first tries
+            it from the package where foo was found and if that fails tries _foo as a global module.
+
+            2) The separate block of Python code that injected code to pull in the attributes
+            from _foo when -builtin is used made use of the -py3 switch to either do
+            'from ._foo import *' or "from _foo import *". This block of code no longer does this
+            and instead checks the Python version at runtime to switch between the two syntaxes.
+
+            In summary, swig-3.0.10 has been modified to ease the creation of wrapper modules
+            that can be fully made part of a Python package.  SWIG no longer
+            assumes the dynamically linked C module is a global module.
+            The dynamic module can now be placed into either the same package as the pure Python
+            module or as a global module.  Both locations are used by the Python wrapper to
+            locate the C module.
+
+            However, this could cause a backwards incompatibility with some code
+            that was relying on the ability of "from package import _module" to
+            pull attributes out of the package directly.  If your code populates a
+            module (which is also a package) with attributes that are SWIG
+            generated modules which were not loaded in a conventional way,
+            swig-3.0.8 and earlier may have worked due to 'from package import
+            _module' bypassing a real import and pulling your module in as an
+            attribute. This will no longer work.  Since this is not a common (or
+            even recommended) practice, most folk should not be affected.
+
+            *** POTENTIAL INCOMPATIBILITY ***
+
+2016-05-31: wsfulton
+            Fix #690 - Smart pointer to %ignored class doesn't expose inherited methods.
+            Regression introduced in swig-3.0.9.
+
 Version 3.0.9 (29 May 2016)
 ===========================
 
diff --git a/CHANGES.current b/CHANGES.current
index b5b4567e2..312343f56 100644
--- a/CHANGES.current
+++ b/CHANGES.current
@@ -2,44 +2,5 @@ Below are the changes for the current release.
 See the CHANGES file for changes in older releases.
 See the RELEASENOTES file for a summary of changes in each release.
 
-Version 3.0.10 (12 Jun 2016)
+Version 3.0.11 (in progress)
 ============================
-
-2016-06-06: mromberg
-            [Python] Patch #698. Add support for -relativeimport for python 2.7, so -py3 is no
-            longer also required for relative import support.
-
-2016-06-05: mromberg
-            [Python] Patch #694 - Fix package import regressions introduced in swig-3.0.9.
-
-            1) The code in 3.0.9 did not fall back to 'import _foo' if 'import bar._foo' failed
-            (assuming bar.foo was the main module). Every place _foo is imported now first tries
-            it from the package where foo was found and if that fails tries _foo as a global module.
-
-            2) The separate block of Python code that injected code to pull in the attributes
-            from _foo when -builtin is used made use of the -py3 switch to either do
-            'from ._foo import *' or "from _foo import *". This block of code no longer does this
-            and instead checks the Python version at runtime to switch between the two syntaxes.
-
-            In summary, swig-3.0.10 has been modified to ease the creation of wrapper modules
-            that can be fully made part of a Python package.  SWIG no longer
-            assumes the dynamically linked C module is a global module.
-            The dynamic module can now be placed into either the same package as the pure Python
-            module or as a global module.  Both locations are used by the Python wrapper to
-            locate the C module.
-
-            However, this could cause a backwards incompatibility with some code
-            that was relying on the ability of "from package import _module" to
-            pull attributes out of the package directly.  If your code populates a
-            module (which is also a package) with attributes that are SWIG
-            generated modules which were not loaded in a conventional way,
-            swig-3.0.8 and earlier may have worked due to 'from package import
-            _module' bypassing a real import and pulling your module in as an
-            attribute. This will no longer work.  Since this is not a common (or
-            even recommended) practice, most folk should not be affected.
-
-            *** POTENTIAL INCOMPATIBILITY ***
-
-2016-05-31: wsfulton
-            Fix #690 - Smart pointer to %ignored class doesn't expose inherited methods.
-            Regression introduced in swig-3.0.9.
diff --git a/Doc/Manual/Sections.html b/Doc/Manual/Sections.html
index 0adc60642..8417bec15 100644
--- a/Doc/Manual/Sections.html
+++ b/Doc/Manual/Sections.html
@@ -8,7 +8,7 @@
 <H1><a name="Sections">SWIG-3.0 Documentation</a></H1>
 
 <p>
-Last update : SWIG-3.0.10 (12 Jun 2016)
+Last update : SWIG-3.0.11 (in progress)
 </p>
 
 <H2><a name="Sections_Sections">Sections</a></H2>
diff --git a/README b/README
index 8d1a5a231..3421b72bf 100644
--- a/README
+++ b/README
@@ -1,6 +1,6 @@
 SWIG (Simplified Wrapper and Interface Generator)
 
-Version: 3.0.10 (12 Jun 2016)
+Version: 3.0.11 (in progress)
 
 Tagline: SWIG is a compiler that integrates C and C++ with languages
          including Perl, Python, Tcl, Ruby, PHP, Java, C#, D, Go, Lua,
diff --git a/configure.ac b/configure.ac
index a29443005..492d9cc1c 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2,7 +2,7 @@ dnl Process this file with autoconf to produce a configure script.
 dnl The macros which aren't shipped with the autotools are stored in the
 dnl Tools/config directory in .m4 files.
 
-AC_INIT([swig],[3.0.10],[http://www.swig.org])
+AC_INIT([swig],[3.0.11],[http://www.swig.org])
 
 dnl NB: When this requirement is increased to 2.60 or later, AC_PROG_SED
 dnl     definition below can be removed