Release 0.4.0.M2

[viktorklang]

I propose to cut the next milestone after the following PRs/Issues are resolved:

#62 (potentially: #82)
#80
#81
#63

What say you @reactive-streams/contributors

[smaldini]

Agree for M2, but not sure about releasing an artifact. Or well shall we duplicate the artifact as M2 ?

[benjchristensen]

I agree with those issues being resolved and then releasing the next milestone.

[tmontgomery]

👍

[rkuhn]

@smaldini: changing the argument type of request(long) will require new artifacts to be published.

[smaldini]

Ha missed that one. Fair enough. Which issue is that, the firehose one ?

[viktorklang]

@smaldini this PR : #82 attempting to reach consensus for the firehose :)

[smaldini]

where are we on this release ? any help required ?

[viktorklang]

Check the issues/pr links in the description, I believe there are a couple
of votes we're waiting for, but most should be good.
On Jul 17, 2014 8:33 PM, "Stephane Maldini" [email protected]
wrote:

where are we on this release ? any help required ?

—
Reply to this email directly or view it on GitHub
#83 (comment)
.

[viktorklang]

Seems like it's #62 and #63 left with #62 being basically good to go but I am still unsure about #63, can we expedite it?

[smaldini]

We shall expedite it. Sorry I've been sucked into a spiral of time, and work.

[rkuhn]

As we’ll need the right artifacts published before we can meaningfully test the TCK (see #91) I propose that we publish the current state of the API as M2 and then add the TCK in M3. This means that outstanding issues like #63 are deferred to M3 as well.

[ktoso]

+1, sounds like a good plan to me.

[smaldini]

Right, I'm on it now. shall that include the #104 or we delay that to M3 along with #63 ?

[rkuhn]

If you give your thumbs-up on #104 then that makes three positive votes, we’d need a fourth one to merge it. Shall we give it a few more hours? That would mean that M2’s API should be really close to or identical with 1.0 (famous last words).

[smaldini]

Ok, I've myself updated signatures on Reactor and pending the last votes on #104 before moving forward.

[viktorklang]

#110 shouldn't affect the M2 release as it's just a spec update.

[smaldini]

I take it we can move forward #104 is now fixed.

[rkuhn]

AFAICS yes. Do you want to publish it?

[smaldini]

Staging now

[smaldini]

Deployed onto sonatype, I guess we need some time before maven central sync :)

[ktoso]

Great, thanks for the quick reaction / release guys :-)

[rkuhn]

Thanks, Stephane! It is already there, just not yet on the search index.