Hans, a great way to keep up with what's going on with the development of 0.4 is to visit the GitHub page https://github.com/JuliaLang/julia and click the "Watch" button. But be prepared for a lot of emails.
--Tim On Friday, September 26, 2014 06:26:36 AM Ivar Nesje wrote: > Hans: I think the reason you did not get an answer is that your question is > more a request than a question. NEWS.md is a great resource we try to keep > updated when we make significant changes to Julia. Unfortunately it's easy > to forget to update it, so it is often forgotten. I'm not sure we should > add dates, because often the NEWS.md notice is written a long time before > the PR is merged. You can look at the commit history > <https://github.com/JuliaLang/julia/commits/master/NEWS.md> if you want. > > Isaiah: Yes, Packages is a really important point for using 0.3.X. I had > that on my mind while writing my comment, but somehow I missed it. > > kl. 15:01:44 UTC+2 fredag 26. september 2014 skrev Isaiah følgende: > > Master should be usable, but many packages won't be. Given the limited > > bandwidth of package maintainers, and the scope of pending changes, > > supporting both 0.3 and 0.4-dev is probably not realistic for many > > packages. > > On Sep 26, 2014 3:19 AM, "Ivar Nesje" <[email protected] <javascript:>> > > > > wrote: > >> I think this is a too strong statement. There are definitely happening a > >> lot on the master (0.4-dev) branch, but it should be quite usable even > >> without reading the majority of Github issues. The more users we have, > >> the > >> earlier concerns is raised, and the earlier we can fix them and prepare > >> for > >> the final release. You should definitely avoid master on any project with > >> a > >> deadline tough. > >> > >> For people compiling julia from source, it would be a great service to > >> the community to use `release-0.3` instead of the explicit version tags. > >> All changes to release-0.3 is first tested on master before they are > >> backported if they don > >> > >> kl. 06:15:11 UTC+2 fredag 26. september 2014 skrev Steve Kelly følgende: > >>> Case and point: https://github.com/JuliaLang/julia/commit/ > >>> 2ef8d31b6b05ed0a8934c7a13f6490939a30b24b > >>> > >>> :) > >>> > >>> On Thu, Sep 25, 2014 at 11:46 PM, Isaiah Norton <[email protected]> > >>> > >>> wrote: > >>>> Checking out the release branch is fine; the 0.3.1 tag is on that > >>>> branch. > >>>> > >>>> On Thu, Sep 25, 2014 at 11:12 PM, John Myles White < > >>>> > >>>> [email protected]> wrote: > >>>>> I think it's more correct to check out tags since there seems to be > >>>>> work being done progressively on that branch to keep up with > >>>>> backports. > >>>>> > >>>>> Not totally sure, though. > >>>>> > >>>>> -- John > >>>>> > >>>>> On Sep 25, 2014, at 7:58 PM, David P. Sanders <[email protected]> > >>>>> wrote: > >>>>> > >>>>> > >>>>> > >>>>> El jueves, 25 de septiembre de 2014 19:59:41 UTC-5, John Myles White > >>>>> > >>>>> escribió: > >>>>>> I just wanted to suggest that almost everyone on this mailing list > >>>>>> should be using Julia 0.3, not Julia 0.4. Julia 0.4 changes > >>>>>> dramatically > >>>>>> from day to day and is probably not safe for most use cases. > >>>>>> > >>>>>> I'd suggest the following criterion: "are you reading the comment > >>>>>> threads for the majority of issues being filed on the Julia GitHub > >>>>>> repo?" > >>>>>> If the answer is no, you probably should use Julia 0.3. > >>>>> > >>>>> Thanks for the nice, clear statement, John! > >>>>> > >>>>> Currently I have been using > >>>>> > >>>>> git checkout release-0.3 > >>>>> > >>>>> and compiling from there. > >>>>> > >>>>> Is this the "correct" thing to do? I notice there is now a v0.3.1 > >>>>> tag. > >>>>> > >>>>> David. > >>>>> > >>>>>> -- John
