Although I believe Jiahao is looking for someone to step up and take charge of a "this week in Julia" publication. Hans, since you want this information yourself, you've just made yourself the perfect candidate.
As that pulse link that Adam forwarded shows, there is a _lot_ of material to cover just in the last week, much of it pretty darn revolutionary. So I'm sure you'll be very busy writing it all up :-). --Tim On Friday, September 26, 2014 07:24:42 AM Adam Smith wrote: > Hans, like John said in the OP, v0.4 is really unstable right now. I would > not expect them to publish updates to NEWS.md for new things that could get > reverted a few days later. If you want to monitor updates, Github provides > some really nice tools, like the Pulse > page: https://github.com/JuliaLang/julia/pulse/weekly > > There are a number of ways to monitor something in flux like v0.4 without > requiring manual updates to a changelog. > > On Friday, September 26, 2014 6:30:48 AM UTC-4, Hans W Borchers wrote: > > Ivar, > > > > thanks for this clarification; I was really under the impression that -- > > like > > for Perl and other projects -- I might never ever again hear from a Julia > > 0.4 > > version. > > > > A question I asked got buried in another thread and never answered, so I'd > > like > > > > to repeat it here: > > Will the NEWS.md file immediately document the (disruptive or > > > > non-disruptive) > > > > changes? That would be very helpful, even if the change is withdrawn > > > > later on. > > > > Also, every NEWS entry could include a date to make it easier to follow > > > > the > > > > development. > > > > By the way, I am a bit worried about some of the names that seem to come > > up in a > > next version of Julia. For example, 'Nullable' or 'NullableArray' sound > > strange > > for me in a technical computing environment. > > > > On Friday, September 26, 2014 9:19:37 AM UTC+2, Ivar Nesje 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.
