Updates for 2.3.0 beta #399
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
speth
force-pushed
the
release-prep
branch
2 times, most recently
from
ad8449c
to
f4d5235
Compare
Cantera 2.3 Changelog (full)Bugs FixedThermo / Species / Elements
Kinetics
Transport
Reactor networks
1D flames
Python package
Matlab toolbox
Examples / Samples
Other
Changes to existing capabilitiesThermo / Species / Elements
Kinetics
TransportReactor networks
1D flames
Python package
Matlab toolbox
Other
New FeaturesThermo / Species / Elements
Kinetics
TransportReactor networks
1D flames
Input file handling (ck2cti, cti, ctml_writer)
Python package
Matlab toolbox
Examples / Samples
Other
Other code improvementsThermo / Species / Elements
Kinetics
Equilibrium solvers
Reactor networks
1D flames
Input file handling (ck2cti, cti, ctml_writer)Python package
Matlab toolbox
Examples / Samples
Test suite
Build system improvements
Other
|
|
I tried to make an abbreviated version, and even this ended up being long. Maybe we need to make releases more frequently. Feel free to edit this to make it shorter. I'm just going to use this comment to draft the announcement for 2.3.0, since it lets me keep all the nice automagic links to Github issues and commits if I do it this way. Dear all, I am pleased to announce the release of Cantera 2.3.0. There have been many changes and improvements since Cantera 2.2.0 was released in June 2015. A somewhat abbreviated Changelog is included below, in addition to note on installing Cantera 2.3.0 using a variety of methods. Regards, Installing Cantera 2.3.0Cantera 2.3.0 introduces a new installation option for the Python package, which is the For more details on installing conda and using Cantera with conda, see http://cantera.github.io/docs/sphinx/html/install.html#conda. The source code and Windows binaries can be downloaded from Github: https://github.com/Cantera/cantera/releases. To use the Matlab toolbox on Windows, install both For Ubuntu users, Cantera 2.3.0 packages for both 16.04 (Xenial Xerus) and 16.10 (Yakkety Yak) are available via the PPA at https://launchpad.net/~speth/+archive/ubuntu/cantera. See http://cantera.github.io/docs/sphinx/html/install.html#ubuntu for additional details. For macOS users, Cantera 2.3.0 will be available pending resolution of Homebrew/homebrew-science#4860. See http://cantera.github.io/docs/sphinx/html/install.html#homebrew for additonal instructions. And of course, you can also just check out the source code directly using Git from https://github.com/Cantera/cantera. Compilation instructions for all platforms are located at: http://cantera.github.io/docs/sphinx/html/compiling.html. DocumentationDocumentation for Cantera 2.3 can be found at: http://cantera.github.io/docs/sphinx/html/index.html. Issues & FeedbackPlease report any issues on the Github issue tracker at https://github.com/Cantera/cantera/issues. When making a bug report, please specify the exact version of Cantera you are using (i.e. There are number of rarely used or redundant features which have been slated for deprecation. Using these methods in Cantera 2.3 will show a deprecation warning, and these methods will be removed before the following release of Cantera. You can examine the list of deprecated functions at: http://cantera.github.io/docs/doxygen/html/deprecated.html. If you believe any of these deprecations are unwarranted, please create an issue on Github. In addition, there are a number of classes and features that have been identified as being potentially unused. They are not used internally within Cantera, have no test coverage, and have no examples available. These classes are identified in Issue #267. If you utilize any of these classes, please consider providing tests or examples which can be integrated into Cantera. If these classes and features remain in their current state, they are likely to be deprecated and removed in a future release. Changes in Cantera 2.3.0Highlights are listed here. See the full changelog for more.
|
|
First-cut Windows binaries are at: http://gir.mit.edu:8010/nightlies/. I've only had a chance to test a couple of them, but I think they're good enough to make the beta announcement. @bryanwweber Unless you have any further comments, I'm ready to merge this and then we can trigger the conda builds. |
|
I'm 👍 on the merge and release. I'd suggest we do more frequent bugfix patch releases so the Changelog doesn't get quite so long between releases. Once you merge, I'll take a look at what we should do for the conda recipes. I think we need a new recipe/branch for 2.3.0 that uploads to the main label (but that should wait for the final release). |
|
Right, I think the conda builds for the beta should still be on the master branch and use the Should we reset the |
|
OK creating the branch structure should work because the CI builds on all the branches, not just master. For that, I think it would be better to have the source tarball downloaded from the official release page, so the conda package always matches an actual release, and not a random commit on the 2.3.0 branch. I think we should check that |
|
Yes, it should download either the tarball or specify the commit that's
tagged as the 2.3.0 release.
2.3.0b1 had better be read as newer than 2.3.0a3. In any case, it's
probably worth cleaning out all of the random alpha builds once we add the
beta.
…On Wed, Nov 30, 2016, 8:19 AM Bryan W. Weber ***@***.***> wrote:
OK creating the branch structure should work because the CI builds on all
the branches, not just master. For that, I think it would be better to have
the source tarball downloaded from the official release page, so the conda
package always matches an actual release, and not a random commit on the
2.3.0 branch.
I think we should check that 2.3.0b1 is read as a newer version than
2.3.0a3, and if it is, reset the build number. Alternatively, we can
delete the existing files from anaconda.org and reset the build number.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#399 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAnXcUZigigN5sb5rE_yEFnpAGeOC9FQks5rDXftgaJpZM4K89nt>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is for updates that should coincide with the start of the 2.3.0 beta period. Feel free to push additional updates to this branch, or let me know if there's anything missing.