pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18784: Bugs and BugTracking
5+ messages / 4 participants
[nested] [flat]
* BUG #18784: Bugs and BugTracking
@ 2025-01-24 05:05 PG Bug reporting form <noreply@postgresql.org>
2025-01-24 18:25 ` Re: BUG #18784: Bugs and BugTracking Álvaro Herrera <alvherre@alvh.no-ip.org>
0 siblings, 1 reply; 5+ messages in thread
From: PG Bug reporting form @ 2025-01-24 05:05 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: bharatdb@cdac.in
The following bug has been logged on the website:
Bug reference: 18784
Logged by: Bharat DB
Email address: bharatdb@cdac.in
PostgreSQL version: 17.0
Operating system: Linux
Description:
Dear PostgreSQL Community,
We hope this message finds you well.
While going through the pgsql-bugs i found out there is no proper website or
a
system to monitor bugs or to track bug status ,i have also referred this
bug
https://www.postgresql.org/message-id/flat/5618263A.40806%40agliodbs.com#a8cc0869f5a3273df07c59fb8e2...
but i can't find that website is working now.
So,we propose creating a centralized repository that:
* Consolidates bug reports related to PostgreSQL-based applications and
their
integrations.
* Includes bugs identified and pushed from the PostgreSQL pgsql-bugs
mailing
list, categorized as open or closed for better tracking.
* Facilitates discussions and resolutions within the community.
This repository aims to reduce duplication of effort, improve transparency,
and
provide a unified platform for managing bug-related information. We are
also
pushing relevant data (e.g., author, message ID, date and time, body
message,
attachments, and URLs) from the pgsql-bugs list to GitHub for improved
organization and access.
I have created and dummy repo and tried to push some bugs ,Kindly find the
attachment of demo data below.
We kindly request your feedback for this initiative.
Your input would be invaluable in ensuring that this repository serves as
a
constructive addition to the PostgreSQL ecosystem.
Looking forward to your thoughts and suggestions.
Thank you for your time and support.
Warm regards,
Vasuki M
CDAC Chennai
Email:bharatdb@cdac.in
Phone:6374605133
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG #18784: Bugs and BugTracking
2025-01-24 05:05 BUG #18784: Bugs and BugTracking PG Bug reporting form <noreply@postgresql.org>
@ 2025-01-24 18:25 ` Álvaro Herrera <alvherre@alvh.no-ip.org>
2025-01-24 19:35 ` Re: BUG #18784: Bugs and BugTracking Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Álvaro Herrera @ 2025-01-24 18:25 UTC (permalink / raw)
To: bharatdb@cdac.in; pgsql-bugs@lists.postgresql.org
Hello
On 2025-Jan-24, PG Bug reporting form wrote:
> While going through the pgsql-bugs i found out there is no proper website or
> a system to monitor bugs or to track bug status ,i have also referred
> this bug
> https://www.postgresql.org/message-id/flat/5618263A.40806%40agliodbs.com#a8cc0869f5a3273df07c59fb8e2...
> but i can't find that website is working now.
This refers to the following
https://granicus.if.org/pgbugs/
which was an experiment with a bug tracker from 2015 that gave no fruit.
> I have created and dummy repo and tried to push some bugs ,Kindly find the
> attachment of demo data below.
I didn't see any attachment to this email, but I doubt that a system
that doesn't feed directly from the mailing list traffic is going to go
anywhere with this community. A manually maintained github repo seems
unworkable.
I described what I see as working during last year's pgconf.dev
developer's meeting, namely a system very similar to our patch
tracker^W^W commitfest app, which would contain links to pgsql-bugs
threads. The app, in addition to listing the relevant thread links for
each bug, would allow simple metadata such as affected Postgres
branches, SHA1 git commit IDs (indicating point at which each bug was
fixed on each branch), maybe a simple tagging system. No discussion
would take place on the app itself, since that should continue to be
relegated to mailing lists.
It would be possible to create bugs in that system in two ways: one,
using the already existing bug reporting form, which would assign the
bug number, post to pgsql-bugs and create the bug metadata in the new
system; two, by manually accepting a link to a thread in some mailing
list (probably pgsql-hackers, but it could be any other
@lists.postgresql.org list), whereby a new bug number would be assigned
but no additional mail is sent.
I think this wouldn't require much new code, because, as I said, it
would be very similar to the commitfest app, so it's quite likely that
we could reuse a lot of that. It would be a separate app, however,
because though they are similar, the requirements are different enough.
Why do I think this would be successful? Many years ago, there was a
proposal that would use Debian's bugtracker, which is essentially a
glorified mailing list with per-bug archives, plus a lot of smarts to
know when to close a bug. This had the most traction among this
community, but the idea died down when it was clear that 1) the Debian
community was not really open to sharing their stuff, and 2) nobody
offered to maintain this.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG #18784: Bugs and BugTracking
2025-01-24 05:05 BUG #18784: Bugs and BugTracking PG Bug reporting form <noreply@postgresql.org>
2025-01-24 18:25 ` Re: BUG #18784: Bugs and BugTracking Álvaro Herrera <alvherre@alvh.no-ip.org>
@ 2025-01-24 19:35 ` Tom Lane <tgl@sss.pgh.pa.us>
2025-01-28 09:56 ` Re: BUG #18784: Bugs and BugTracking VASUKI M <vasukim1992002@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 2025-01-24 19:35 UTC (permalink / raw)
To: Álvaro Herrera <alvherre@alvh.no-ip.org>; +Cc: bharatdb@cdac.in; pgsql-bugs@lists.postgresql.org
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@alvh.no-ip.org> writes:
> I described what I see as working during last year's pgconf.dev
> developer's meeting, namely a system very similar to our patch
> tracker^W^W commitfest app, which would contain links to pgsql-bugs
> threads.
Yeah, given our existing workflow (which no one seems in a hurry
to change), what we fundamentally want is an index to mailing list
threads about bugs, plus status information.
> Why do I think this would be successful? Many years ago, there was a
> proposal that would use Debian's bugtracker, which is essentially a
> glorified mailing list with per-bug archives, plus a lot of smarts to
> know when to close a bug. This had the most traction among this
> community, but the idea died down when it was clear that 1) the Debian
> community was not really open to sharing their stuff, and 2) nobody
> offered to maintain this.
Even more years ago (roughly around 2000 IIRC), we actually did try
to use a bug tracker, but the experiment only lasted a few weeks.
It failed because (a) that tracker was not adapted to mailing-list-
based workflow, and (b) we didn't have people who were interested
in moderating/curating the tracker's contents. If you don't have
some people who will keep status entries up-to-date, close out junk
bugs, and such, the tracker descends to uselessness very quickly.
Our community was far smaller then than it is today, and I bet
finding people for (b) would be easier. But we still need
something that meets criterion (a), and GitHub ain't it.
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG #18784: Bugs and BugTracking
2025-01-24 05:05 BUG #18784: Bugs and BugTracking PG Bug reporting form <noreply@postgresql.org>
2025-01-24 18:25 ` Re: BUG #18784: Bugs and BugTracking Álvaro Herrera <alvherre@alvh.no-ip.org>
2025-01-24 19:35 ` Re: BUG #18784: Bugs and BugTracking Tom Lane <tgl@sss.pgh.pa.us>
@ 2025-01-28 09:56 ` VASUKI M <vasukim1992002@gmail.com>
2025-01-30 03:59 ` Fwd: BUG #18784: Bugs and BugTracking VASUKI M <vasukim1992002@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: VASUKI M @ 2025-01-28 09:56 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>; Tom Lane <tgl@sss.pgh.pa.us>; alvherre@alvh.no-ip.org; +Cc: bharatdb@cdac.in
*Thank you for the feedback!
*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@cdac.in, vasukim1992002@gmail.com
phn:+91 6374605133
On Tue, 28 Jan 2025 at 15:17, Bharat Database <bharatdb@cdac.in> wrote:
>
> > On 01/25/2025 1:05 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >
> >
> > =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@alvh.no-ip.org> writes:
> > > I described what I see as working during last year's pgconf.dev
> > > developer's meeting, namely a system very similar to our patch
> > > tracker^W^W commitfest app, which would contain links to pgsql-bugs
> > > threads.
> >
> > Yeah, given our existing workflow (which no one seems in a hurry
> > to change), what we fundamentally want is an index to mailing list
> > threads about bugs, plus status information.
> >
> i totally understand it
>
> > > Why do I think this would be successful? Many years ago, there was a
> > > proposal that would use Debian's bugtracker, which is essentially a
> > > glorified mailing list with per-bug archives, plus a lot of smarts to
> > > know when to close a bug. This had the most traction among this
> > > community, but the idea died down when it was clear that 1) the Debian
> > > community was not really open to sharing their stuff, and 2) nobody
> > > offered to maintain this.
> >
> > Even more years ago (roughly around 2000 IIRC), we actually did try
> > to use a bug tracker, but the experiment only lasted a few weeks.
> > It failed because (a) that tracker was not adapted to mailing-list-
> > based workflow, and (b) we didn't have people who were interested
> > in moderating/curating the tracker's contents. If you don't have
> > some people who will keep status entries up-to-date, close out junk
> > bugs, and such, the tracker descends to uselessness very quickly.
> >
> > Our community was far smaller then than it is today, and I bet
> > finding people for (b) would be easier. But we still need
> > something that meets criterion (a), and GitHub ain't it.
> >
> > regards, tom lane
>
>
> ------------------------------------------------------------------------------------------------------------
> [ C-DAC is on Social-Media too. Kindly follow us at:
> Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
>
> This e-mail is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies and the original message. Any unauthorized review, use,
> disclosure, dissemination, forwarding, printing or copying of this email
> is strictly prohibited and appropriate legal action will be taken.
>
> ------------------------------------------------------------------------------------------------------------
>
>
Attachments:
testrepo1.png (image/png, 223.2K) download
view image
testrepo2.png (image/png, 131.5K) download
view image
* Fwd: BUG #18784: Bugs and BugTracking
2025-01-24 05:05 BUG #18784: Bugs and BugTracking PG Bug reporting form <noreply@postgresql.org>
2025-01-24 18:25 ` Re: BUG #18784: Bugs and BugTracking Álvaro Herrera <alvherre@alvh.no-ip.org>
2025-01-24 19:35 ` Re: BUG #18784: Bugs and BugTracking Tom Lane <tgl@sss.pgh.pa.us>
2025-01-28 09:56 ` Re: BUG #18784: Bugs and BugTracking VASUKI M <vasukim1992002@gmail.com>
@ 2025-01-30 03:59 ` VASUKI M <vasukim1992002@gmail.com>
0 siblings, 0 replies; 5+ messages in thread
From: VASUKI M @ 2025-01-30 03:59 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org
---------- Forwarded message ---------
From: VASUKI M <vasukim1992002@gmail.com>
Date: Tue, 28 Jan 2025 at 15:26
Subject: Re: BUG #18784: Bugs and BugTracking
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>, Tom
Lane <tgl@sss.pgh.pa.us>, <alvherre@alvh.no-ip.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-bugs@lists.postgresql.org <
pgsql-bugs@lists.postgresql.org>, <bharatdb@cdac.in>
*Thank you for the feedback!
*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@cdac.in, vasukim1992002@gmail.com
phn:+91 6374605133
On Tue, 28 Jan 2025 at 15:17, Bharat Database <bharatdb@cdac.in> wrote:
>
> > On 01/25/2025 1:05 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >
> >
> > =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@alvh.no-ip.org> writes:
> > > I described what I see as working during last year's pgconf.dev
> > > developer's meeting, namely a system very similar to our patch
> > > tracker^W^W commitfest app, which would contain links to pgsql-bugs
> > > threads.
> >
> > Yeah, given our existing workflow (which no one seems in a hurry
> > to change), what we fundamentally want is an index to mailing list
> > threads about bugs, plus status information.
> >
> i totally understand it
>
> > > Why do I think this would be successful? Many years ago, there was a
> > > proposal that would use Debian's bugtracker, which is essentially a
> > > glorified mailing list with per-bug archives, plus a lot of smarts to
> > > know when to close a bug. This had the most traction among this
> > > community, but the idea died down when it was clear that 1) the Debian
> > > community was not really open to sharing their stuff, and 2) nobody
> > > offered to maintain this.
> >
> > Even more years ago (roughly around 2000 IIRC), we actually did try
> > to use a bug tracker, but the experiment only lasted a few weeks.
> > It failed because (a) that tracker was not adapted to mailing-list-
> > based workflow, and (b) we didn't have people who were interested
> > in moderating/curating the tracker's contents. If you don't have
> > some people who will keep status entries up-to-date, close out junk
> > bugs, and such, the tracker descends to uselessness very quickly.
> >
> > Our community was far smaller then than it is today, and I bet
> > finding people for (b) would be easier. But we still need
> > something that meets criterion (a), and GitHub ain't it.
> >
> > regards, tom lane
>
>
> ------------------------------------------------------------------------------------------------------------
> [ C-DAC is on Social-Media too. Kindly follow us at:
> Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
>
> This e-mail is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies and the original message. Any unauthorized review, use,
> disclosure, dissemination, forwarding, printing or copying of this email
> is strictly prohibited and appropriate legal action will be taken.
>
> ------------------------------------------------------------------------------------------------------------
>
>
Attachments:
testrepo1.png (image/png, 223.2K) download
view image
testrepo2.png (image/png, 131.5K) download
view image
end of thread, other threads:[~2025-01-30 03:59 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-01-24 05:05 BUG #18784: Bugs and BugTracking PG Bug reporting form <noreply@postgresql.org>
2025-01-24 18:25 ` Álvaro Herrera <alvherre@alvh.no-ip.org>
2025-01-24 19:35 ` Tom Lane <tgl@sss.pgh.pa.us>
2025-01-28 09:56 ` VASUKI M <vasukim1992002@gmail.com>
2025-01-30 03:59 ` VASUKI M <vasukim1992002@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox