Re: Bugs status tracking

Hi Greg,

Thank you for your response and feedback.

I have created a *demo repository* for tracking pgsql-bugs reports:
🔗 GitHub Repository
<https://github.com/Vasuki-git/mailing-lists/issues?q=is%3Aissue%20state%3Aopen%20sort%3Aupdated-desc>

The goal of this repo is to provide a *structured view* of bug reports from
the pgsql-bugs mailing list while ensuring that all discussions continue in
the mailing list itself. Each GitHub issue contains details such as
the *subject,
date, and message ID* to help contributors quickly find and respond to the
original thread.

I understand that this is just an initial *proof of concept*, and I welcome
any feedback or suggestions on improving the workflow. I appreciate your
advice, and I’ll iterate on this based on community input.

Looking forward to your thoughts!

Best,
Vasuki


On Mon, 17 Feb 2025 at 20:01, Greg Sabino Mullane <htamfids@gmail.com>
wrote:

> On Mon, Feb 17, 2025 at 2:47 AM VASUKI M <vasukim1992002@gmail.com> wrote:
>
>> 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.
>>
>
> All of our data is public and free to use, so you are welcome to do with
> it what you want.
>
> I would suggest just creating a proof of concept and let's see what it
> looks like. Nobody is going to officially bless it beforehand. Being able
> to see and critique an actual workflow is invaluable.
>
> Be warned that no matter what you come up with, not everyone will be happy
> with it. That's the nature of things, so don't be discouraged.
>
> Cheers,
> Greg
>
> --
> Crunchy Data - https://www.crunchydata.com
> Enterprise Postgres Software Products & Tech Support
>
>