New release?

[spraints]

Howdy everyone! (in particular, @pmiossec and @sc68cal)

I think we should cut another release (0.19.0). Is there anything that you think should be wrapped up before we do? One thing I'd like to do is to try out the new releases API so that creating a release is a one-click type of deal. What else?

Tracking this with the v0.19.0 milestone.

[pmiossec]

I'm Ok with that but I want #442 and #452 included... (and perhaps a little more things that I just think about this morning. I will inform you if we should wait for that after a quick test)

I don't know the release API. I will have a look.

[pmiossec]

Here it is #453 ;)

[spraints]

I don't know the release API. I will have a look.

Same here. It's totally a non-essential, it's just something I've been interested in doing.

[spraints]

(I guess a milestone would be appropriate here.)

[sc68cal]

Agreed - there's a ton of work that @pmiossec has done that should get merged. Otherwise, I think we got a lot of PR's from the community taken care of. The only outstanding one is #346 - but it sounds like there are unresolved issues with it. Maybe after we release 0.19 we can reach out to the original author of it and see if he's had any luck figuring out some of the edge cases.

PS - @pmiossec you're doing great work

[eduaquiles]

Hi,
we (the team I'm working on) believe #311 should be included on this release. This is almost becoming a show stopper for us.

[pmiossec]

@eduaquiles None of us have the problem. Could you jump into with your team and try to solve this problem.
If you do it, we will wait for the release...

[eduaquiles]

Hi, I tried to reproduce the problem in our project and couldn't right now. If someone on the team manages to reproduce it soon, I'll try to replicate in a test case here.

[pmiossec]

I am REALLY interested by a release before Thursday!
I also would like that #482 must be included and if possible #483.

I know that the release process is not finished but I think it's not blocking and could wait a little....

[pmiossec]

I think that we are ready to release, now...

[spraints]

On its way...

[pmiossec]

🆒
I hope the release process will work ;)

[spraints]

0.19.0 is done!

The new tasks worked, except for uploading the release binary. I'm not sure why.

[pmiossec]

It used to work...
I will test to see if I have not introduced a last minute bug...
On 20 Nov 2013 08:15, "Matt Burke" notifications@github.com wrote:

Closed #451 #451.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/451
.

[pmiossec]

Was the upload successful this time with the 0.19.1? or should I have a look?

[spraints]

Yeah, 0.19.1 worked. I changed Release.proj quite a bit, though I'm not sure what substantive change I made.

[pmiossec]

I have done a new milestone (v0.19.2). And after the remaining PR merged, I wish we could release a new version because I would like to see #489 released as soon as possible...

[spraints]

0.19.2 is on its way. Having NEXT.md, the automated releases, and a milestone made making the release soooo much easier!

[sc68cal]

🍻

[pmiossec]

Hey guys! What about a new release?

I would like to see the small changes #551, #556, #557, #558 (if someone could test it in time) in it but otherwise, I think we could release a new version.

If you see something else than should be inside the new release...

[spraints]

👉 #559