Re: svn status should not show unmodified files in changelists

Julian Foad wrote on Wed, Nov 06, 2019 at 16:07:23 +0000:
> Perhaps one aspect of being in a mature and stable phase of a project's life
> means that if we are going to change how an existing feature works, we
> should not change it one little bit at a time like we did in early
> development phases. Instead we should plan and release a set of related
> changes all together. Instead of just changing "svn status" to not show
> unmodified files, we should plan a set of improvements to changelists, and
> that would be one of the changes.

How do you figure this? What would be the benefit?

If you say that we should plan ahead and keep the big picture in mind, I'd
agree; but it sounds like you're saying that small, incremental changes and
not letting the perfect be the enemy of the good were appropriate approaches
for 0.x, while now is the time for making larger refactorings all at once…

Did I misunderstand?

Cheers,

Daniel
Received on 2019-11-07 12:18:20 CET