Getting to 1.0 -- How can we get packages to "make that tag"?

[kristoffer.carlsson]

@cce

Is the lack of a 1.0 a suggestion to users that they shouldn’t depend upon it for production work?

No.

@cce

What is the commitment to keep the API stable?

The commitment is to tag a breaking release when the API change. The rate such tags will come has to be communicated explicitly by the project and cannot be encoded in the version number.

@cce

When I mark a dependent on DataFrames , how should semantic versioning work?

See 6. Compatibility · Pkg.jl

@cce

How about dependencies of DataFrames … are their API going to be stable?

Until the authors of them decide to make breaking changes. Also not something that can be encoded in a version number.

@cce

Stable, yet pre-1.0 packages, are even more annoying once dependent packages enter the picture. Just today, I noticed DataFrames was somehow downgraded in a local environment.

This has nothing to do with being pre -1.0 but just a consequence of a package tagging breaking releases.

---

In summary, there seems to be a lot of questions here but none of them seem really related to tagging a 1.0. What you basically say is that you want packages to make fewer breaking changes. That is a very valid position. But it is the way you want packages to be developed that you want changed, not if a package go from 0.18 to 0.19 or 18.0 to 19.0.