How can I test 0.4 release branch updates?

[Erik Schnetter]

I'd like to help testing the 0.4.x releases as they are prepared. For this, I'm following the 0.4 branch in the git repo closely. I expected that the commits that make up 0.4.1 would be present there for some time before the actual release. Alas, that doesn't seem to be the case -- tonight, 99 commits were pushed, immediately followed by a release. Where can I test the upcoming 0.4.x releases as they are prepared?

-erik

--

Erik Schnetter <schn...@gmail.com> http://www.perimeterinstitute.ca/personal/eschnetter/

[Yichao Yu]

On Mon, Nov 9, 2015 at 8:22 AM, Erik Schnetter <schn...@gmail.com> wrote:
> I'd like to help testing the 0.4.x releases as they are prepared. For this,
> I'm following the 0.4 branch in the git repo closely. I expected that the
> commits that make up 0.4.1 would be present there for some time before the
> actual release. Alas, that doesn't seem to be the case -- tonight, 99
> commits were pushed, immediately followed by a release. Where can I test the
> upcoming 0.4.x releases as they are prepared?

It should be quite obvious if you just check those commits....

https://github.com/JuliaLang/julia/pull/13834

[Tony Kelman]

I've generally been rolling backports up into a branch and opening PR's against the release branch both to save some load on CI, and to have a central place to post testing results and discuss what should make it into the patch releases. Also helps on the off-chance I identify a regression while running PackageEvaluator with binaries built from the prospective backport branch and need to rebase or revert anything.