[Debichem-devel] The drawbacks of dummy changelog entries

[Santiago Vila]

El 17/3/25 a las 16:35, Andrius Merkys escribió:
> For each Salsa repository there will be at most one UNRELEASED ("dummy") debian/changelog entry, which is not meant to be uploaded until someone does s/UNRELEASED/unstable/ and releases the package. I have seen this practice in >2 teams and I think it has some benefits.
> 
> First, it shows that new release is in progress. It might be that someone is working actively, made a drive-by change, or hit a roadblock.
> 
> Second, it documents changes since the last update of debian/changelog. While one might say that 'git log' does the same, 'git log' usually contains much more noise. I personally work in small commits without rebasing them.
> 
> Third, it is a convenient place for todo list for the upcoming upload.

I see your point, but I don't see how any of the above applies
for the completely empty dummy changelogs I was really talking about.

Maybe it would make sense to create a changelog only when there are
actual changes? That way the warning about "pending commits, time to release?"
would only be triggered when it really makes sense.

Thanks.