Re: [VOTE] Apache ActiveMQ Artemis 2.9.0

2019-05-31 Thread Timothy Bish
On 5/30/19 2:39 PM, Justin Bertram wrote: I would like to propose an Apache ActiveMQ Artemis 2.9.0 release. This is one of the smallest releases we've done. It includes a handful of bug fixes, a few improvements, and one major new feature: [ARTEMIS-2308] - Support exporting metrics The rele

Re: [DISCUSS] Component/Plugin repository

2019-05-31 Thread Clebert Suconic
On Fri, May 31, 2019 at 2:42 PM Robbie Gemmell wrote: > > I probably would do one each, yes. Its the easiest separation, keeps > things independent and focused from the start and can avoid various > hassles later. > > I'd perhaps consider 'all stuff' aggregation (e.g foo = > metrics), but really

Re: [DISCUSS] Component/Plugin repository

2019-05-31 Thread Robbie Gemmell
I probably would do one each, yes. Its the easiest separation, keeps things independent and focused from the start and can avoid various hassles later. I'd perhaps consider 'all stuff' aggregation (e.g foo = metrics), but really I dont personally see the benefits as outweighing the other things a

Re: [VOTE] Apache ActiveMQ Artemis 2.9.0

2019-05-31 Thread Christopher Shannon
+1, having a vendor neutral approach for exporting metrics using micrometer is a nice feature On Thu, May 30, 2019 at 11:02 PM Howard Gao wrote: > +1 > > > On Fri, May 31, 2019 at 3:26 AM Clebert Suconic > > wrote: > > > +1 [binding] > > > > On Thu, May 30, 2019 at 2:39 PM Justin Bertram > > w

Re: Artemis past releases page breakages

2019-05-31 Thread Clebert Suconic
Please accept my apologies... I have been on so many channels all at once that I overlooked into this. it would be nice to make this simpler though. I have tried to get rid of the documentation per previous version for instance (you can just download the documentation with the zip). On Fri, May 3

Re: [DISCUSS] Component/Plugin repository

2019-05-31 Thread Clebert Suconic
I agree with you, and that was my preference as well. I was trying to understand if one git per component is what Robbie was suggesting. Although there's an issue though, when you have one super git for many independent components, how would you tag releases? each fodler would be in fact an indep

Re: [DISCUSS] Component/Plugin repository

2019-05-31 Thread michael . andre . pearce
I think one git repo per thing maybecome a bit too scattery. Id go for one repo with multiple modules. Get Outlook for Android On Thu, May 30, 2019 at 7:42 PM +0100, "Clebert Suconic" wrote: On Thu, May 30, 2019 at 12:25 PM Robbie Gemmell wrote: > > I would put them outwith

Re: Artemis past releases page breakages

2019-05-31 Thread Robbie Gemmell
Yes it is, I even noted I found it was already documented when I went to add one of the times I was reporting the issue. https://github.com/apache/activemq-artemis/blame/2.8.1/RELEASING.md#L299 (The details are a touch stale now in referring to html of the old site update process) On Fri, 31 May

Re: Artemis past releases page breakages

2019-05-31 Thread Gary Tully
is that step in: https://github.com/apache/activemq-artemis/blob/master/RELEASING.md On Thu, 30 May 2019 at 12:29, Robbie Gemmell wrote: > > I've found that the docs/downloads/etc links for recent releases on > the past releases page are broken nearly every time I have used the > page over the l