Hey Justin, yeah that makes sense to me. Thanks, Ken
On Thu, Nov 20, 2025 at 10:36 AM Justin Bertram <[email protected]> wrote: > As far as I'm aware, you can't simply remove "classic" from " > https://hub.docker.com/r/apache/activemq-classic"; or "activemq" from " > https://hub.docker.com/r/apache/activemq-artemis"; as that would break > anybody currently using them. Instead we should: > > - create new locations for both ActiveMQ and Artemis > - update the documentation on the old location to point to the new > location > - publish new tags to both places for a time while folks transition > - cease publishing new tags to the old location > - wait an additional period of time before removing any tags or > potentially just leave them > > > Justin > > On Thu, Nov 20, 2025 at 12:25 PM Ken Liao <[email protected]> wrote: > > > Thanks JB, since I have been looking at Helm chart and K8s, I would like > to > > call out that we should also change the following Docker repositories: > > > > Artemis: https://hub.docker.com/r/apache/activemq-artemis <- remove > > "activemq" > > ActiveMQ: https://hub.docker.com/r/apache/activemq-classic <- remove > > "classic" > > > > Thanks, > > Ken > > > > On Thu, Nov 20, 2025 at 9:44 AM Robbie Gemmell <[email protected] > > > > wrote: > > > > > Repo change applied > > > > > > On Thu, 20 Nov 2025 at 17:08, Robbie Gemmell <[email protected] > > > > > wrote: > > > > > > > > Jira description updated, and > > > > https://github.com/apache/activemq/pull/1545 raised for review. > > > > > > > > On Thu, 20 Nov 2025 at 17:00, Robbie Gemmell < > [email protected] > > > > > > wrote: > > > > > > > > > > Those elements are self-serve, no need to bother asking Infra > > > > > anything, we can just edit the project description in Jira and > update > > > > > the repo description in the .asf.yaml file (I'll do both now, if > you > > > > > what to close your Jira) > > > > > > > > > > On Thu, 20 Nov 2025 at 16:22, Matt Pavlovich <[email protected]> > > > wrote: > > > > > > > > > > > > Hi JB- > > > > > > > > > > > > I think a new static website generation with modern them is a > great > > > idea. I think we should prioritize that, since any new docs, etc can > all > > > reference the new layout (we should maintain a healthy set of static > > > redirects b/c of the legacy pages already indexed by search engines). > > > > > > > > > > > > I created an INFRA ticket for the JIRA and GitHub rename of > > > ‘ActiveMQ Classic’ to simply ‘ActiveMQ’ per the resolution: > > > > > > https://issues.apache.org/jira/browse/INFRA-27427 > > > > > > > > > > > > Thanks, > > > > > > Matt > > > > > > > > > > > > > On Nov 20, 2025, at 10:13 AM, Jean-Baptiste Onofré < > > > [email protected]> wrote: > > > > > > > > > > > > > > Hi folks, > > > > > > > > > > > > > > Now that we have two Top-Level Projects (ActiveMQ and > Artemis), I > > > > > > > would like to propose the following action plan across five key > > > areas > > > > > > > for discussion: > > > > > > > > > > > > > > 1. Website > > > > > > > I propose two immediate actions regarding the ActiveMQ website: > > > > > > > a. We should quickly remove the term "Classic" from the project > > > name > > > > > > > and all mentions across the website. > > > > > > > b. I propose an important refactoring of the website structure, > > > > > > > leveraging a modern static site generator such as Antora, > > > Docusaurus, > > > > > > > or Hugo (see Point 2 for related details). > > > > > > > > > > > > > > 2. Documentation > > > > > > > We have a significant amount of work ahead to ensure the > > > documentation > > > > > > > content is current and complete. To facilitate this, I propose > > > > > > > adopting a framework like Hugo to manage documentation across > > > multiple > > > > > > > versions effectively. > > > > > > > > > > > > > > 3. GitHub Issues > > > > > > > I plan to restart the discussion regarding migrating our issue > > > > > > > tracking from Jira to GitHub Issues. This will be initiated in > a > > > > > > > separate thread. > > > > > > > > > > > > > > 4. GitHub Actions (CI) > > > > > > > I have started implementing GitHub Actions for our Continuous > > > > > > > Integration (CI) process (as demonstrated in > > > > > > > https://github.com/apache/activemq/pull/1497 > > > > > > > (https://github.com/apache/activemq/pull/1497)). This setup > will > > > also > > > > > > > allow us to manage dependency updates automatically via > > Dependabot. > > > > > > > > > > > > > > 5. Automated Release/ATR > > > > > > > Building upon the work in Point 4, we will be able to > transition > > > > > > > toward Automatic Release CI/ATR. This topic will also be > > discussed > > > in > > > > > > > a separate, dedicated thread. > > > > > > > > > > > > > > I will initiate separate threads for each of these points to > > allow > > > for > > > > > > > focused discussion. Additionally, I would like to make a call > for > > > > > > > contributions for anyone interested in helping with these > > important > > > > > > > topics. > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > Regards, > > > > > > > JB > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > > For additional commands, e-mail: [email protected] > > > > > > > For further information, visit: > > > https://activemq.apache.org/contact > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > For further information, visit: https://activemq.apache.org/contact > > > > > > > > > > > >
