Tags are generally used when something hasn't been resolved yet. E.g. the `decision` tag means a nontrivial decision needs to be made.
the `0.4` and `0.4-projects` tags are the best way to get a feel for what is on the agenda for 0.4. There may be more big projects, or less, it's impossible to say right now, but there are already some big things lined up. To get a feel for the most interesting changes, I'd suggest sorting by number of comments. This isn't a perfect measure, but it does bring some interesting things to the top; Array Views, libgit2 integration, overloading of field access (e.g. `a.b`), associating data with functions, modules, etc... (that's a fancy way of saying better documentation), Incremental GC upgrade, C-struct compatibility.... and those are just the largest, most interesting ones I can see for now. Of course, there may be even more groundshaking and interesting things to come out, I know some work has been done regarding multithreading, static compilation, etc... but I cannot hazard a guess as to when we might see such things appear in actual builds. -E On Thu, Aug 21, 2014 at 3:23 AM, Ross Boylan <[email protected]> wrote: > On Wed, Aug 20, 2014 at 11:27:11PM -0700, Kevin Squire wrote: > > On Wednesday, August 20, 2014, K Leo <[email protected]> wrote: > > > > > > Now the nightlies will be the early builds of 0.4. Is that reasonable > to > > > assume these early builds will be less reliable and so I should better > stay > > > with 0.3 for some time? > > > > > > > They probably won't get toooo broken, but there are a lot of potentially > > breaking changes planned, so quite likely less reliable than what you've > > been seeing. > > Is there a way to get a sense of what those are, esp. stuff we might > want to keep in mind as we write code for 0.3? Is there some place to > go for a roadmap? > > I tried https://github.com/JuliaLang/julia/milestones/0.4-projects, > and paying special attention to the "breaking" tag, but I'm not sure > if that's the way to go. > > Finally, is there a way to find what the tags mean beyond guessing > from the tag? For example, what exactly is broken by something tagged > "breaking"? I don't mean what the specific changes are for a > particular issue, but what are the situations in which it applies? > > Another example is the "decision" tag. Does that mean a decision has > been made? Or that it needs to be made? > > Thanks. > > Ross Boylan >
