All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sage Weil <sage-BnTBU8nroG7k1uMJSBkQmQ@public.gmane.org>
To: ceph-maintainers-Qp0mS5GaXlQ@public.gmane.org
Cc: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ceph-users-Qp0mS5GaXlQ@public.gmane.org
Subject: Re: Can we drop ubuntu 14.04 (trusty) for kraken and lumninous?
Date: Mon, 14 Nov 2016 14:24:19 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.11.1611141424060.29579@piezo.us.to> (raw)
In-Reply-To: <alpine.DEB.2.11.1611111837410.29579-ie3vfNGmdjePKud3HExfWg@public.gmane.org>

On Fri, 11 Nov 2016, Sage Weil wrote:
> Currently the distros we use for upstream testing are
> 
>  centos 7.x
>  ubuntu 16.04 (xenial)
>  ubuntu 14.04 (trusty)
> 
> We also do some basic testing for Debian 8 and Fedora (some old version).
> 
> Jewel was the first release that had native systemd and full xenial 
> support, so it's helpful to have both 14.04 and 16.04 supported to provide 
> an upgrade path.  But I think we can safely drop 14.04 now for kraken and 
> luminous.  Our options are
> 
> 1) keep testing on xenial and trusty, and keep building packages for both

Sounds like we'll keep trusty around for a while.  Thanks, everyone!

sage

  parent reply	other threads:[~2016-11-14 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 18:43 Can we drop ubuntu 14.04 (trusty) for kraken and lumninous? Sage Weil
2016-11-11 20:22 ` Blair Bethwaite
     [not found]   ` <CA+z5DszZp-j450Q1HyfQQtEx9tqeazJ=PqnUkmwFND_kMrvk-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-14 10:59     ` Özhan Rüzgar Karaman
     [not found] ` <alpine.DEB.2.11.1611111837410.29579-ie3vfNGmdjePKud3HExfWg@public.gmane.org>
2016-11-11 20:10   ` Randy Orr
2016-11-14 11:08   ` Tomasz Kuzemko
2016-11-14 14:24   ` Sage Weil [this message]
2016-11-16 18:40     ` Yuri Weinstein
     [not found]       ` <CAMMFjmE_S0ew2h7wWFF2wQccjffX7iGiJS=sxgkvOcvv86DG6Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-16 20:48         ` Sage Weil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.11.1611141424060.29579@piezo.us.to \
    --to=sage-bntbu8nrog7k1umjsbkqmq@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-maintainers-Qp0mS5GaXlQ@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.