Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

per-API crate version with appended build info: +<revision> #38

Closed
Byron opened this issue Mar 22, 2015 · 1 comment
Closed

per-API crate version with appended build info: +<revision> #38

Byron opened this issue Mar 22, 2015 · 1 comment
Assignees
@Byron
Milestone
v0.1 - feature co...

Comments

@Byron
Copy link
Owner

Byron commented Mar 22, 2015

We control crate versions with one version for all, which should only change if the generator changes, and thus produces different code. Standard semver rules apply.

To assure we don't degenerate the exact API version the crate represents, we should append build metadata, to get versions such as 0.1.0+20150309.

That way, we will only produce new crate versions if something truly changed.
@Byron Byron added this to the v0.1 - feature completeness milestone Mar 22, 2015
@Byron Byron self-assigned this Mar 22, 2015
@Byron Byron closed this as completed in 8ad316b Mar 22, 2015
Byron added a commit that referenced this issue Mar 22, 2015
@Byron
fix(cargo): repository/source-code link
030c40d 
Previously it pointed to a timestamp file. Unified repository
source code link generation, and simplified 'deps.mako'.

Related to #38
@Byron
Copy link
Owner Author

Byron commented Mar 22, 2015

You can watch the development stream on youtube.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Byron Byron

Labels
None yet
Projects
None yet
Milestone
v0.1 - feature completeness
Development

No branches or pull requests
1 participant
@Byron