Re: GitHub Issues & Discussions enabled

--000000000000ae5235064b3146b0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi JB,

What about the satellite projects like nms, nms-amqp and nms-openwire?

What should we use there?

Best,
KP

On Thu, Feb 19, 2026 at 6:37=E2=80=AFPM Jean-Baptiste Onofr=C3=A9 <jb@nanth=
rax.net>
wrote:

> By the way, just to clarify about the conventional commit message, it's a
> suggestion, you are free to use it or not :)
>
> Personally, I will force myself to do use it (to force myself to think
> about the kind of changes I'm doing).
>
> Regards
> JB
>
> On Thu, Feb 19, 2026 at 6:19=E2=80=AFPM Jean-Louis Monteiro <
> jlmonteiro-6Zl4/RV5/[email protected]> wrote:
>
> > That looks great JB. Thanks for pushing on it.
> > I'm sure we'll learn and adjust as we go along.
> >
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Thu, Feb 19, 2026 at 5:52=E2=80=AFPM Matt Pavlovich <mattrpav@apache=
.org>
> > wrote:
> >
> > > Thanks for all your efforts on this! It would be good to add a md fil=
e
> > > with all this info and link it from the webpage and main README.md
> > >
> > > A couple of follow-ons:
> > >
> > > 1. I=E2=80=99m playing around with Milestones as a way to track long =
running
> > > feature groups across version releases =E2=80=94 ie JMS 3.0/2.1
> > >
> > > 2. Project names need to be fully qualified =E2=80=98Apache ActiveMQ =
v6.3.0=E2=80=99 =E2=80=94
> > > this allows for better visibility across orgs and repos.
> > >
> > > 3. Projects allow us to link issues in dependencies in other orgs/rep=
os
> > > that fix things that we find or are related to a release for easier
> > > discovery by end-users.
> > >
> > > More to come!
> > >
> > > Thanks,
> > > Matt Pavlovich
> > >
> > > > On Feb 19, 2026, at 10:41=E2=80=AFAM, Jean-Baptiste Onofr=C3=A9 <jb=
@nanthrax.net>
> > > wrote:
> > > >
> > > > Hi folks,
> > > >
> > > > We are pleased to announce that GitHub Issues & Discussions.
> > > >
> > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > Jira is now read-only and we should now all use GitHub Issues.
> > > >
> > > > We have the following labels available:
> > > > - bug: for bug reports
> > > > - dependencies: for dependencies updates
> > > > - enhancement: for improvements on existing code
> > > > - feature: for a complete new features
> > > > - proposal: for a design proposal, big features
> > > > - stale: when the issue is "inactive" for more than 60 days
> > > >
> > > > Please use these labels to classify the issues.
> > > >
> > > > When you create a PR, you can associate it with an issue either in
> the
> > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > I also suggest using conventional commit messages in PR with the
> > > > format <type>(<scope>): <subject> where scope is optional. The type
> can
> > > be:
> > > > - feat: (a new feature is introduced with the changes)
> > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > - docs: (changes to the documentation)
> > > > - style: (formatting, missing semicolons, etc; no production code
> > change)
> > > > - refactor: (refactoring production code, eg. renaming a variable)
> > > > - test: (adding missing tests, refactoring tests; no production cod=
e
> > > change)
> > > > - chore: (changes that do not relate to a fix or feature and don't
> > modify
> > > > src or test files (for example updating dependencies or change in
> > > > production code))
> > > > - perf =E2=80=93 (performance improvements)
> > > > - ci =E2=80=93 (continuous integration related)
> > > > - build =E2=80=93 (changes that affect the build system or external
> > dependencies)
> > > > - revert =E2=80=93 (reverts a previous commit)
> > > > That's a nice practice because GitHub can use that to create nice
> > Release
> > > > Notes.
> > > > Thanks to that, it's not necessary to create GH issues for all
> changes.
> > > >
> > > > For versions, we are using GitHub Projects (
> > > > https://github.com/apache/activemq/projects?query=3Dis%3Aopen).
> > > > You can assign several projects/versions per issue, and track the
> > status
> > > of
> > > > the versions.
> > > >
> > > > 2. GitHub Discussions
> > > > We also enabled GitHub Discussions where we can have technical
> > > discussions.
> > > > The GH Discussions are automatically going to the dev@ mailing list=
.
> > > >
> > > > Let us know if you have any questions.
> > > >
> > > > Regards
> > > > JB
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe-UzBZ5Px8zVWY1pf4d8vP8EB+6BGkLq7r@public.gmane.org
> > > For additional commands, e-mail: [email protected]
> > > For further information, visit: https://activemq.apache.org/contact
> > >
> > >
> > >
> >
>

--000000000000ae5235064b3146b0--