Cargo version

[mdinger]

I didn't see the cargo version process specified but cargo is currently version 0.0.1 and rust version 1.0 alpha. Will cargo go 1.0 with rust? If this is undecided, it might be useful to specify somewhere.

[coderanger]

To make this a bit more concrete, it would be really nice if when the 1.0 beta comes out (or next alpha if one happens) that there is a simultaneous alpha/beta release of cargo. This makes life a lot easier for people building packages and distributing Rust since right now there is no specific version of Cargo that corresponds to 1.0.0-alpha beyond whatever commit the official installers happened to use.

[jljusten]

@brson: Since you updated the rust page for the alpha release, would you happen to know which cargo version was included with the alpha release builds? Maybe that cargo version could be tagged?

[brson]

At the moment there aren't concrete plans to make releases of Cargo. The Cargo nightly that corresponds to releases of Rust is in this file: https://github.com/rust-lang/rust-packaging/blob/master/cargo-revs.txt. Note that it's only set up to permanently record cargo revisions for stable releases of Rust.

cc @alexcrichton

[jljusten]

cargo-revs.txt has:

1.0.0: 2015-01-07

That doesn't really indicate a particular cargo hash, nor does it indicate 'alpha'. Would it be possible to clarify that in cargo-revs.txt? (Assuming a cargo tag isn't possible.)

[brson]

@jljusten That's right, it's just a date from the nightly archives, and it's not connected to the alpha. The way cargo versions in rust-packaging is set up doesn't account for the pre-1.0 release process - it only considers stable releases to be releases.

It would be possible to add more metadata there but I'm not sure its the appropriate place since the tool doesn't require it.

[jljusten]

@brson: Is it possible to trace that nightly cargo release back to a cargo repo version?

[brson]

@jljusten Yes, cargo --version will print the git commit, though I'd like to make that bit of metadata more accessible for tooling: rust-lang/rust#21243

[jljusten]

In case anyone is interested, for the 1.0.0 alpha it appears to be 23ed197:

rust-1.0.0-alpha-x86_64-unknown-linux-gnu/bin$ ./cargo --version
cargo 0.0.1-pre-nightly (23ed197 2015-01-06 02:37:42 +0000)

I suppose the cargo-revs.txt date discrepancy is due to the commit vs. build times, but it certainly doesn't help with the confusion. :)

[alexcrichton]

I don't particularly have many strong opinions here, as @brson said we don't have a clear story for the versioning of Cargo separate from Rust right now.

That being said I don't mind "cutting a version" at some point to just say that we're on 0.1.0 or something like that.

[beatgammit]

"cutting a version" makes it much easier to package, so I'm very much in favor of giving it a version number.

@alexcrichton Where is the best place to start the discussion on if/how cargo releases relate to rust releases?

[callahad]

FWIW, Rust 1.0.0-beta shipped with:

$ ./cargo --version
cargo 0.0.1-pre-nightly (84d6d2c 2015-03-31) (built 2015-03-31)

Link: 84d6d2c

[lloeki]

FYI, this is blocking on Homebrew, so there's currently only a rust package and no cargo, which drastically reduces usefulness. It would be great if something as simple as a rust-1.0.0-beta tag could be created in git, and possibly a matching release on the GitHub page.