The 'track version as Project' thing is interesting, though kinda
further underscores the limitations of Milestones which are really the
main surfaced way of handling versions.
I'll bet some folks on the 'users' side of things looking at released
issues later would even miss that you are doing
I would prefer to keep JIRA for their REST interface.
Also: one thing to notice is the possibility of using private comments
in JIRA. Say you ever have a security issue. I think you can have PMC
private comments on JIRAs. I'm not sure you have the same in github
issues.
I didn't see a note
Hi folks,
this vote passed with the following result:
+1 (binding): Christopher Shannon, JB Onofré, Matt Pavlovich, Clebert Suconic
+1 (non binding): Jamie Goodyear, François Papon, Cesar Hernandez
I'm promoting the artifacts on Maven Central and dist, then, I will
update the website and Jira.
On the lack of Issues tab, though it doesnt seem to have been too much
of an issue so far, we could certainly improve that by ensuring each
repo README always covers how to raise things (or just links to the
website page that covers it; I think some repos already do). Plus,
opening Discussions
Hi Clebert-
How widely used are private comments today?
I ran a search and I do not see any private comments in use with the ActiveMQ
project. I tried searching the ARTEMIS project, perhaps I got the JQL incorrect?
project = ARTEMIS AND issueFunction in commented("group activemq-pmc”)
project
I don't have a strong opinion on migrating from Jira to GitHub Issues.
I would prefer GitHub Issues only for its better integration and because
new users that reach from the GitHub repository could be confused to not
find the `Issues` tabs (most of the GitHub projects use it).
Also GitHub Issues
Is there a private comment capability on GitHub? To me that’s a breaking
deal feature and I have never seen it.
On Fri, Apr 5, 2024 at 12:15 PM Domenico Francesco Bruscino <
bruscin...@gmail.com> wrote:
> I don't have a strong opinion on migrating from Jira to GitHub Issues.
> I would prefer
The ActiveMQ team is pleased to announce Apache ActiveMQ 6.1.1 release.
It's a maintenance release on the ActiveMQ 6.1.x series, bringing:
- add firstMessageTimestamp in the StatisticsPlugin
- fix on Docker images authentication
- add sun.nio.* opens classes required for some transports
-
Whilst Jira can certainly do that, I dont believe we have ever used it
in that fashion here, and so I dont see that it could be considered a
break either way. Also, the process of e.g privately reporting
security issues wouldnt change in any event, it would remain as it is
now (and is detailed on
Hi,
Thanks again Justin for the detailed doc, that's a great one !
I understand the gaps you identified and agree with your points.
Regarding the comments and feedback, I think we don't have a strong
enough consensus for this move.
So I would propose to stay with Jira for now.
Thoughts ?
I haven’t used it on the Apache Jira but I use private comments all the
time on my company JIRA for things that would be related to security and
injeritently private.
I thought we could eventually start using a feature like that and I thought
it would be a nice feature to keep. But if everybody
11 matches
Mail list logo
