Bug#1029225: Announced soft freeze date clashes with Ruby team's team-meeting to prepare for Bookworm
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: debian-ruby@lists.debian.org, terceiro@debian.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
on December 19th, 2022, the Ruby team announced a proposed meeting from
February 6th to 10th 2023 [1,2]. One of the main tasks will be the preparation
for Bookworm and the final switch to Ruby 3.1.
Yesterday, the release team announced the final freeze dates [3].
Unfortunately, the date for the soft freeze is scheduled for February 12th,
which will make it virtually impossible for us to get the packages, which are
not yet in Testing (e.g. the whole Jekyll ecosystem), and the packages, which
are scheduled for removal before the meeting, back into Testing and therefore
into Bookworm.
We would like to ask you to postpone the freeze date(s) by a full week, so we
can care about all affected packages properly and ship them with Bookworm.
I know, that these dates have been proposed a year ago. Unfortunately, nobody
spotted this timing issue sooner. Otherwise, we would have contacted you, of
course.
Regards, Daniel
[1] https://lists.debian.org/debian-sprints/2022/12/msg00002.html
[2] https://wiki.debian.org/Teams/Ruby/Meeting/Paris2023
[3] https://lists.debian.org/debian-devel-announce/2023/01/msg00004.html
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPJ31wACgkQS80FZ8KW
0F0+XQ//SX5f0NO5tbfHhV0bqMziEZneXJ5TQVAd/0C0owkCigWy5LprofRyMRUe
DR70CJwd1xsNVqQD9qnN0NrvJX2iT7R0sU28So7u3lefpMh9ISMp3NyqWYnO/CEI
BZ3b8w1iy73REg9pHnYBtvB2z2+WSfwVY6yqq2lpCmN1EDx/tezY2IAtpq/FZ2Up
Vn4f83E7nD/3LgPao/jYzPRtARxod2DfKKTkHUzLged5dSXvSGZPY6Nm1kkIdpCj
mw7o8+5ilsIAc11FiZ6u2Yfy6bj7Qwgds3hGrkA1cZH0lVMlyVyBExY1SRCgqmUO
nSymzomKsfqEOjuZnknVwwz0k2R8ZaId+KfbwSmWt7VtVtZEpT1ztHBPBUuURBeS
B/44Rv6+PLfENB6DT0GjzdidQPNiOGPtbe8tX2qvotbXHmpxSu2820c4eYsdnoMm
6G1xnt6JieFw7FdC6w0BZnA8SJG3KZ9hS5AUe+SVj3BT6CQU1X1HBEEm6CP1JFlT
t7+GqrVjyaiR7FYsTTF6Uc+ZJeprkn2IXF9awYGKzNe1KegXgu4GlsqHF3QSn2lM
4XZ7Jl007PLmez6GhPCvAI+L6jHLcxLqJ90cSFFEhzvpIzjbb2XcZecNENTUY6CT
S3bthBRtZerAIdJxVJfL2f5j9XRLvkoAFjOpVv8AjzXScf9Lve4=
=S4nU
-----END PGP SIGNATURE-----
Reply to: