clojars

http://clojars.org discussion and “support”, see http://status.clojars.org for status.
2016-09-18T16:59:46.000164Z

Hi guys. I’m looking into the feed.clj.gz file format, am I right that 1) versions should be sorted by time of release 2) scm.tag is the commit of the latest release? If the both are ‘yes’, then there’s probably a bug there, for instance:

{:group-id "org.clojars.smallrivers", :artifact-id "aleph", :description "a framework for asynchronous communication", :scm {:connection "scm:git:<git://github.com/dajac/aleph.git>", :developer-connection "scm:git:<ssh://git@github.com/dajac/aleph.git>", :tag "a361d01502e6711a845a184b783685d264a0bd45", :url "<https://github.com/dajac/aleph>"}, :versions ["0.2.1-SNAPSHOT" "0.2.1-rc5" "0.2.1-rc4" "0.2.1-alpha2-SNAPSHOT”]}
however on clojars versions are sorted as: 0.2.1-rc5 0.2.1-rc4 0.2.1-SNAPSHOT 0.2.1-alpha2-SNAPSHOT

2016-09-18T17:01:13.000166Z

also :tag in the feed points to the 0.2.1-SNAPSHOT which is probably not the latest one (but the first in the :versions)

2016-09-18T17:13:45.000171Z

@smaant it doesn't look like we do any sorting on that data, but would welcome a PR to fix the sorting and to show the latest scm. The feed is generated here: https://github.com/clojars/clojars-web/tree/master/src/clojars/tools/generate_feeds.clj#L13

2016-09-18T17:14:12.000173Z

Yeah, i’m looking at it right now too

2016-09-18T17:16:00.000175Z

Will do a PR, yes. Would you mind if I also extend format a little bit - I want to have tags for all versions? Will make it backward compatible with current one.

2016-09-18T17:24:33.000176Z

Yep, that's fine as long as it stays backward compatible. Would you mind filing an issue for it as well for release tracking purposes?

2016-09-18T17:26:27.000177Z

One for bug and another for extension?

2016-09-18T17:30:54.000178Z

yes, 2 issues probably makes sense

2016-09-18T18:21:06.000180Z

@tcrawley i would probably need some input here https://github.com/clojars/clojars-web/issues/563