Hello all,

Well, despite my noted attempts to make "minor upgrade script changes to
account for the 3.0.6 upgrade script", one of those changes did not make it
into the release tarball, causing the upgrade script to fail and rollback
when run.  (Thank you to Václav Jansa for finding and pointing out this
issue.)  A revised tarball (denoted with 'a') is now available on the
downloads page.  If you just want to download the updated upgrade script,
you can grab it from here:


I apologize for any inconvenience.


On Fri, Mar 30, 2018 at 9:27 AM, Daniel Wells <dbwe...@gmail.com> wrote:

> Hello all,
> After several positive reports from testers, and following shortly after
> the security releases on Wednesday, the 3.1 release candidate has been
> rolled over to become the official 3.1.0 release.  As expected, the only
> changes from RC to 3.1.0 were the template security patches and minor
> upgrade script changes to account for the 3.0.6 upgrade script.
> As I've mentioned in past emails, my hope and goal is to carry over the
> momentum from this release into the 3.1 maintenance phase.  With this in
> mind, here is a list of bugs currently targeted at 3.1.1:
> https://launchpad.net/evergreen/+milestone/3.1.1
> Unfortunately, this list is currently not representative of the challenges
> before us.  Our tracking system prioritizes testing coordination, and this
> makes some sense, as it is the phase of development where our community
> standards require involvement from multiple individuals (via the multiple
> sign-off requirement).  We should, however, also consider how we might
> increase awareness of important bugs earlier in the development process.  I
> will be sending a separate email with a modest proposal along these lines.
> Once again, thank you to everyone who participated in getting 3.1.0 out
> the door.  I look forward to continuing to work together to ensure that
> Evergreen meets the needs of everyone involved.
> Sincerely,
> Dan

Reply via email to