For me, this is certainly the best option. There can/will be other releases, and other fixes are likely to be needed as well.
On 8 August 2018 at 11:27, Christopher Shannon <christopher.l.shan...@gmail.com> wrote: > The other option (which I think is better now that I think about it) is > since I can't re-run a new vote anyways for 2 weeks is to just let this > vote go and then do another release in the next month. It's the same work > and at least the people who have been waiting for fixes in this release > will get them this week. > > On Wed, Aug 8, 2018 at 6:25 AM Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > >> I can cancel the vote if you want but I won't be able to re-run a new vote >> for 10 days to 2 weeks. I'm out of the office next week so if I start a >> new vote today then 72 hours won't have passed before I'm gone on vacation >> so I won't be able to finish up the rest of the release stuff. >> >> On Tue, Aug 7, 2018 at 5:43 PM Arthur Naseef <a...@amlinv.com> wrote: >> >>> Can we get this commit added to the release? It's currently on the master >>> branch. >>> >>> d8c80a98212ee5d73a281483a2f8b3f517465f62 >>> >>> Please let me know what else needs to be done to get it into the release. >>> >>> Art >>> >>> >>> On Tue, Aug 7, 2018 at 2:39 PM, Arthur Naseef <a...@amlinv.com> wrote: >>> >>> > I found that one issue was not fully fixed. Working on a fix for it >>> now. >>> > >>> > Sorry I didn't find this earlier - keep forgetting I can't test this >>> with >>> > Chrome. >>> > >>> > https://issues.apache.org/jira/browse/AMQ-6954 >>> > >>> > Art >>> > >>> > >>> > On Mon, Aug 6, 2018 at 5:33 PM, jgenender <jgenen...@apache.org> wrote: >>> > >>> >> +1 >>> >> >>> >> Jeff >>> >> >>> >> >>> >> >>> >> -- >>> >> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404 >>> . >>> >> html >>> >> >>> > >>> > >>> >>
