[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2023-06-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402789 Bug 402789 depends on bug 422878, which changed state. Bug 422878 Summary: Change to work with GitLab issues https://bugs.kde.org/show_bug.cgi?id=422878 What|Removed |Added -

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2022-09-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402789 darkdragon-...@web.de changed: What|Removed |Added CC||darkdragon-...@web.de -- You are receiv

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2020-06-12 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=402789 Christophe Giboudeaux changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=399636

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2020-06-12 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 Claudius Ellsel changed: What|Removed |Added Depends on||422878 Referenced Bugs: https://bugs.kde.or

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2020-06-12 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 Claudius Ellsel changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2020-06-11 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #16 from Claudius Ellsel --- (In reply to Nicolás Alvarez from comment #14) > It's more than that, we can't get rid of bugzilla until we completely re-do > the crash reporting system. I did not find much about it on the internet, are you re

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2020-06-11 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #15 from Claudius Ellsel --- (In reply to Nate Graham from comment #13) > I hear you, Claudius. I don't like mailing lists either, and I agree that > Bugzilla is clunky and antiquated. I'm very much in favor of migrating > everything to GitL

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2020-06-10 Thread Nicolás Alvarez
https://bugs.kde.org/show_bug.cgi?id=402789 Nicolás Alvarez changed: What|Removed |Added CC||nicolas.alva...@gmail.com --- Comment #14 fro

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2020-06-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #13 from Nate Graham --- I hear you, Claudius. I don't like mailing lists either, and I agree that Bugzilla is clunky and antiquated. I'm very much in favor of migrating everything to GitLab issues. However our sysadmins are already at 100%

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2020-06-10 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #12 from Claudius Ellsel --- (In reply to Nate Graham from comment #10) > I remember being where you are right now, Claudius. You want to have an > impact on big things, but none of the channels of communication available to > you as a user

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2020-06-10 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #11 from Claudius Ellsel --- (In reply to Ben Cooksley from comment #9) > Having it open as a feature request wouldn't be correct either i'm afraid. > > Changes in community tooling is far outside of scope for Bugzilla - things > like this

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-19 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #10 from Nate Graham --- I remember being where you are right now, Claudius. You want to have an impact on big things, but none of the channels of communication available to you as a user seem adequate for this. The solution is to step up an

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-19 Thread Ben Cooksley
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #9 from Ben Cooksley --- Having it open as a feature request wouldn't be correct either i'm afraid. Changes in community tooling is far outside of scope for Bugzilla - things like this if not initiated directly by groups within KDE trying o

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-19 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #8 from Claudius Ellsel --- (In reply to Nate Graham from comment #7) > "RESOLVED NOT A BUG" is another way of saying, "This isn't something that's > appropriate to have in the bug tracker." > > It's simply not the right place to discuss wh

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #7 from Nate Graham --- "RESOLVED NOT A BUG" is another way of saying, "This isn't something that's appropriate to have in the bug tracker." It's simply not the right place to discuss whether or not we're going to move to replace Bugzilla w

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-16 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #6 from Claudius Ellsel --- Same applies to Resolved - not a bug (at least imho). I thought waitingforinfo was more accurate than this (although not fitting good). This is not resolved imho. -- You are receiving this mail because: You are

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-16 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=402789 Christophe Giboudeaux changed: What|Removed |Added Status|VERIFIED|RESOLVED Resolution|WAITINGFORI

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-16 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 Claudius Ellsel changed: What|Removed |Added URL||https://gitlab.com/gitlab-o

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-15 Thread Ben Cooksley
https://bugs.kde.org/show_bug.cgi?id=402789 Ben Cooksley changed: What|Removed |Added CC||bcooks...@kde.org --- Comment #3 from Ben Cooksl

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-15 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 --- Comment #2 from Claudius Ellsel --- Thanks for letting me know, nice to hear this is already in consideration :) Nonetheless, I think it should be tracked somewhere (preferably on KDE side), as the result of said evaluation is not clear. After sea

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-15 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402789 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-02 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=402789 Christophe Giboudeaux changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mai

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-02 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 Claudius Ellsel changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-02 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de -- You are receiving