The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions.
Thanks, Florian
On Wed, Aug 23, 2023 at 6:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
To get ahead of this, the move to the RHEL project on issues.redhat.com is not specific to Platform Tools. The entire RHEL product will be migrating there soon.
We will update the bug reporting and contributor guides shortly, but Florian's advice below is correct.
josh
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions.
Thanks, Florian
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Aug 23, 2023 at 6:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
The Red Hat Jira CS project currently blocks community members from filing issues or making comments.
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
I don't know this personally, since my account is old and originates from the JBoss JIRA instance, but I've been told that you are required now to disclose address and phone number and agree to the RHEA TOS to access the Jira when you create your account. It would be worth double-checking this.
The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions.
Please fix this and don't make accounts go automatically inactive. That's annoying and painful.
-- 真実はいつも一つ！/ Always, there's only one truth!
On Wed, Aug 23, 2023 at 8:46 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 6:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
The Red Hat Jira CS project currently blocks community members from filing issues or making comments.
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
I don't know this personally, since my account is old and originates from the JBoss JIRA instance, but I've been told that you are required now to disclose address and phone number and agree to the RHEA TOS to access the Jira when you create your account. It would be worth double-checking this.
The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions.
Please fix this and don't make accounts go automatically inactive. That's annoying and painful.
To my understanding, this will not be changed. Inactive accounts are culled to reduce seat license counts. I believe the cutoff is 90-days. While I agree it's a change in behavior and somewhat annoying, logging into the instance once a quarter does not seem onerous for someone that wants to actively participate.
josh
On Wed, Aug 23, 2023 at 9:28 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 23, 2023 at 8:46 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 6:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
The Red Hat Jira CS project currently blocks community members from filing issues or making comments.
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
I don't know this personally, since my account is old and originates from the JBoss JIRA instance, but I've been told that you are required now to disclose address and phone number and agree to the RHEA TOS to access the Jira when you create your account. It would be worth double-checking this.
The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions.
Please fix this and don't make accounts go automatically inactive. That's annoying and painful.
To my understanding, this will not be changed. Inactive accounts are culled to reduce seat license counts. I believe the cutoff is 90-days. While I agree it's a change in behavior and somewhat annoying, logging into the instance once a quarter does not seem onerous for someone that wants to actively participate.
It is onerous for people who use CentOS Stream and file bug reports waiting for responses given the current lag times. BZes already don't get responses for weeks or months in some cases. Even as an active participant (if you'd like to count me as one), most of *my* BZes get nothing for months. I have no reason to regularly check Jira for my issues because there's nothing going on anyway.
It's not "somewhat annoying", it's actually really bad. If you really need to worry about seat counts, then adjust the inactivity period to align with how long it takes for someone to respond to a ticket. Probably one to two years is more appropriate.
I do not think it is reasonable to disable volunteer user/contributor accounts like this, especially since it disables your watch lists in Jira.
-- 真実はいつも一つ！/ Always, there's only one truth!
On Wed, Aug 23, 2023 at 9:39 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 9:28 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 23, 2023 at 8:46 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 6:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
The Red Hat Jira CS project currently blocks community members from filing issues or making comments.
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
I don't know this personally, since my account is old and originates from the JBoss JIRA instance, but I've been told that you are required now to disclose address and phone number and agree to the RHEA TOS to access the Jira when you create your account. It would be worth double-checking this.
The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions.
Please fix this and don't make accounts go automatically inactive. That's annoying and painful.
To my understanding, this will not be changed. Inactive accounts are culled to reduce seat license counts. I believe the cutoff is 90-days. While I agree it's a change in behavior and somewhat annoying, logging into the instance once a quarter does not seem onerous for someone that wants to actively participate.
It is onerous for people who use CentOS Stream and file bug reports waiting for responses given the current lag times. BZes already don't get responses for weeks or months in some cases. Even as an active participant (if you'd like to count me as one), most of *my* BZes get nothing for months. I have no reason to regularly check Jira for my issues because there's nothing going on anyway.
It's not "somewhat annoying", it's actually really bad. If you really need to worry about seat counts, then adjust the inactivity period to align with how long it takes for someone to respond to a ticket. Probably one to two years is more appropriate.
I do not think it is reasonable to disable volunteer user/contributor accounts like this, especially since it disables your watch lists in Jira.
OK. I will state this more clearly.
You asked to change this. I inquired if it could be changed internally. The answer is no, it cannot.
I'm not trying to justify or argue the merits of the existing mechanism. I am trying to set clear expectations so people are aware of the way it works and can plan accordingly.
josh
On Wed, Aug 23, 2023 at 9:42 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 23, 2023 at 9:39 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 9:28 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 23, 2023 at 8:46 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 6:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
The Red Hat Jira CS project currently blocks community members from filing issues or making comments.
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
I don't know this personally, since my account is old and originates from the JBoss JIRA instance, but I've been told that you are required now to disclose address and phone number and agree to the RHEA TOS to access the Jira when you create your account. It would be worth double-checking this.
The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions.
Please fix this and don't make accounts go automatically inactive. That's annoying and painful.
To my understanding, this will not be changed. Inactive accounts are culled to reduce seat license counts. I believe the cutoff is 90-days. While I agree it's a change in behavior and somewhat annoying, logging into the instance once a quarter does not seem onerous for someone that wants to actively participate.
It is onerous for people who use CentOS Stream and file bug reports waiting for responses given the current lag times. BZes already don't get responses for weeks or months in some cases. Even as an active participant (if you'd like to count me as one), most of *my* BZes get nothing for months. I have no reason to regularly check Jira for my issues because there's nothing going on anyway.
It's not "somewhat annoying", it's actually really bad. If you really need to worry about seat counts, then adjust the inactivity period to align with how long it takes for someone to respond to a ticket. Probably one to two years is more appropriate.
I do not think it is reasonable to disable volunteer user/contributor accounts like this, especially since it disables your watch lists in Jira.
OK. I will state this more clearly.
You asked to change this. I inquired if it could be changed internally. The answer is no, it cannot.
I'm not trying to justify or argue the merits of the existing mechanism. I am trying to set clear expectations so people are aware of the way it works and can plan accordingly.
I am not refuting your base premise that you cannot deactivate accounts after a period of time. I am, however, telling you *why* this is onerous as you seem to believe it is not. If you intend to use metrics for determining participation, then you're going to have problems because of the issues I stated. I even offered a suggestion of a more reasonable timeline for deactivation based on the current lag times.
Unless something changes on your side, this is going to be a downgrade overall from an engagement and usability perspective for contributors.
-- 真実はいつも一つ！/ Always, there's only one truth!
On Wed, Aug 23, 2023 at 9:54 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 9:42 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 23, 2023 at 9:39 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 9:28 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 23, 2023 at 8:46 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 6:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
The Red Hat Jira CS project currently blocks community members from filing issues or making comments.
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
I don't know this personally, since my account is old and originates from the JBoss JIRA instance, but I've been told that you are required now to disclose address and phone number and agree to the RHEA TOS to access the Jira when you create your account. It would be worth double-checking this.
The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions.
Please fix this and don't make accounts go automatically inactive. That's annoying and painful.
To my understanding, this will not be changed. Inactive accounts are culled to reduce seat license counts. I believe the cutoff is 90-days. While I agree it's a change in behavior and somewhat annoying, logging into the instance once a quarter does not seem onerous for someone that wants to actively participate.
It is onerous for people who use CentOS Stream and file bug reports waiting for responses given the current lag times. BZes already don't get responses for weeks or months in some cases. Even as an active participant (if you'd like to count me as one), most of *my* BZes get nothing for months. I have no reason to regularly check Jira for my issues because there's nothing going on anyway.
It's not "somewhat annoying", it's actually really bad. If you really need to worry about seat counts, then adjust the inactivity period to align with how long it takes for someone to respond to a ticket. Probably one to two years is more appropriate.
I do not think it is reasonable to disable volunteer user/contributor accounts like this, especially since it disables your watch lists in Jira.
OK. I will state this more clearly.
You asked to change this. I inquired if it could be changed internally. The answer is no, it cannot.
I'm not trying to justify or argue the merits of the existing mechanism. I am trying to set clear expectations so people are aware of the way it works and can plan accordingly.
I am not refuting your base premise that you cannot deactivate accounts after a period of time. I am, however, telling you *why* this is onerous as you seem to believe it is not. If you intend to use
My personal tolerance for inconvenience has no bearing on the ability to enact a change.
metrics for determining participation, then you're going to have problems because of the issues I stated. I even offered a suggestion of a more reasonable timeline for deactivation based on the current lag times.
Unless something changes on your side, this is going to be a downgrade overall from an engagement and usability perspective for contributors.
Noted. I'm not sure what else you'd like me to do at this point, so we should probably stop furthering this subthread.
josh
On Wed, Aug 23, 2023, at 9:38 AM, Neal Gompa wrote:
It's not "somewhat annoying", it's actually really bad. If you really need to worry about seat counts, then adjust the inactivity period to align with how long it takes for someone to respond to a ticket. Probably one to two years is more appropriate.
For the record I agree with you, Neal. I also have no power to change things on the JIRA side, but what I think we *do* have the power to change is to enable issues on gitlab.com for example. Then it probably wouldn't be too hard to add some automation that can sync between the two - automatically reflect comments made on gitlab to JIRA for example.
Many of the projects I work on we work primarily in terms of Github issues, and there's already some automation to auto-generate a JIRA issue for a Github issue - leaving the GH issue as the "source of truth".
On Wed, 2023-08-23 at 09:28 -0400, Josh Boyer wrote:
On Wed, Aug 23, 2023 at 8:46 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 6:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
The Red Hat Jira CS project currently blocks community members from filing issues or making comments.
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
I don't know this personally, since my account is old and originates from the JBoss JIRA instance, but I've been told that you are required now to disclose address and phone number and agree to the RHEA TOS to access the Jira when you create your account. It would be worth double-checking this.
The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions.
Please fix this and don't make accounts go automatically inactive. That's annoying and painful.
To my understanding, this will not be changed. Inactive accounts are culled to reduce seat license counts. I believe the cutoff is 90-days. While I agree it's a change in behavior and somewhat annoying, logging into the instance once a quarter does not seem onerous for someone that wants to actively participate.
josh
Will it send out a notification that an account is going to be disabled or do I need to add a calendar event to make sure I log in often enough?
Pat
On Wed, Aug 23, 2023 at 8:25 AM Patrick Riehecky via CentOS-devel < centos-devel@centos.org> wrote:
Will it send out a notification that an account is going to be disabled or do I need to add a calendar event to make sure I log in often enough?
BTW, I'm checking on this and will report back. It seems like the polite thing to do.
On Wed, Aug 23, 2023 at 3:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
I am trying this with my personal account. If I go to projects and search for CentOS, I ONLY get "CS", and it's not called CS it's called "CentOS Stream". The only indication I get that it is "CentOS Stream (CS)" is when I look at the Key.
Please, let us know how to REALLY get to your project on Jira. Otherwise I think the CentOS Stream team (The team that creates the compose) will be getting alot of your tickets/issues.
On Wed, Aug 23, 2023 at 9:27 AM Troy Dawson tdawson@redhat.com wrote:
On Wed, Aug 23, 2023 at 3:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
I am trying this with my personal account. If I go to projects and search for CentOS, I ONLY get "CS", and it's not called CS it's called "CentOS Stream". The only indication I get that it is "CentOS Stream (CS)" is when I look at the Key.
Please, let us know how to REALLY get to your project on Jira.
https://github.com/CentOS/docs-contributors-guide/pull/19
https://issues.redhat.com/projects/RHEL
josh
On Wed, Aug 23, 2023 at 6:29 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 23, 2023 at 9:27 AM Troy Dawson tdawson@redhat.com wrote:
On Wed, Aug 23, 2023 at 3:51 AM Florian Weimer fweimer@redhat.com
wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
I am trying this with my personal account. If I go to projects and search for CentOS, I ONLY get "CS", and it's not
called CS it's called "CentOS Stream".
The only indication I get that it is "CentOS Stream (CS)" is when I look
at the Key.
Please, let us know how to REALLY get to your project on Jira.
So, we don't search for "CentOS Stream" we are supposed to search for "RHEL"?
I'm sorry, I'm not meaning to be a pain. This is the first group that has moved things from bugzilla to Jira, and thus the first instructions. I'm trying to look at this from someone who logs into Jira for the first time, with no bookmarks and/or pre-defined looks.
If I want to create a bug (or defect), or search for a defect on binutils, how do I do it? What Fabian said above, does not work for someone new to Jira.
On Wed, Aug 23, 2023 at 6:42 AM Troy Dawson tdawson@redhat.com wrote:
On Wed, Aug 23, 2023 at 6:29 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 23, 2023 at 9:27 AM Troy Dawson tdawson@redhat.com wrote:
On Wed, Aug 23, 2023 at 3:51 AM Florian Weimer fweimer@redhat.com
wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb,
glibc,
systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called
“RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and
select
“CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
I am trying this with my personal account. If I go to projects and search for CentOS, I ONLY get "CS", and it's
not called CS it's called "CentOS Stream".
The only indication I get that it is "CentOS Stream (CS)" is when I
look at the Key.
Please, let us know how to REALLY get to your project on Jira.
So, we don't search for "CentOS Stream" we are supposed to search for "RHEL"?
I'm sorry, I'm not meaning to be a pain. This is the first group that has moved things from bugzilla to Jira, and thus the first instructions. I'm trying to look at this from someone who logs into Jira for the first time, with no bookmarks and/or pre-defined looks.
If I want to create a bug (or defect), or search for a defect on binutils, how do I do it? What Fabian said above, does not work for someone new to Jira.
Now that I re-read the pull request, I see that the answer is in there. I have gone through the steps, and it indeed makes sense.
I think a screenshot or two might be beneficial, but it works.
Troy
On Wed, Aug 23, 2023 at 10:23 AM Troy Dawson tdawson@redhat.com wrote:
On Wed, Aug 23, 2023 at 6:42 AM Troy Dawson tdawson@redhat.com wrote:
On Wed, Aug 23, 2023 at 6:29 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 23, 2023 at 9:27 AM Troy Dawson tdawson@redhat.com wrote:
On Wed, Aug 23, 2023 at 3:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
I am trying this with my personal account. If I go to projects and search for CentOS, I ONLY get "CS", and it's not called CS it's called "CentOS Stream". The only indication I get that it is "CentOS Stream (CS)" is when I look at the Key.
Please, let us know how to REALLY get to your project on Jira.
So, we don't search for "CentOS Stream" we are supposed to search for "RHEL"?
I'm sorry, I'm not meaning to be a pain. This is the first group that has moved things from bugzilla to Jira, and thus the first instructions. I'm trying to look at this from someone who logs into Jira for the first time, with no bookmarks and/or pre-defined looks.
If I want to create a bug (or defect), or search for a defect on binutils, how do I do it? What Fabian said above, does not work for someone new to Jira.
Now that I re-read the pull request, I see that the answer is in there. I have gone through the steps, and it indeed makes sense.
Our emails crossed in flight :) I'm glad it makes sense!
I think a screenshot or two might be beneficial, but it works.
I agree.
josh
On Wed, Aug 23, 2023 at 9:42 AM Troy Dawson tdawson@redhat.com wrote:
On Wed, Aug 23, 2023 at 6:29 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 23, 2023 at 9:27 AM Troy Dawson tdawson@redhat.com wrote:
On Wed, Aug 23, 2023 at 3:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
I am trying this with my personal account. If I go to projects and search for CentOS, I ONLY get "CS", and it's not called CS it's called "CentOS Stream". The only indication I get that it is "CentOS Stream (CS)" is when I look at the Key.
Please, let us know how to REALLY get to your project on Jira.
So, we don't search for "CentOS Stream" we are supposed to search for "RHEL"?
Yes, which is semantically similar to having to file bugs in the Red Hat Enterprise Linux product in bugzilla.
I'm sorry, I'm not meaning to be a pain. This is the first group that has moved things from bugzilla to Jira, and thus the first instructions. I'm trying to look at this from someone who logs into Jira for the first time, with no bookmarks and/or pre-defined looks.
I linked directly to the project to use in the PR. I'm confused why that doesn't point you directly to the project in question.
If I want to create a bug (or defect), or search for a defect on binutils, how do I do it? What Fabian said above, does not work for someone new to Jira.
s/Fabian/Florian
We can look at adding instructions for "how to use Jira", but they're not likely to land in the quickstart. We don't have "how to use bugzilla" instructions there either.
Briefly though, it's not that different. You login and go to the project, you click the blue "Create" button, and you select the component you want to file an issue against. It would be helpful if someone not familiar with Jira actually tried to do this and documented the pain points or confusing things along the way. That would round out documentation faster.
josh
On Wed, Aug 23, 2023 at 12:50:57PM +0200, Florian Weimer wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
This does not seem to be available to non-employees? I tried to find "CentOS Stream" under Projects, and can't find it but I can find RHEL.
I happen to have a bug to file that can't wait, so I guess I'll file under RHEL and ask for it to be moved.
On Wed, Sep 13, 2023 at 05:21:54PM -0500, Michel Lind wrote:
On Wed, Aug 23, 2023 at 12:50:57PM +0200, Florian Weimer wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
This does not seem to be available to non-employees? I tried to find "CentOS Stream" under Projects, and can't find it but I can find RHEL.
I happen to have a bug to file that can't wait, so I guess I'll file under RHEL and ask for it to be moved.
Ah, looks like Project should be RHEL, but Products should be CentOS Stream
Well, I missed that field in my last issue. Luckily, it wasn't specific to Platform Tools, so I did get a reply.
On 9/13/23 15:28, Michel Lind wrote:
On Wed, Sep 13, 2023 at 05:21:54PM -0500, Michel Lind wrote:
On Wed, Aug 23, 2023 at 12:50:57PM +0200, Florian Weimer wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
This does not seem to be available to non-employees? I tried to find "CentOS Stream" under Projects, and can't find it but I can find RHEL.
I happen to have a bug to file that can't wait, so I guess I'll file under RHEL and ask for it to be moved.
Ah, looks like Project should be RHEL, but Products should be CentOS Stream
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue
Has anyone written, or is planning on writing a blog, with pictures, to show how to do this more clearly? Although the instructions are correct, I still would like some pictures with circles and arrows that say "click here".
On Wed, Sep 13, 2023 at 3:38 PM Carlos Rodriguez-Fernandez < carlosrodrifernandez@gmail.com> wrote:
Well, I missed that field in my last issue. Luckily, it wasn't specific to Platform Tools, so I did get a reply.
On 9/13/23 15:28, Michel Lind wrote:
On Wed, Sep 13, 2023 at 05:21:54PM -0500, Michel Lind wrote:
On Wed, Aug 23, 2023 at 12:50:57PM +0200, Florian Weimer wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb,
glibc,
systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called
“RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and
select
“CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
This does not seem to be available to non-employees? I tried to find "CentOS Stream" under Projects, and can't find it but I can find RHEL.
I happen to have a bug to file that can't wait, so I guess I'll file under RHEL and ask for it to be moved.
Ah, looks like Project should be RHEL, but Products should be CentOS Stream
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi Michel,
"CentOS Stream 8", and "CentOS Stream 9", is in "Affected Version/s" when you select the Project "RHEL".
That's how I have submitted an issue before.
Regards, Carlos.
On 9/13/23 15:21, Michel Lind wrote:
On Wed, Aug 23, 2023 at 12:50:57PM +0200, Florian Weimer wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
This does not seem to be available to non-employees? I tried to find "CentOS Stream" under Projects, and can't find it but I can find RHEL.
I happen to have a bug to file that can't wait, so I guess I'll file under RHEL and ask for it to be moved.
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 2023-08-23 03:50, Florian Weimer wrote:
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
https://www.linkedin.com/feed/update/urn:li:activity:7113569427962413056/
Brian Smith mentioned the enterprise agreement requirement today. It's present when trying to create an account if you click on the "log in" link at issues.redhat.com. It's *not* present if you open "sso.redhat.com" directly and start the signup process. However, I don't know if you will be prompted to accept the agreement later, if you create an account and then use it for Jira.
(I'd test it, but I don't know if throw-away accounts are acceptable use, and I'm also temporarily limited in my ability to create throw-away email addresses.)
* Gordon Messmer:
On 2023-08-23 03:50, Florian Weimer wrote:
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
https://www.linkedin.com/feed/update/urn:li:activity:7113569427962413056/
Brian Smith mentioned the enterprise agreement requirement today. It's present when trying to create an account if you click on the "log in" link at issues.redhat.com. It's *not* present if you open "sso.redhat.com" directly and start the signup process. However, I don't know if you will be prompted to accept the agreement later, if you create an account and then use it for Jira.
It looks like a new requirement that is retroactively applied to existing accounts once they access issues.redhat.com.
I'll see what I can do to get this reverted.
Thanks, Florian
On Wed, Oct 4, 2023 at 1:02 PM Florian Weimer fweimer@redhat.com wrote:
- Gordon Messmer:
On 2023-08-23 03:50, Florian Weimer wrote:
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
https://www.linkedin.com/feed/update/urn:li:activity:7113569427962413056/
Brian Smith mentioned the enterprise agreement requirement today. It's present when trying to create an account if you click on the "log in" link at issues.redhat.com. It's *not* present if you open "sso.redhat.com" directly and start the signup process. However, I don't know if you will be prompted to accept the agreement later, if you create an account and then use it for Jira.
It looks like a new requirement that is retroactively applied to existing accounts once they access issues.redhat.com.
I'll see what I can do to get this reverted.
Thanks, Florian
And Florian brought this to my attention as well. I've been looking into it and it appears to be an artifact of how SSO was architected. I don't see any terms required for bugzilla.redhat.com so I don't think we need them for issues.redhat.com. Florian or I will send an update when we confirm one way or the other whether we think terms are needed or not. Hopefully not and it's just a matter of removing that check and checkbox from the page.
-Mike
Thanks Florian and Mike for looking into this.
Amy
On Friday, October 6, 2023, Mike McGrath mmcgrath@redhat.com wrote:
On Wed, Oct 4, 2023 at 1:02 PM Florian Weimer fweimer@redhat.com wrote:
- Gordon Messmer:
On 2023-08-23 03:50, Florian Weimer wrote:
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as
I
know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
7113569427962413056/
Brian Smith mentioned the enterprise agreement requirement today. It's present when trying to create an account if you click on the "log in" link at issues.redhat.com. It's *not* present if you open "sso.redhat.com" directly and start the signup process. However, I don't know if you will be prompted to accept the agreement later, if you create an account and then use it for Jira.
It looks like a new requirement that is retroactively applied to existing accounts once they access issues.redhat.com.
I'll see what I can do to get this reverted.
Thanks, Florian
And Florian brought this to my attention as well. I've been looking into it and it appears to be an artifact of how SSO was architected. I don't see any terms required for bugzilla.redhat.com so I don't think we need them for issues.redhat.com. Florian or I will send an update when we confirm one way or the other whether we think terms are needed or not. Hopefully not and it's just a matter of removing that check and checkbox from the page.
-Mike
* Florian Weimer:
- Gordon Messmer:
On 2023-08-23 03:50, Florian Weimer wrote:
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
https://www.linkedin.com/feed/update/urn:li:activity:7113569427962413056/
Brian Smith mentioned the enterprise agreement requirement today. It's present when trying to create an account if you click on the "log in" link at issues.redhat.com. It's *not* present if you open "sso.redhat.com" directly and start the signup process. However, I don't know if you will be prompted to accept the agreement later, if you create an account and then use it for Jira.
It looks like a new requirement that is retroactively applied to existing accounts once they access issues.redhat.com.
I'll see what I can do to get this reverted.
I've been notified that the requirement to agree to the Enterprise Agreement has been lifted. Based on a limited test, I believe to be this to be the case.
Please let me know if there are further issues.
Thanks, Florian
-
Amy Marrich -
Brendan Conoboy -
Carlos Rodriguez-Fernandez -
Colin Walters -
Florian Weimer -
Gordon Messmer -
Josh Boyer -
Michel Lind -
Mike McGrath -
Neal Gompa -
Patrick Riehecky -
Troy Dawson