Re: python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED
On Fri, May 26, 2017 at 03:04:47PM +0200, Raphael Hertzog wrote:
>...
> I remember having had a discussion with Chris Lamb who uploaded 1.9.0
> to unstable without any coordination with the other co-maintainers (while
> he only recently re-joined the maintainers to maintaine 1.9.x in experimental).
>
> We discussed the possibility to try to get 1.11 LTS... it was possibility with a
> lot of preparatory work that did never happen.
>...
Who is "we", and how would that ever have been possible?
In December when 1.9 entered unstable and you uploaded 1.8.7-2~bpo8+1
1.11 LTS was already announced to be released in April 2017.[1]
At that point the expected date for the final hard freeze of stretch was
December 2016 [2] (it was moved to February 2017 later[3]).
Freeze in December 2016 means expected release in April/May 2017,
and the last permitted upload date for new upstream versions to
stretch would have been in late November 2016.
This sounds as if it was already obvious in December 2015 that 1.11 LTS
was a not an option for stretch, just like it is already obvious today
that 2.2 LTS won't be an option for buster.
> Cheers,
cu
Adrian
[1] https://web.archive.org/web/20151103183439/https://www.djangoproject.com/download/
[2] https://www.debian.org/News/2009/20090729
[3] https://lists.debian.org/debian-devel-announce/2016/03/msg00001.html
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Reply to: