Hi,
Sorry about the re-post. I should have send this the first time with a better Subject and in it's own thread:
Hi
On Tue, Jun 14, 2016 at 08:06:23AM +0200, Frank Loeffler wrote:
I plan to create release branches in about 8 hours (or so).
The release branches have been created, and you can use the following URL to get a checkout of it (remember, GetComponents also takes URLs):
https://bitbucket.org/einsteintoolkit/manifest/raw/ET_2016_05/einsteintoolki...
This does NOT mean the release it out of the door yet.
If we don't see any errors, this will be what will be released, hopefully soon. The more errors we can detect now the better. Critical things would still be fixed, non-critical can be mentioned in the release notes. In order for any of this to happen, we need
- YOU *
to test the to-be release.
Frank
On Tue, Jun 14, 2016 at 8:02 AM, Frank Loeffler knarf@cct.lsu.edu wrote:
The release branches have been created, and you can use the following URL to get a checkout of it (remember, GetComponents also takes URLs):
https://bitbucket.org/einsteintoolkit/manifest/raw/ET_2016_05/einsteintoolki...
Is the release still going to be called ET_2016_05, even though it will be released in June?
On Tue, Jun 14, 2016 at 8:58 AM, Frank Loeffler knarf@cct.lsu.edu wrote:
On Tue, Jun 14, 2016 at 08:50:20AM -0400, Barry Wardell wrote:
Is the release still going to be called ET_2016_05, even though it will
be
released in June?
Yes.
Thanks. I have created the ET_2016_05 release branch of the git super-repository that is used by Jenkins. The EinsteinToolkitReleased < https://build.barrywardell.net/job/EinsteinToolkitReleased/%3E job on Jenkins now tracks the ET_2016_05 release branch and all tests currently pass.
users@lists.einsteintoolkit.org
-
Barry Wardell -
Frank Loeffler