You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2021. It is now read-only.
I think I am subscribed to pkgdb notifications but when limb created nodejs-gettext-parser package branches, I do not get personal notifications in email but on IRC.
My point here is we are used to with the process where we pick any older package review completed bug and can find on bugzilla itself that when package submitter requested for SCM request and when its completed.
This will not be there now with new pkgdb admin request process.
Now why I find this information is useful because I do review triaging most times and just by looking this information I can know what progress is happening on review. Like if review is approved whether submitter have submitted SCM request or not. If not then I can ping him accordingly but now it looks bugzilla is disconnected from further process.
I am still not sure if this implementation will be duplicate FMN to users but for bugzilla history its important.
The text was updated successfully, but these errors were encountered:
I think I am subscribed to pkgdb notifications but when limb created nodejs-gettext-parser package branches, I do not get personal notifications in email but on IRC.
My point here is we are used to with the process where we pick any older package review completed bug and can find on bugzilla itself that when package submitter requested for SCM request and when its completed.
This will not be there now with new pkgdb admin request process.
Now why I find this information is useful because I do review triaging most times and just by looking this information I can know what progress is happening on review. Like if review is approved whether submitter have submitted SCM request or not. If not then I can ping him accordingly but now it looks bugzilla is disconnected from further process.
I am still not sure if this implementation will be duplicate FMN to users but for bugzilla history its important.
The text was updated successfully, but these errors were encountered: