Skip to content
This repository has been archived by the owner on Aug 12, 2022. It is now read-only.

Tag Tau v0.1.0 #7488

Merged
merged 5 commits into from
Jan 7, 2017
Merged

Tag Tau v0.1.0 #7488

merged 5 commits into from
Jan 7, 2017

Conversation

waldyrious
Copy link
Contributor

@waldyrious waldyrious commented Jan 7, 2017

This version restores compatibility with Base, after the MathConst --> Irrational change, and makes the tests pass again.

@waldyrious waldyrious changed the title Tag Tau v0.0.4 Tag Tau v0.1.0 Jan 7, 2017
@waldyrious
Copy link
Contributor Author

waldyrious commented Jan 7, 2017

Please squash the commits on merging. This is the first METADADA.jl update I'm making since I got commit rights in Tau.jl, and tried to follow the pattern of the past releases, which resulted in a few hiccups in the process.

@@ -0,0 +1 @@
julia 0.4
Copy link
Contributor

@tkelman tkelman Jan 7, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do tests pass on 0.4? ref JuliaMath/Tau.jl#12 looks like travis isn't enabled?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought I had tested that in JuliaMath/Tau.jl@378fa9f, but I clearly overlooked the definitions in .travis.yml. I'll test in my fork where I have enabled Travis testing (I need @Aerlinger's intervention to enable Travis in the main repo), and will report back.

Copy link
Contributor Author

@waldyrious waldyrious Jan 7, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tkelman confirmed, the tests don't actually pass in 0.4. I'll look into supporting it with Compat later (JuliaMath/Tau.jl#13), but for now I'll change the requires file in this PR and in the repo (I could make a new tag and release 0.1.1, but since the travis.yml definitions in 0.1.0 don't actually test 0.4, I think that'd be overkill.)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tightening version requirements requires modifying the existing tags in-place like you just did. Releasing a new tag that's 0.5-only wouldn't change the fact that the 0.1.0 tag (if you hadn't just fixed it) would be installable but non-functional on Julia 0.4.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm assuming you're talking about "tags" as in "version directories in METADATA.jl", not actually git tags in the package's repo, in which case, yeah, I see what you mean. Let me know if I misunderstood, though.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm assuming you're talking about "tags" as in "version directories in METADATA.jl"

Right, published versions in METADATA. Those can be a subset of the git tags in the package repo, some of the latter might go unpublished.

@tkelman tkelman merged commit 8c8a4e6 into JuliaLang:metadata-v2 Jan 7, 2017
@waldyrious waldyrious deleted the patch-1 branch January 7, 2017 20:08
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants