On 2 December 2015 at 12:58, Robbie Gemmell <[email protected]> wrote: > On 2 December 2015 at 10:51, Oleksandr Rudyy <[email protected]> wrote: >> Hi all, >> >> I have produced 6.0.0 RC4 build and would like to initiate voting to >> release Qpid Java Components 6.0.0 RC4 as the final 6.0.0. >> >> The release artifacts are available from maven staging repo at: >> https://repository.apache.org/content/repositories/orgapacheqpid-1055 >> >> If you want to test it out using maven you can add temporarily the staging >> repo into your poms: >> <repositories> >> <repository> >> <id>staging</id> >> <url> >> https://repository.apache.org/content/repositories/orgapacheqpid-1055</url> >> </repository> >> </repositories> >> >> >> Please indicate your vote below. If you favor releasing the 6.0.0 RC 4 >> artifacts as 6.0.0 GA, vote +1. If you have reason to think RC 4 is not >> ready >> for release, vote -1. >> >> This vote will close at 17:00 UTC on Monday 7th December, at which time >> I will tally the votes. >> >> Kind Regards, >> Alex > > I tried the broker out using the binary assembly available in the > staging repo, which seemed fine. However I couldn't actually see any > obvious source release assembly, which is what would actually > constitute the release. Is it hiding somewhere in particular I've not > seen it, or is it missing? > > In the past the source archive was produced outside the ant/maven > builds along with the various others for the cpp bits etc. The maven > build can create a source release archive itself if desired, there is > actually a basic default variant of this in the apache parent by > default but it was suppressed in the java build pom previously as it > was being handled elsewhere (its similarly suppressed in the JMS > client build, but replaced with a specific assembly module handling > both the source and binary archives). > > Robbie
I had meant to add but forgot to when eventually writing the mail.. Its a good idea to put all the artifacts to be mirrored into the dev area of the dist repo at https://dist.apache.org/repos/dist/ before the vote. That makes it clearer what is/isn't going to be present in the end and means the only action needed to release them after the vote is a simple remote copy operation to the release area, helping reduce scope for any mistakes and that what folks test is what gets released. Robbie --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
