-
Notifications
You must be signed in to change notification settings - Fork 535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update ref to 1.0.0.final #267
Conversation
Looks good so far :) |
Any feedback on the grammar, I think so far so good on this side but I feel a bit dodgy on this aspect to check the related box :) |
@smaldini I've done a pass, but I'd like to have more eyes on it. |
maybe we can start the release of the binary and checks the impls too. |
Right let's start the testing process, should I publish final on codehaus before merging @viktorklang ? |
@smaldini I'm not sure, assuming we already validated the integrity of the bits (perhaps do a RC5-final binary comparison before pushing?) it seems like we should be able to push it to maven central. |
@viktorklang I'm usually risk averse and I would just merge and push to maven. |
@smaldini Check the SHA of the RC5 jars and compare to the SHA of the final jars before pushing, and I'll sleep better :) |
I've rarely seen 1.0.0 that works for everyone anyway, thats why there is a minor digit hey 💃 |
there's a bunch of TCK javadoc missing but well... |
@smaldini documentation improvement is never done :) |
Strange , .asc and md5 are different from version to another. |
which is strange since I'm only one commit away. looking at the content |
right Manifest is regenerated
|
@smaldini Alright, if that's the only diff then let's go :) |
It is on its way to maven central, joyful tear. |
Awesome, @reactive-streams/contributors should update to it so we can Cheers,
|
@jsuereth and @rkuhn suspect that the ".final" part of the version number Cheers,
|
+1
|
@alkemist The problem would be that OSGi considers "1.0.0" < "1.0.0.RC5", how do we set a different version in the OSGi manifest, something like "1.0.0.final" is actually the right thing for OSGi. |
Still +1. |
background on why using "1.0.0.final" for Maven is problematic: http://mojo.codehaus.org/versions-maven-plugin/version-rules.html (in short: "1.0.0.final" is interpreted as "0.0.0-1.0.0.final" and effectively only string comparison is used) |
@alkemist I take it that your +1 is for the "1.0.0" maven version. In sbt I would know how to fix the OSGi version, how do we do this in gradle? |
FWIW, Ivy (therefore SBT) and Gradle understand that final > rc. |
I also think we should release 1.0.0 and then if OSGi is a mess release 1.0.1 as a patch release. |
@rkuhn what exactly do you want to do? Just use |
Yes, that would solve all the issues AFAICS.
|
Solving all issues sounds good to me Cheers,
|
Gradle OSGI plugin was already taking care of the bundle version but yeah making explicit is not harmful. |
I tried it out with Viktor’s instructions locally and this was the resulting manifest:
I tried to find information about what that version string means but that syntax is not mentioned anywhere in the freely available docs (I do not have an OSGi specification handy). |
Yeah Grade OSGI plugin uses the version you specify :) |
Ah, use |
we don't need that extra line |
Is that correct enough for another try :) ?
|
Who uses OSGI again ? sorry fixing that. |
|
now ? |
I'm not sure about: "Export-Package: org.reactivestreams;version="1.0.0.release"" For the record, let it be known, OSGi is an instrument for inflicting pain. |
I'm going to make a slide about that springio.net tomorrow I think... |
@smaldini a slide about what? OSGi? |
Yeah 👍 who cares about specs that are actually changing something in async processing without involving operating systems type containers. |
@smaldini Your latest manifest is looking good! |
@rkhun Just to make sure, is "1.0.0.release" considered to be newer than "1.0.0.RC5" by OSGi? (note difference in upper/lower case) |
Yes, it is, see https://osgi.org/javadoc/r4v43/core/org/osgi/framework/Version.html (it uses |
@rkuhn Thanks! Alright, so it looks like we have a solution! let's switch to version Sounds good? |
The tag is not here yet since the PR was not merged. Right now it can then :) Sent from my iPhone
|
@rkuhn @smaldini @benjchristensen @alkemist and @reactive-streams/contributors in general. I think we ought to merge this PR and publish the fixed |
Yes, I’ll start with the release now. |
Godspeed Cheers,
|
Thanks @rkuhn! I was literally in flight from London Publisher to Barcelona Subscriber, fortunately flights are using backpressure too. Sent from my iPhone
|
@smaldini There is back pressure for sure, the longer the flight the worse back pain... |
WIP for #223