Clojurians Log v2

@danielcompton: re ^: we have an open PR that would allow us to move to postgres

so it's a possibility

yeah, I was thinking of that

although it’s pretty nice that it can all run out of an sqlite db

yeah, agreed

@micha: it looks like aether grabs the maven-metadata last, just before mutating and pushing it back up:

Sending org/immutant/transactions/2.1.2/transactions-2.1.2.jar (8k)
    to <https://clojars.org/repo/>
Sending org/immutant/transactions/2.1.2/transactions-2.1.2.pom (5k)
    to <https://clojars.org/repo/>
Sending org/immutant/transactions/2.1.2/transactions-2.1.2.jar.asc (1k)
    to <https://clojars.org/repo/>
Sending org/immutant/transactions/2.1.2/transactions-2.1.2.pom.asc (1k)
    to <https://clojars.org/repo/>
Retrieving org/immutant/transactions/maven-metadata.xml (1k)
    from <https://clojars.org/repo/>
Sending org/immutant/transactions/maven-metadata.xml (1k)
    to <https://clojars.org/repo/>

I was doing it a deploy and noticed it, so thought I'd let you know

cool

snapshots might be different

they will be a little different, since there are two metadata files involved - the top-level, and one in the 0.1.0-SNAPSHOT dir

I must be late to the party ... Clojars is back up, but what's with "Promotion currently disabled"?

@hlship: ah! Well, I did a deploy right before the outage, so forgot to send out the release announcement. it's still sitting in Drafts/

we're going to get rid of the releases repo, since it isn't used much, and has some fundamental issues

and I had to disable it now, since it pushes to s3, and that s3 bucket belonged to alex osborne

he wanted to be free of it

see https://github.com/clojars/clojars-web/issues/415#issuecomment-167932198

did you actually use <http://releases.clojars.org|releases.clojars.org>?

OK. What counts for me is that I deployed a new version to Clojars (io.aviso/pretty 0.1.21) and it appears to be available publically.

right, promotion has nothing to do with that

everything you deploy is immediately available

works for me!

promotion was just for pushing things to the "release" repo

that's one of the points of confusion around promotion