> On Apr 14, 2021, at 12:48 PM, Arjun Ray <[email protected]> wrote: > > On Wed, 14 Apr 2021 12:05:22 -0500, you wrote: > > | I知 in favor of updated the CMS to a more current C++, given the > | sustained interest in C++ and ActiveMQ. > > In-project interest seems to have shifted to Artemis (and AMQP), > making Classic a step-child within its own project.
ActiveMQ has a well established user base and significant continued investment by developers and end-users. I anticipate an updated CMS library would be very useful to many ActiveMQ users for years to come. > | Generally, forking isn稚 great for anyone in the long term. > > I agree. But what choices remain when "Won't fix" wihout explanation > is the gatekeepers' response to an obvious improvement? > > | Perhaps its best suited for a v4.x release and baseline against > | newer C++ libs? > > This sounds like a good idea. What is the procedure for this? 1. Create a clone of this git repo activemq-cpp <https://github.com/apache/activemq-cpp> 2. Create a branch (using the JIRA name is good ie AMQCPP-664) 3. Make the code changes 4. Push the branch to your cloned repo. 5. GitHub will prompt you to create a Pull Request (PR) since it detects your repo is a clone of the upstream. 6. PR can now be reviewed and merged by others. A brief guide here: https://activemq.apache.org/contributing <https://activemq.apache.org/contributing> Thanks! Matt Pavlovich
