On Fri, Dec 21, 2018 at 4:55 AM Robbie Gemmell <[email protected]> wrote:
> On Thu, 20 Dec 2018 at 16:14, Robbie Gemmell <[email protected]> > wrote: > > > > On Wed, 19 Dec 2018 at 22:00, Ganesh Murthy <[email protected]> wrote: > > > > > > Hello All, > > > > > > Please cast your vote on this thread to release RC1 as the > > > official Qpid Dispatch Router version 1.5.0. > > > > > > RC1 of Qpid Dispatch Router version 1.5.0 can be found here: > > > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.5.0-rc1/ > > > > > > The following features, improvements, and bug fixes are introduced in > 1.5.0: > > > > > > Features - > > > DISPATCH-1142 - Edge Router Module - Connection manager to select > > > the active uplink > > > DISPATCH-1143 - Connection-scoped link routes > > > DISPATCH-1145 - Edge Router - Implement address proxy component > > > DISPATCH-1150 - A request/response message client API for core > > > DISPATCH-1154 - Synchronize routed link configurations on edge > > > router with interior router > > > DISPATCH-1156 - Delivery echo-prevention for edge routers > > > DISPATCH-1194 - Asynchronous address lookup on attach for Edge to > > > determine if there are link-route destinations > > > DISPATCH-1224 - Waypoints may be attached by external containers > > > without using auto-links > > > > > > Improvements - > > > DISPATCH-1141 - Add an event API in the router core to more > > > cleanly support module interactions > > > DISPATCH-1147 - Expose address priority > > > DISPATCH-1152 - Improvements to the core-endpoint API > > > DISPATCH-1159 - Remove the term "uplink" from the edge router - > > > It's confusing > > > DISPATCH-1160 - Add edge address tracking module to interior > > > routers which will inform edges of mobile address receiver changes > > > DISPATCH-1165 - Generate egress-link histograms for more kinds of > > > connections > > > DISPATCH-1178 - Allow unspecified router-id in configuration - > > > select a random ID > > > DISPATCH-1191 - Log files could use some analysis and summary tools > > > DISPATCH-1199 - [tools] Log scraper tool should be moved to tools > directory > > > DISPATCH-1200 - [Test] system_tests_edge_router must import 're' > > > DISPATCH-1201 - [tools] Scraper is mishandling transfers with no > > > AMQP properties > > > DISPATCH-1202 - [tools] Scraper README is stale > > > DISPATCH-1205 - Allow signed int values >= 0 be parsed as unsigned > int > > > DISPATCH-1207 - [tools] Scraper does not handle session recreation > > > over same connection > > > DISPATCH-1208 - [tools] Scraper is slow with large number of links > > > DISPATCH-1209 - Add and enabling gate to control the > > > initialization of core modules > > > DISPATCH-1210 - [tools] Scraper could find and show unsettled > transfers > > > DISPATCH-1216 - [tools] Scraper should sort links by source/target > address > > > DISPATCH-1227 - Add a policy setting to allow or forbid dynamic > link routes > > > > > > Bug fixes - > > > DISPATCH-1146 - Core-endpoint can't receive deliveries on > > > core-initiated links > > > DISPATCH-1153 - Router crash when a detach arrives on a link that > > > is processing deliveries > > > DISPATCH-1163 - Coverity issues on master branch > > > DISPATCH-1164 - Failing to compile the router when only python3 is > installed > > > DISPATCH-1170 - System tests failing when executed on a python3 > only machine > > > DISPATCH-1171 - Interior router crash when edge receiver > disconnects > > > DISPATCH-1176 - Router crash when connected to network that has > > > > 400 edge routers > > > DISPATCH-1181 - handling MAU when local address is not yet defined > > > can result in wrong treatment > > > DISPATCH-1187 - Allow router to be configured to log in UTC time > > > DISPATCH-1189 - "log" configuration is missing "module" attribute > > > DISPATCH-1196 - Delivery reference count assertion can fail with > > > released multiframe messages > > > DISPATCH-1197 - Released multi-frame deliveries can cause stalling > > > of inbound links > > > DISPATCH-1198 - An early query of > > > 'org.apache.qpid.dispatch.router.node' can crash the router > > > DISPATCH-1212 - Incorrect "Dropped Presettled Count " in output of > > > qdstat -g when receiver drops off > > > DISPATCH-1213 - Sender link sending pre-settled multi-frame > > > deliveries can stall if receiver drops > > > DISPATCH-1218 - Assertion hit while running ctests > > > DISPATCH-1219 - [tools] Scraper fails to parse AMQP error with no > > > description > > > DISPATCH-1220 - Valgrid errors when running > system_tests_edge_router > > > DISPATCH-1221 - Syncing a new router to an existing network can > fail > > > DISPATCH-1222 - coverity static analysis reports several issues > > > DISPATCH-1223 - [tools] Scraper miscounts transfers with 'more' > > > set as unsettled > > > DISPATCH-1228 - qdstat -a fails with "KeyError: priority" against > > > 1.4 version of router > > > > > > Thanks > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > +1 > > > > I checked things over as follows: > > - Verified the signature and checksum files. > > - Checked for LICENCE and NOTICE files being present. > > - Ran "mvn apache-rat:check" to verify headers in the archive. > > - Ran the build (against Proton 0.26.0) and tests > > - Ran the Qpid JMS 0.40.0 RC1 HelloWorld example against the broker. > > > > Robbie > > I meant to cover this and somehow forgot. As I also mentioned on the > Broker-J 7.1.0 vote, I think it would be nicer to create the first > X.Y.0 RC from master, then only create a branch later if/when actually > needed for an X.Y.Z release (or a respin if master doesnt still suit > that). Branching first in this way means master ends up never having > any tags to help somewhat deliminate its activity later, and at least > at the time the version change commits were the only difference > between it and the branch. Commits must already be cherry picked to do > a 1.5.1 when that may not have yet been necessary for a period (or > possibly at all depending on the work+releases occurring later, e.g a > swift but minimal 1.5.1 from master then 1.6.0). > > > Starting next release, I will do what Robbie is suggesting above. Thanks. > > Robbie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
