Re: scratch/igc: Keeping a TODO list?

[Eli Zaretskii]

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sun, 12 Jan 2025 16:59:31 +0000
> Cc: eller.helmut@gmail.com, emacs-devel@gnu.org, gerd@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I think we should have a TODO list of the necessary jobs that are
> > prerequisites for landing the branch.  Developments that are not
> > necessary for that are best kept separate, since they can wait until
> > after we land the branch.
> 
> My current idea is to split the file into separate sections:
> - *Blockers* are known to be blocking merging IGC to the master branch.
> - *Not blockers* are known not to be blocking a merge.
> - *Uncategorized* are not yet categorized into any the above.
> - *Other ideas* are improvement ideas.

My recommendation would be to leave only the first group.  The rest
don't need to be managed, so having them is just extra work without
any significant gain.  I think we should focus on the important stuff
and on the goal.

> This means that the list you ask for is essentially "Blockers", and then
> what follows after is a relatively exhaustive list of other things.
> 
> My thinking is that this helps because:
> - We won't risk losing track of anything, not even smaller items.
> - It's easier to look at all items as a whole, and perhaps see that this
>   or that item belongs in a different category.
> - We can just merge the remaining items into etc/TODO when we merge to
>   master.
> - It will make it easier for casual observers to jump in and help.
> 
> I agree that non-MPS related ideas are best kept separate.

people could add items to etc/TODO on the branch regardless, so I
don't think we should maintain separately any tasks that are not
necessary for preparing the branch.  That was your original motivation
for having this list, wasn't it?