A small suggestion for the Release Notes about ungoogled-chromium-macos HOT 4 CLOSED

yep, I'm definitely in favor of removing the timestamp. I'm not entirely sure if they were added because CI was unstable or frequent rebuilds were needed, though

For now, we shouldn't need to rerun CIs unless we're changing the CI script and just want to test it. And I don't see any cases where there will be rebuilds (with the old script, it's possible that multiple releases will be created, it won't happen again).

I will make this change in the next update then.

from ungoogled-chromium-macos.

Yeah it is an unexpected problem to have it mismatched (I introduced this bug and haven't found it) and I do plan to remove these in the next update.

My plan is to just remove entirely the epoch timestamp from the release (from tag, title, and body), and also just use the chromium_version + ungoogled_revision (in this case, just the 121.0.6167.85-1.1) for both the tag and the release title, so that it behaves in the same way as the other repos in the org. (As mentioned here a bit (sort of))

Any opinions on this? /cc @networkException @PF4Public

from ungoogled-chromium-macos.

yep, I'm definitely in favor of removing the timestamp. I'm not entirely sure if they were added because CI was unstable or frequent rebuilds were needed, though

from ungoogled-chromium-macos.

yep, I'm definitely in favor of removing the timestamp. I'm not entirely sure if they were added because CI was unstable or frequent rebuilds were needed, though

They were added in #92, perhaps @kramred has any recollection of it if they're around?

from ungoogled-chromium-macos.