Preparation for Enzo 2.5 release - missing anything?

[Brian O'Shea]

Hi folks,

Now that all of the targeted PRs are accepted I spent a bit of time getting ready for the Enzo 2.5 public release, and I want to make sure that I haven't missed anything.  Please take a look through this list, and let me know if I've missed anything.

Done:

+ CHANGELOG, README, and version numbers updated: https://bitbucket.org/enzo/enzo-dev/pull-requests/324/updates-in-preparation-for-v25-release/diff

+ Public release email drafted - attached at the end of this email (to be sent to enzo-dev and enzo-users)

To do:

+ Create Enzo 2.5 docs for readthedocs.org and enzo-project.org (WHO IS IN CHARGE OF THIS?  Britton?)

+ Merge stable branch with week-of-code and run test suite [Brian]

+ Add enzo-2.5 tag to last stable branch changeset [Brian]

+ move @ bookmark if necessary [Brian]

+ send out public release email [?]

Does this look right, or am I missing anything?  (Note: I'm going off of https://enzo.readthedocs.org/en/latest/developer_guide/DoingARelease.html, so if I am missing something we probably want to update these docs as well!)

--Brian

----------------------------

Subject:  ANN: Enzo 2.5 public release

Email body:  

We are pleased to announce the release of Version 2.5 of the Enzo

code. This is a periodic release that includes all changes committed

to the Enzo BitBucket repository since August 2014. This release

contains some new features and a number of enhancements and bugfixes.

New features include: support for Version 2.0 of the Grackle chemistry

and cooling library; refinement by Must Refine particles and metal

mass; cosmic ray pressure, diffusiong and injection for the ZEUS

solver; Kinetic stellar feedback; power-of-two memory allocation to

decrease fragmentation; and many new problem types.

There have been a number of enhancements to the hydro, MHD, radiation

transport, and star particle routines, and a variety of performance

enhancements to the same set of packages.

There have also been a number of significant bugfixes, including

several that may increase the stability and efficiency of production

multi-physics simulations.

We urge all users to update to the latest version if they are using

Enzo 2.4 or earlier. While one can obtain the release by downloading a

tar file, we strong encourage all users to use enzo from a clone of

the mercurial repository, which will facilitate reproducible work with

the code.

For more information about enzo, see http://enzo-project.org.

For the release notes and changelog, see

http://enzo-project.org/ReleaseNotes.html and the CHANGELOG file in

the root directory of the enzo-dev repository.

On behalf of the Enzo collaboration,

Brian O'Shea

[Cameron Hummels]

"diffusiong and injection for the ZEUS"

Typo, and maybe restructure to be: "a cosmic ray fluid including pressure, diffusion and injection;"

--
You received this message because you are subscribed to the Google Groups "enzo-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enzo-dev+u...@googlegroups.com.
To post to this group, send email to enzo...@googlegroups.com.
Visit this group at https://groups.google.com/group/enzo-dev.
For more options, visit https://groups.google.com/d/optout.

--

Cameron Hummels

NSF Postdoctoral Fellow

Department of Astronomy

California Institute of Technology

http://chummels.org

[Brian O'Shea]

Nice catch, thanks!  Fixed in the draft email.

[John Wise]

Hi Brian,

This all looks good to me. Thanks for taking charge of this point
release.

John

On Sun, 06 Mar 2016 at 13:35 -0500, Brian O'Shea wrote:
> Hi folks,
> Now that all of the targeted PRs are accepted I spent a bit of time
> getting ready for the Enzo 2.5 public release, and I want to make sure
> that I haven't missed anything.  Please take a look through this list, and
> let me know if I've missed anything.
> Done:
> + CHANGELOG, README, and version numbers updated:

> [1]https://bitbucket.org/enzo/enzo-dev/pull-requests/324/updates-in-preparation-for-v25-release/diff

> + Public release email drafted - attached at the end of this email (to be
> sent to enzo-dev and enzo-users)
> To do:

> + Create Enzo 2.5 docs for [2]readthedocs.org and [3]enzo-project.org (WHO

> IS IN CHARGE OF THIS?  Britton?)
> + Merge stable branch with week-of-code and run test suite [Brian]
> + Add enzo-2.5 tag to last stable branch changeset [Brian]
> + move @ bookmark if necessary [Brian]
> + send out public release email [?]
> Does this look right, or am I missing anything?  (Note: I'm going off

> of [4]https://enzo.readthedocs.org/en/latest/developer_guide/DoingARelease.html,

> For more information about enzo, see [5]http://enzo-project.org.

> For the release notes and changelog, see

> [6]http://enzo-project.org/ReleaseNotes.html and the CHANGELOG file in

> the root directory of the enzo-dev repository.
> On behalf of the Enzo collaboration,
> Brian O'Shea
>

> --
> You received this message because you are subscribed to the Google Groups
> "enzo-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to [7]enzo-dev+u...@googlegroups.com.
> To post to this group, send email to [8]enzo...@googlegroups.com.
> Visit this group at [9]https://groups.google.com/group/enzo-dev.
> For more options, visit [10]https://groups.google.com/d/optout.
>
> References
>
> Visible links
> 1. https://bitbucket.org/enzo/enzo-dev/pull-requests/324/updates-in-preparation-for-v25-release/diff
> 2. http://readthedocs.org/
> 3. http://enzo-project.org/
> 4. https://enzo.readthedocs.org/en/latest/developer_guide/DoingARelease.html
> 5. http://enzo-project.org/
> 6. http://enzo-project.org/ReleaseNotes.html
> 7. mailto:enzo-dev+u...@googlegroups.com
> 8. mailto:enzo...@googlegroups.com
> 9. https://groups.google.com/group/enzo-dev
> 10. https://groups.google.com/d/optout

--
John Wise
Assistant Professor of Physics
Center for Relativistic Astrophysics, Georgia Tech
http://cosmo.gatech.edu