Finalizing the Pyomo 6.3.0 release

djlaky · Feb 23, 2022 · c461f53 · c461f53
1 parent 946b9bd
commit c461f53
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 9 deletions.
diff --git a/.coin-or/projDesc.xml b/.coin-or/projDesc.xml
@@ -227,8 +227,8 @@ Carl D. Laird, Chair, Pyomo Management Committee, claird at andrew dot cmu dot e
 			     Use explicit overrides to disable use of automated
 			     version reporting.
 			-->
-			<stableVersionNumber>6.2</stableVersionNumber>
-			<releaseNumber>6.2</releaseNumber>
+			<stableVersionNumber>6.3.0</stableVersionNumber>
+			<releaseNumber>6.3.0</releaseNumber>
 
 		</developmentStatus>
 

diff --git a/RELEASE.txt b/RELEASE.txt
@@ -1,20 +1,21 @@
-We are pleased to announce the release of Pyomo 6.2.
+We are pleased to announce the release of Pyomo 6.3.0.
 
 Pyomo is a collection of Python software packages that supports a
 diverse set of optimization capabilities for formulating and analyzing
 optimization models.
 
-
 The following are highlights of the 6.0 release series:
 
  - Improved stability and robustness of core Pyomo code and solver interfaces
  - Integration of Boolean variables into GDP
  - Integration of NumPy support into the Pyomo expression system
+ - Added support for Python 3.10
  - New packages:
     - APPSI (Auto-Persistent Pyomo Solver Interfaces)
     - External grey box models
     - PyROS (Pyomo Robust Optimization Solver)
     - Structural model analysis
+    - Rewrite of the TrustRegion Solver
 
 A full list of updates and changes is available in the CHANGELOG.txt
 

diff --git a/pyomo/core/base/alias.py b/pyomo/core/base/alias.py
@@ -51,7 +51,7 @@
 
 @deprecated("The Alias component was never completed/tested and will "
             "be removed.  Consider using Reference()",
-            version='6.3', remove_in='6.3.1')
+            version='6.3.0', remove_in='6.3.1')
 class Alias(Component):
 
     __slots__ = ('_aliased_object')

diff --git a/pyomo/version/info.py b/pyomo/version/info.py
@@ -24,10 +24,10 @@
 # should generally be left at 0, unless a downstream package is tracking
 # main and needs a hard reference to "suitably new" development.
 major=6
-minor=2
-micro=1
-releaselevel='invalid'
-#releaselevel='final'
+minor=3
+micro=0
+#releaselevel='invalid'
+releaselevel='final'
 serial=0
 
 if releaselevel == 'final':