[Jenkins-infra] Discussion about removing packages

Oleg Nenashev o.v.nenashev at gmail.com
Tue Apr 25 16:35:26 UTC 2017


The problem is with updating people.

Since 2.55 the packages do not get updated correctly in Debian (see
https://issues.jenkins-ci.org/browse/JENKINS-43629). It may be possible to
imagine use-case when people get updated to 2.54 and then stuck if we do
not delete the package. I do not care much about that for Weekly releases,
but we may hit the same issue once Java 8 goes into LTS.

So we need to decide what to do within 2 months till the next LTS baseline



2017-04-25 18:21 GMT+02:00 Andrew Bayer <andrew.bayer at gmail.com>:

> My instinct is also to reject this. Historically, I've only ever pulled
> public-facing releases when there's something unbelievably catastrophic
> wrong with them, not just for a bug like this.
>
> A.
>
> On Tue, Apr 25, 2017 at 12:13 PM, R. Tyler Croy <tyler at monkeypox.org>
> wrote:
>
>>
>> There has been some discussion by users and some contributors about
>> removing
>> Jenkins 2.54 Debian packages which didn't properly specify a dependency on
>> JRE8.
>>
>> Related to: https://issues.jenkins-ci.org/browse/INFRA-1167
>>
>>
>> I wanted to get more input from infra folks before any direction is taken.
>>
>> I'm strongly against this for the following reasons:
>>
>>  * This is a weekly release issue. We have not, to my recollection, ever
>>    *pulled* a weekly release. LTS users will never be affected by this
>> kind of
>>    issue. Pulling a weekly release is a terrible precedent in my opinion,
>> and
>>    more work than I would ever want to support.
>>
>>  * I would argue that users affected by this issue are basically using
>>    unsupported Jenkins versions anyways, as we do not support weekly
>> releases
>>    except for maybe "latest." When the LTS moves to Java 8, these users
>>    will also then be running unsupported versions of Jenkins.
>>
>>  * Ubuntu 14.04 LTS is three years old, and is only receiving maintenance
>>    updates anyways (https://www.ubuntu.com/info/release-end-of-life).
>> While
>>    unfortunate that this has affected some users, those using older LTSes
>> and
>>    weekly Jenkins releases are operating (IMHO) in an uncanny valley as
>> far as
>>    software stability goes.
>>
>>  * We have no automation or auditability for such a package removal. I
>> don't
>>    think we should either really.
>>
>>
>> In the past, we never pulled other Jenkins versions which were broken
>> from the
>> start (think boot errors), and I don't think this issue merits changing
>> that
>> now.
>>
>>
>> I am interested in other people's opinions, since I'm very biased against
>> the
>> weekly releases for "serious business" to begin with :)
>>
>>
>> Cheers
>> - R. Tyler Croy
>>
>> ------------------------------------------------------
>>      Code: <https://github.com/rtyler>
>>   Chatter: <https://twitter.com/agentdero>
>>      xmpp: rtyler at jabber.org
>>
>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
>> ------------------------------------------------------
>>
>> _______________________________________________
>> Jenkins-infra mailing list
>> Jenkins-infra at lists.jenkins-ci.org
>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>
>>
>
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20170425/4cc6785f/attachment.html>


More information about the Jenkins-infra mailing list