It was clear a release was coming at some point, however I think Tim's mail is more around that it was actually not clear precisely when it would, and so a notice would have been nice. If anything the mail thread made it less clear when it would arrive, given it had been coming for several weeks and the previous mail was 6 days before the one saying you had tagged it.
I have no issue with lack of heads up mail in general, especially when its well understood the point it will release (e.g JIRAs assigned being resolved) or releases are frequent enough it simply becomes much less important, but I also think it would have been good in this case given the several prior heads ups served to somewhat mislead. On 16 May 2018 at 17:32, Clebert Suconic <clebert.suco...@gmail.com> wrote: > I have been pushing this for a few weeks. I thought it was more than > clear. I didn’t mean to get anyone by surprise. > > Along the conversation here 2.5.1 will just be renamed as 2.6.0. > > > I’m traveling today and I wanted to tag and upload from home. And I wanted > something to do tonight at the hotel :). Sorry for any trouble. > > We can try another one shortly in a few weeks. (2 or 3) > > On Wed, May 16, 2018 at 11:53 AM Timothy Bish <tabish...@gmail.com> wrote: > >> On 05/16/2018 11:09 AM, Clebert Suconic wrote: >> > I just tagged as 2.6.0... It's uploading... >> > >> > I will cleanup JIRA tonight / tomorrow.. should send the voting thread >> > soon (tonight or tomorrow) >> >> This seems a bit backwards to me. I'd think in the future it'd be nice >> to send some notice before you spin the release to give folks some >> warning. The title of this thread still references a 2.5.1 release in a >> week which are both incorrect so anyone watching for it might miss the >> notice and anyone working on last minute fixes or whatnot gets no notice. >> >> It'd probably be a good idea to do the JIRA cleanup prior to all this as >> a way to better gauge where things stand before pulling the trigger and >> also give people some better insight into what is in the release when >> the vote thread appears. >> >> It probably wouldn't be as big a deal if releases were happening on a >> more frequent basis but given the long delay I'd say some warning next >> time would probably be the courteous thing to do. >> >> > On Thu, May 10, 2018 at 10:33 AM, Clebert Suconic >> > <clebert.suco...@gmail.com> wrote: >> >> I have been clearing the testsuite. Other guys are working with me on >> >> that (Francesco, Justin for instance). I'll do as soon as I'm done. >> >> >> >> On Thu, May 10, 2018 at 8:24 AM, Christopher Shannon >> >> <christopher.l.shan...@gmail.com> wrote: >> >>> +1 to make this a 2.6.0 release, there are now over 80 commits and >> >>> been enough time that I think a 2.6.0 makes more sense >> >>> >> >>> On Thu, May 3, 2018 at 12:09 PM, Clebert Suconic >> >>> <clebert.suco...@gmail.com> wrote: >> >>>> Meanwhile please set your fixes as 2.5.1... i will rename it as 2.6.0 >> >>>> before releasing as everything is already filtered there. >> >>>> >> >>>> On Thu, May 3, 2018 at 12:04 PM, Clebert Suconic >> >>>> <clebert.suco...@gmail.com> wrote: >> >>>>> From the entire set.. we only have fixes.. and 4 enhancements... >> >>>>> (previously existent features). >> >>>>> >> >>>>> I would prefer saving 2.6.0 for a more substantial release.. but if >> >>>>> you guys still prefer calling 2.6.0 I'm fine with that. >> >>>>> >> >>>>> On Thu, May 3, 2018 at 11:02 AM, Robbie Gemmell >> >>>>> <robbie.gemm...@gmail.com> wrote: >> >>>>>> I see there are some updates retargetting JIRA version at 2.5.1 from >> >>>>>> 2.6.0. I think the changes on master are now more suited to the >> >>>>>> release being versioned as 2.6.0. There are plenty of changes in the >> >>>>>> time since 2.5.0 that would have suited 2.5.x releases, but there >> >>>>>> seems to be enough others in there now that might better fit a 2.6.0 >> >>>>>> due to adding new functionality etc. >> >>>>>> >> >>>>>> Thoughts? >> >>>>>> >> >>>>>> Robbie >> >>>>>> >> >>>>>> On 26 April 2018 at 22:46, Clebert Suconic < >> clebert.suco...@gmail.com> wrote: >> >>>>>>> Little snafu today... I'm dealing with a failure in >> >>>>>>> >> org.apache.activemq.artemis.tests.integration.openwire.amq.RedeliveryPolicyTest.testRedeliveryPolicyPerDestination >> >>>>>>> >> >>>>>>> will send the vote soon. >> >>>>>>> >> >>>>>>> On Wed, Apr 25, 2018 at 9:24 PM, Clebert Suconic >> >>>>>>> <clebert.suco...@gmail.com> wrote: >> >>>>>>>> I will cut it tomorrow. I won’t merge anything until it’s out. >> >>>>>>>> >> >>>>>>>> @Commiters please don’t break Anything today :) >> >>>>>>>> >> >>>>>>>> @everyvody if there is anything you want Merged or committed >> tomorrow let me >> >>>>>>>> know. >> >>>>>>>> >> >>>>>>>> On Wed, Apr 25, 2018 at 4:41 PM pwjenkins >> >>>>>>>> <phillip.jenk...@entrustdatacard.com> wrote: >> >>>>>>>>> Are you on track to release by the end of April? >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>> -- >> >>>>>>>>> Sent from: >> >>>>>>>>> http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html >> >>>>>>>> -- >> >>>>>>>> Clebert Suconic >> >>>>>>> >> >>>>>>> >> >>>>>>> -- >> >>>>>>> Clebert Suconic >> >>>>> >> >>>>> >> >>>>> -- >> >>>>> Clebert Suconic >> >>>> >> >>>> >> >>>> -- >> >>>> Clebert Suconic >> >> >> >> >> >> -- >> >> Clebert Suconic >> > >> > >> >> -- >> Tim Bish >> twitter: @tabish121 >> blog: http://timbish.blogspot.com/ >> >> -- > Clebert Suconic
