I think that the only thing we're waiting on is my hashing branch<https://github.com/JuliaLang/julia/pull/6624>. I've been working on bringing comparisons (isequal, isless) into line with the new hashing behavior that it introduced. It's pretty tedious work, but I've made a fair amount of progress. If that's really the only thing we're waiting on, we could have an RC by this weekend.
On Tue, Apr 29, 2014 at 1:12 PM, Ryan Gardner <[email protected]> wrote: > Any rough estimate on what "soon" is? > > ...not trying to push, of course. We're trying to lock in on a version of > Julia and if soon is like 2 days, this may affect what we decide to do. > > > On Monday, April 28, 2014 2:33:26 PM UTC-4, Isaiah wrote: > >> There is no official schedule yet. It has been about six months since 0.2 >> was released, and we are very close to 0.3 now... My rough guess for 0.4 >> would be August-ish, bumping to LLVM3.5, but that's really just a guess. >> >> >> >> >> On Mon, Apr 28, 2014 at 10:31 AM, Ryan Gardner <[email protected]> wrote: >> >>> Similarly, is there any schedule for the releases (either one with rough >>> objectives or a harder one)? >>> >>> >>> On Monday, April 28, 2014 9:48:18 AM UTC-4, Ryan Gardner wrote: >>>> >>>> Can anyone point me to something that describes or briefly describe the >>>> process for determining/ensuring that a release is stable. A few sentences >>>> is fine. >>>> >>>> Is there essentially a large set of test cases that are run on the code >>>> before the release it made, while those test cases aren't run on the >>>> nightly builds? How are those test cases chosen/written/obtained? How are >>>> unresolved issues determined to be acceptable, or is there an effort to >>>> resolve all bug-related issues? Thanks. >>>> >>> >>
