On Sun, 28 May 2023 at 04:53, Michael Osipov wrote:
>
> Am 2023-05-27 um 12:10 schrieb Tamás Cservenák:
> > Howdy,
> >
> > I do agree with Lukasz here...but
> >
> > In general, my intention with bringing up this on Slack was motivated by
> > following reasons:
> > - we do have ML (signup needed),
You are correct, never used Polarion. Sounds like that might have been as bad
as PVCS compared to nearly all other SCM 😉
IMO simple is better when it comes to that stuff and linking tickets isn't that
hard. I've not done anything with gitlab but on GH its trivial, maybe not the
best but just
Am 2023-05-27 um 22:21 schrieb Jeremy Landis:
Not sure if was mentioned. Spring moved all their legacy Jira for all their
projects entirely to GitHub Issues. Believe it was done with everything.
https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues
Now con
Not sure if was mentioned. Spring moved all their legacy Jira for all their
projects entirely to GitHub Issues. Believe it was done with everything.
https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues
Now concerns of MS are unfounded thus far. MS is bigge
Am 2023-05-26 um 21:29 schrieb Michael Osipov:
Hi,
we solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12353222
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MPIR/issues
Staging repo:
https://repositor
Am 2023-05-27 um 12:10 schrieb Tamás Cservenák:
Howdy,
I do agree with Lukasz here...but
In general, my intention with bringing up this on Slack was motivated by
following reasons:
- we do have ML (signup needed),
- we do have JIRA (ask + approval + signup needed),
But all this is a high barri
+1
pt., 26 maj 2023, 21:29 użytkownik Michael Osipov
napisał:
> Hi,
>
> we solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12353222
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MPIR/issues
>
+1
Thanks!
El vie, 26 may 2023 a la(s) 16:29, Michael Osipov (micha...@apache.org)
escribió:
> Hi,
>
> we solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12353222
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.o
I am +1 to move to GH issues.
In Apache BookKeeper and Pulsar we had a script that did the migration
pretty seamlessly and I used that script also for other OSS projects
outside of the ASF. (I can't find it now, but it should be buried in some
git repo somewhere)
Enrico
Il Sab 27 Mag 2023, 13:02
> It occurs to me that not that long ago, Jira used to be open signup.
> is there a specific reason it changed? Does that reason still apply?
It's still open and self-serving at [1]. Just need one more moderate step
from committers or PMC members. To reduce spam, yes.
Best,
tison.
[1] https://se
So much spam got into jira, it had to be locked down. You should see the
junk I mod out of the Xalan lists...
Gary
On Sat, May 27, 2023, 06:55 Elliotte Rusty Harold
wrote:
> On Sat, May 27, 2023 at 6:11 AM Tamás Cservenák
> wrote:
>
> > In general, my intention with bringing up this on Slack w
How does StackOverflow fit in if at all? Any pros and cons to share?
Gary
On Sat, May 27, 2023, 06:43 tison wrote:
> > single point of entrance
>
> One last comment - it's a maintainer strategy to reduce the burden of
> monitoring multiple channels, and users generally gather to where their
> q
On Sat, May 27, 2023 at 6:11 AM Tamás Cservenák wrote:
> In general, my intention with bringing up this on Slack was motivated by
> following reasons:
> - we do have ML (signup needed),
> - we do have JIRA (ask + approval + signup needed),
>
Good points all around.
It occurs to me that not tha
> single point of entrance
One last comment - it's a maintainer strategy to reduce the burden of
monitoring multiple channels, and users generally gather to where their
questions can be answered. But it's not a user strategy; they ask on the
platform they are used to or closest to where the issue
I agree with Tamas' suggestion about the single point of entrance. Here are
several examples I experienced:
1. Apache SkyWalking[1] uses a single GH Issue to track all its issues and
Discussions for user questions and some rough ideas.
2. Apache Pulsar[2] (I'm one of its committers) uses multiple
As a Maven user experiencing finding issue tracker recently[1][2], here are
my two coins:
1. GitHub Issues help to get issues reported at the exact code repo.
I found a usage question for ASF parent pom and find the code repo at[3],
no GitHub Issues and I jump to the linked JIRA project MPOM, whi
Howdy,
I do agree with Lukasz here...but
In general, my intention with bringing up this on Slack was motivated by
following reasons:
- we do have ML (signup needed),
- we do have JIRA (ask + approval + signup needed),
But all this is a high barrier for "one off" users, many of our users want
to
I have no strong feelings, however relying too much on single service
vendor is never a good idea. In this case if one day, by some
terms&condition changes, github repos are not an option any more, we are
fine with ASF infrastructure. But we can't do same thing for issues
which are embedded in
Le vendredi 26 mai 2023, 19:41:53 CEST Benjamin Marwell a écrit :
> Big +1, as more and more projects are already migrating (including Apache
> Shiro).
>
> I'd vote for maven-jlink-plugin: Not many issues currently.
>
> > not having to create an issue if a PR exists first
>
> I'd at least make m
on testing GH issues migration from Jira: yes
cache-extension [1] looks like an interesting example, given it has a small
history with its Jira content
we also have mvnd which uses GH issues from the start: testing and making
clear practices on release and release notes could also be worked ther
20 matches
Mail list logo
