More disruption between 0.6 and 0.7/1.0?

Internals & Design
1

I was just wondering, if it would be OK to do more disruptive changes - like APIs/Interfaces/splits in packages at the 0.7/1.0 julia boundary?

2

You mean in your packages? Seems like a reasonable time to do it.

3

I would encourage to get as many breaking changes as possible before 1.0.0; as in now better than after.

4

We’ll be doing this for JuMP also, but it will be a soft break. JuMP/MathProgBase (0.18.x) will continue to be usable in some form in 0.7/1.0.

5

I guess there can be arguments for both for and against coordinating breaking changes with Julia language releases. I am planning some myself that rely on named tuples.

But if the changes are otherwise orthogonal to the language proper, I can also see arguments against it — users and developers will be dealing with a lot of change already, it may be better to spread it out.

Also, I am not sure what the timeline is for v0.7. If a set of packages or an API is ripe for reorganization, why not do it now?

1 Like
6

I think the overall goal should be to make the 0.7 to 1.0 transition as smooth as possible.

7

i agree. I changed the title.