Thread

Bugs status tracking

VASUKI M <vasukim1992002@gmail.com> — 2025-02-17T04:36:12Z

Hi,
Refer this bug:
https://www.postgresql.org/message-id/flat/CACTYHzhXPM4wOFavXLaSpj3bNPF%2BF3rNc_RV0%3DLF-KzPGofQrw%40mail.gmail.com#e0b0377dda5356911a4497107f21c797
Please can u tell whether it is ok or not or do we need to change anything
,as of now the community is bigger and we have people to track the status
so please give suggestions or corrections.

*I understand the community's strong preference for maintaining the
mailing list as the primary platform for discussions. My proposal does not
aim to replace or disrupt the workflow of the mailing list. Instead, it
seeks to provide a transparent and organized way to access bug-related
data, which can be particularly helpful for new contributors or those
outside the community. Currently, there is no centralized system to track
the status of bugs, nor is there a dedicated GitHub repository for
PostgreSQL bugs, as the main Git repository does not allow issues to be
posted.

*Let me explain the workflow, and I welcome feedback and suggestions:

*--Bug as the Main Issue with Comments in Chronological Order:*
Each bug from the pgsql-bugs mailing list will be added as a main
issue in the GitHub repository, with all subsequent replies organized as
comments in chronological order.[Currently, viewing an entire discussion
requires navigating the thread link in the mailing list. This proposal
ensures that bugs and replies are always presented in an organized and
accessible manner.]
**Automatic Updates: If a new reply is logged for an
existing bug, it will be automatically added to the corresponding issue's
comments. Labels will also update dynamically. For example, if a previously
closed bug is reopened, its label will change to "Open."

*--Bug Status Identification:*
Bug status will be categorized as "Open," "Closed," or
"Unresponsive" using NLP techniques such as Sentiment Analysis, Keyword
Analysis, and Time Heuristics based on the content and tone discussed.
**Any suggestions for improvements or alternate methods for
identifying bug statuses are greatly appreciated.

*--Maintaining the Mailing List Workflow:*
This system will not serve as a discussion platform. Instead, it
maintains a systematic flow and status of bugs posted on the pgsql-bugs
mailing list in a more readable format.
**If anyone wants to discuss a bug based on the status in the
GitHub repository, they can refer to the date posted and continue the
discussion on the mailing list. Any updates from the mailing list will then
be reflected in the GitHub repository.

*As Álvaro suggested earlier, if there is a way to collaborate with the
CommitFest app or integrate this proposal with the mailing list more
directly, please share the relevant code or guidelines. Such collaboration
would be a valuable addition.

Thanks and regards,
Vasuki M
C-DAC,Chennai,India
mail: bharatdb(at)cdac(dot)in, vasukim1992002(at)gmail(dot)com
phn:+91 6374605133