Hi Robbie, Thanks for the note about releasing from master. I changed the broker release instructions [1] to release next major/minor version from master.
Kind regards, Alex [1] https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Broker-J On Thu, 20 Dec 2018 at 12:36, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > > On Wed, 19 Dec 2018 at 17:09, Oleksandr Rudyy <oru...@gmail.com> wrote: > > > > Hi folks, > > > > I built release artefacts for Qpid Broker-J version 7.1.0 RC1. > > Please, give them a test out and vote accordingly. > > > > The source and binary archives can be grabbed from: > > https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.1.0-rc1/ > > > > The maven artifacts are also staged for now at: > > https://repository.apache.org/content/repositories/orgapacheqpid-1165 > > > > The new versions comes with a number of improvements and bug fixes. > > You can find the full list of JIRAs included into the release here: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12338931 > > > > Kind Regards, > > Alex > > > > P.S. For testing of maven broker staging repo artefacts, please add into to > > your poms the staging repo as below: > > > > <repositories> > > <repository> > > <id>staging</id> > > <url> > > https://repository.apache.org/content/repositories/orgapacheqpid-1165</url> > > </repository> > > </repositories> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > For additional commands, e-mail: users-h...@qpid.apache.org > > +1 > > I checked things over as follows: > - Verified all the signature and checksum files. > - Ran "mvn apache-rat:check" to verify headers in the source archive. > - Checked for LICENCE and NOTICE files being present in the archives. > - Ran the build and tests with "mvn clean verify -DskipITs=false". > - Started broker from binary archive, used the web console to create a queue. > - Ran the Qpid JMS 0.40.0 RC1 HelloWorld example against the broker. > > As mostly an aside, I think it might have been nicer to create the > release from master, then only create a branch later if/when actually > needed. Branching first in this way means master ends up never having > any tags to help somewhat deliminate its activity later, and at least > currently the version change commits are the only difference between > it and the branch. Commits must already be cherry picked to do a 7.1.x > when that may not have yet been necessary for a period (or possibly at > all depending on the work+releases occurring later). > > Robbie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
