[Pkg-puppet-devel] PROPOSAL: reports=none retention policy on the server side

[Jérôme Charaoui]

Hello,

Le 2024-08-29 à 09 h 49, Antoine Beaupré a écrit :
> So let's try to settle this thread.
> 
> It seems a simple solution would be to switch the server-side
> configuration to "reports=none", only on the server, and remove the cron
> job.
> 
> That way, the *clients* can still send reports, and operators can
> *still* enable storing those on disk in YAML by tweaking that setting,
> but by default we don't accumulate those.

Agreed.

> We would make both changes (remove cron job and change setting) in sid,
> then wait for trixie to pick it up, then send a proposed-update for
> bookworm.
> 
> At this point, I'm not sure it warrants a NEWS file update, but if we do
> that we should probably narrow it down to bookworm. Otherwise we could
> also update the release notes, like we already did for that peculiar
> upgrade. That might be simpler and more visible/useful for people that
> might not already have upgraded.

One issue here I can see is that there could be objections from the 
stable release team. If that happens, then yes, we definitely need a 
NEWS file for unstable... Not sure whats the best course of action here.

> (I would object to doing the NEWS update in sid, as that might confuse
> people who *did* upgrade to bookworm correctly, when they upgrade to
> trixie.)
> 
> If there are no objections to this, I propose we deploy start this
> process on the coming Tuesday, September 3rd.

I was actually working on this now. I have also other things waiting to 
be uploaded, including a fix for FTBFS. I would also prefer we upload 
sooner rather than later, otherwise 8.4.0-5 (with the cron job) will 
have migrated to trixie.

-- Jérôme