On Thu, Mar 5, 2015 at 5:19 AM, Robbie Gemmell <[email protected]> wrote:
> Hi everyone, > > I noticed yesterday that the latest '0.32-SNAPSHOT' java builds > weren't in fact for 0.32 at all, but rather from trunk instead. The > reason being that trunk is still versioned 0.32-SNAPSHOT despite the > recent branching, so the nightly job has been publishing those instead > of the next version. > Urgh, I didn't anticipate that. I left the trunk versions unchanged because I wasn't sure what versions to change them too. I think you've addressed this problem well enough in the short term, but if anyone would prefer it, I can use 0.33 as a placeholder release and update the versions on trunk. > I created a new job to publish actual 0.32 snapshots starting yesterday: > > https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Artefact-Release-0.32/ > > I have disabled the trunk until trunk is updated with the next verison > number: > https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Artefact-Release/ Related note: I am not generating the java binaries for the distribution. My release tool produces source distributions, and the old release.sh was never updated for maven. Mark Soderquist requested them at https://issues.apache.org/jira/browse/QPID-6422 Keith, would you generate these? You can add them to the dist repo under dist/dev/qpid/$release/binaries/.
