I was actually just working on it. I was out a fair bit last week due to
Spring Break so that caused some delay. I'll get it together ASAP.


Justin

On Thu, Mar 28, 2024 at 2:09 PM Matt Pavlovich <mattr...@gmail.com> wrote:

> Hey Justin-
>
> Checking in.. have you had a chance to collect your findings?
>
> Thanks,
> Matt
>
> > On Mar 18, 2024, at 3:26 PM, Justin Bertram <jbert...@apache.org> wrote:
> >
> > I hope to present it later this week. Thanks for your patience!
> >
> >
> > Justin
> >
> > On Sun, Mar 17, 2024 at 6:16 PM Matt Pavlovich <mattr...@gmail.com>
> wrote:
> >
> >> Hi Justin-
> >>
> >> Sure, when do you plan to share your research?
> >>
> >> Thanks,
> >> Matt
> >>
> >>> On Mar 15, 2024, at 10:22 AM, Justin Bertram <jbert...@redhat.com>
> >> wrote:
> >>>
> >>> -1
> >>>
> >>> I don't think there's been sufficient discussion of the pros and cons
> to
> >>> make an informed decision. I've done some investigation and testing and
> >> I'd
> >>> like a chance to present my findings. This would be a fairly
> significant
> >>> change, and I think it deserves a more detailed review than we've had
> so
> >>> far.
> >>>
> >>> Also, I think migration should be considered for ActiveMQ as a whole
> and
> >>> not just a single component (i.e. Classic). Having multiple different
> >> ways
> >>> to complete the same task in the same project isn't going to be great
> for
> >>> users or contributors. If the change is good for one component then it
> >>> stands to reason that it would be good for all.
> >>>
> >>>
> >>> Justin
> >>>
> >>> On Fri, Mar 15, 2024 at 10:06 AM Matt Pavlovich <mattr...@gmail.com>
> >> wrote:
> >>>
> >>>> All-
> >>>>
> >>>> Kicking off a vote thread for migrating ActiveMQ Classic issues from
> >> JIRA
> >>>> to GitHub.
> >>>>
> >>>> This vote covers:
> >>>> - Migration of ActiveMQ Classic JIRA issues to GitHub
> >>>> - Update Apache ActiveMQ website with links to GitHub issues
> >>>>
> >>>> This vote will be open for at least 72 hours.
> >>>>
> >>>> Thank you,
> >>>> Matt Pavlovich
> >>>>
> >>>>
> >>
> >>
>
>

Reply via email to