[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Announcing EOL for Jessie images

On Tue, Oct 23, 2018 at 10:04:33AM +0200, Thomas Goirand wrote:
> >> I object because, at the 2018 Debian Cloud Sprint, we collectively
> >> decided that we were not offering Debian LTS Cloud Images.  Are we
> >> changing our decision?  I'd like to see collective decision making, not
> >> one-offs for each platform.
> > 
> > That's precisely why I asked. However, I don't want to focus too much on
> > process or collective decision making. Every provider is different.
> We're supposed to be deciding collectively. I don't agree that every
> provider is different for this specific case.

I disagree.

> > The existing images available for a given provider, and their adoption, is
> > different.
> No. On every platform, seeing Jessie going away is painful. Please don't
> consider your own case as a special one. This isn't helping anyone, and
> this isn't the case. I'd very much prefer if we were having consistency.

I disagree.

The level of adoption matters, and is potentially quite
different. A newer cloud platform, or one that was not supported by
Debian, might not have any users of jessie at all. So the matter is
irrelevant to them.

The specifics of this issue relate to the discoverability and
presentation of the jessie AMIs in the AWS Marketplace. Different cloud
providers may have different systems with different behavior. For
example, there may be other ways to indicate that a release is
deprecated while still letting it show up in search results. I do not
want to have to cater to the lowest common featureset. I want to use the
mechanisms provided by the cloud provider in the native way.


Attachment: signature.asc
Description: PGP signature

Reply to: