Fork me on GitHub
#clojure-dev
<
2015-08-10
>
ragge10:08:24

@alexmiller: Hi! What's the workflow for "withdrawing" a patch/proposed solution, like in http://dev.clojure.org/jira/browse/CLJ-1794. If I no longer think my approach/solution is good, what should I do?

danielcompton10:08:17

@ragge: just leave a comment

ragge10:08:18

@danielcompton: done that, but I don't think the patch/approach should be considered further by screeners etc... as it currently stands, description doesn't match discussion in comments

danielcompton10:08:54

Looks ok to me, people will read the comments for context before going off the deep end. If you’d created the ticket then you could edit the description to add your notes there, not sure if that’s kosher if it’s not your ticket.

ragge10:08:54

Well, I didn't create it but I edited the description quite heavily (from a link to a tweet basically) so I do feel some responsibility for it simple_smile

ragge10:08:13

But fair enough

ragge10:08:42

Just thinking what would be most effecient if I was to screen this ticket myself (without any prior knowledge)

danielcompton10:08:37

sure, maybe add a note at the bottom of the description describing why you think what you think

alexmiller14:08:20

@ragge we can delete the patch if you like

alexmiller14:08:28

@ragge I just modified the description to make current status clearer for me at least

jonas16:08:27

I’d like to release a new version of data.csv which I haven’t done in a long time. Such a long time in fact that I have completely forgotten the release process simple_smile. Is it documented anywhere? Do I need to update the pom.xml file or is it somehow automated?

alexmiller16:08:25

that is up to date

alexmiller16:08:01

the pom.xml will be modified by the build process you kick off in Hudson - it will ask you what version to release, update it, release, update again to next snapshot

alexmiller16:08:14

let me know if you need anything

jonas16:08:33

ok, thanks! I’ll give it a try

jonas17:08:27

@alexmiller: As far as I can tell it worked as advertised on the “How to Make Releases” doc and the release should be on its way to maven central now

jonas17:08:41

nice! I guess it takes a while for the maven central search to catch up as it still lists 0.1.2 as the latest release http://search.maven.org/#search%7Cga%7C1%7Cdata.csv

alexmiller17:08:16

oh, yeah that's created in some batch process, takes a while for it to catch up

alexmiller17:08:29

usually takes 10m to an hour for a deployed release to be downloadable

alexmiller17:08:37

in my experience