>
One good thing is that there would be some historybehind each item that's added and closed
Yes this is the exact point that I was going for because honestly clicking on a link on the todo list to just see some bug/feature request that existed in 2007 and then tracking it down to the last thread just to see that no one wanted it in the first place was a little frustrating.
I am not sure of the exact solution here but that can be put forward to further discussion or we can stop redirecting new developers to the todo list.
Maybe some experienced members from the community can provide their insights in form of a wiki page?
That being said, I am also really new to the community and limited in my knowledge of the main code base and best practices, but this has been my experience so far.
Regards,
Akshat Jaimini
On 2024-Sep-19, Akshat Jaimini wrote:
> I was going through the TODO list on the wiki to pick up some patches to
> work on and I found a lot of outdated items on that list that are over a
> decade old.
Yeah, this has been done before. It's a hard thankless job.
> Can I get a green signal to remove these items from the wiki?
Let's discuss each item here first.
> PS: I think we should also reconsider the idea of using a wiki page to list
> all the todo items. It will be really helpful if we can integrate some sort
> of a bug tracker to our workflow. Will the hackers mailing list be a good
> place to start a thread on this?
I don't love this wiki page, but I'm not sure a generic bugtracker is
going to be better. One good thing is that there would be some history
behind each item that's added and closed, but bugtrackers have lots of
features and I think it's going to become a stinking mess pretty
quickly.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
