Comment 9 for bug 1558857

Quoting Stefan Bader (<email address hidden>):
> Well as it stands right now, at least the (admittedly more basic things)
> stuff I do run is working with 1.3.1. So I cannot add any exciting
> arguments. And upstream tends to always recommend "the latest stuff", so
> next week this could be 1.3.3. ;)

Right, that's my feeling.

> Technically it looks possible but with the risk of being beyond Debian
> right now. Which has a few challenges on the packaging side (mostly to
> ensure it is clear where things came from) but also the normal approach
> for a LTS release is to be a little more conservative about latest and
> greatest as that also means not that well tested/settled.
>
> So I personally would be hesitant unless there are even more specific

Right, wanted to make sure you didn't know of any current bad xen issues.

> reasons like 1.3.2 allows to do x and that will be important because of
> this reason. The problem is/was that newer not only means fixes but also
> new breakage. So I rather stick to a reasonable pace and want to see
> very good reasons to move fast(er) (besides not being the runner type
> anyways ;)).

Agreed. Thanks, Stefan.