On Mon, 2019-10-07 at 16:29 +0100, Daniel P. Berrangé wrote:
> On Mon, Oct 07, 2019 at 04:58:34PM +0200, Andrea Bolognani wrote:
> > It seems to me that people who want to run the latest version of
> > whatever application will also use a non-obsolete operating system,
> > and conversely people
On Mon, Oct 07, 2019 at 04:58:34PM +0200, Andrea Bolognani wrote:
> On Mon, 2019-10-07 at 13:35 +0100, Daniel P. Berrangé wrote:
> > On Mon, Oct 07, 2019 at 01:58:10PM +0200, Andrea Bolognani wrote:
> > > Can't we follow the same policy as the main library? That would make
> > > it more
On Mon, 2019-10-07 at 13:35 +0100, Daniel P. Berrangé wrote:
> On Mon, Oct 07, 2019 at 01:58:10PM +0200, Andrea Bolognani wrote:
> > Can't we follow the same policy as the main library? That would make
> > it more straightforward to reason about. Also note that our CI only
> > runs jobs on the
On Mon, Oct 07, 2019 at 01:58:10PM +0200, Andrea Bolognani wrote:
> On Mon, 2019-10-07 at 12:13 +0100, Daniel P. Berrangé wrote:
> > Given this is only low/moderate maint cost, I'm tempted to be quite
> > generous to applications and say that in January each year, we purge
> > support for versions
On Mon, 2019-10-07 at 12:13 +0100, Daniel P. Berrangé wrote:
> Given this is only low/moderate maint cost, I'm tempted to be quite
> generous to applications and say that in January each year, we purge
> support for versions older than 5 years.
>
> This would imply...
>
> - Jan 2020 - purge
In at least the Python and Go bindings for libvirt we use conditional
compilation to allow the bindings to be build against old versions of
libvirt.
For Python this goes back to 0.9.11, from Apr 2012
For Go this goes back to 1.2.0, from Dec 2013
I'm wondering whether it would be worthwhile to
