Dear release team,
The puppet team invested a lot of time to package puppetserver 7. This
included:
- packaging all clojure packages
- fixing jruby
- packaging all puppet-modules that are "core"
- packaging puppetserver itself
At this time, we do have a puppetserver that works and is up-to-shape,
and it is probably the opinion of the team members that it should be
part of Bookworm.
It is my feeling that probably, we will need further update as we
discover issues, and probably, we will need updates during the freeze.
There's sill currently some autopkgtest not working on arch not amd64 or
arm64 for example.
However, it would be *very* frustrating for the team if we don't reach
our goal to have pupptserver 7 in Bookworm, and it probably would also
be a shame for Debian users if, for the first time in a long history of
Debian release, we didn't have puppet included in Debian.
May I ask (in advance) to the release team, to have a relaxed policy for
puppetserver related packages during the freeze, and allow us a little
bit more time to fix what's remaining? We're nearly there, and I believe
that by the end of next month, every piece of the puzzle will be in
place, including a nice upgrade path from Bullseye.
At the same time, and that concerns *me* for OpenStack packages: I had
no way to check if openstack-cluster-installer worked well before
puppetserver is in. I'll be doing the checks "soon", but that's a bit
late as well in the development process. I do expect that I'll have some
puppet manifest last-minute modifications to be done. I do expect these
type of change to be "not small"...
Cheers,
Thomas Goirand (zigo)
