search

JuliaLang / julia

The Julia Programming Language
https://julialang.org/
MIT License
45.75k stars 5.49k forks source link

Release Candidate plans for 0.2 #3827

Closed staticfloat closed 11 years ago

staticfloat commented 11 years ago

Where better to discuss RC policy that on an issue tracker?

After seeing https://github.com/JuliaLang/julia/issues/2597#issuecomment-21534868 and almost replying to @ViralBShah right there in the issue, I thought it might be useful to hash out how we plan to do RC's and the eventual release of 0.2. All my experience with RC's has been with the blender project, which has a pretty intense set of policies regarding when certain pieces of code can get merged into trunk, but I think we can adapt some of their practices to help our releases to go as smoothly as possible.

I'm thinking that we should tag some commit as 0.2.0-rc1, and then push that out to the community at large to see if they can break it. The key here is as widespread testing as possible, followed by bugfixes only making their way into master, everything else happens in a topic branch. Once a predetermined amount of time goes by (for the blender heads it's on the order of a week, I believe) where no new issues come up and we're able to squash all the showstoppers, a release is made. There are usually a few bugs that are found afterward, but unless they're something really terrible a bugfix build is usually not released.

The most important thing here is getting the community to test the RC builds on all their very inventive setups, which means probably announcing things like this on julia-dev, julia-users, etc.... The bugfix week (or however long it is) is also a really good time to focus in on documentation, but let's be honest, when is a time when we WOULDN'T say it's a good time to focus in on the docs?

Discuss!

ihnorton commented 11 years ago

Windows binaries are up

staticfloat commented 11 years ago

I have taken the liberty of adding on a commit to master that gets the binary to self-identify as a release candidate: 040f3ab6b7acc9507e8cc11b36e53df648e1b8d1. I'm building OSX binaries now, off of that SHA.

WestleyArgentum commented 11 years ago

First off, huzza!

But I'm curious, why do we need separate builds for osx 10.6 and 10.7?

staticfloat commented 11 years ago

It has to do with Keno's work on the profiler over the summer. See issue

4515 for instance.

First off, huzza!

But I'm curious, why do we need separate builds for osx 10.6 and 10.7?

— Reply to this email directly or view it on GitHubhttps://github.com/JuliaLang/julia/issues/3827#issuecomment-26373106 .

WestleyArgentum commented 11 years ago

Ah, kk, thanks