Re: What is holding up 2.20 release?

[Jonas Hahnfeld]

Hi David,

Am Montag, den 18.11.2019, 18:10 +0100 schrieb Jonas Hahnfeld:
> Am Samstag, den 16.11.2019, 21:52 +0100 schrieb David Kastrup:
> > Carl Sorensen <
> > address@hidden
> > 
> > > writes:
> > > Dear Team,
> > > 
> > > It seems to me like we are pretty much in shape such that we should
> > > release 2.20.  I'd be fine if we called 2.19.83-1 the 2.20 release,
> > > even if there are some critical regressions.  2.19.83 is SO much
> > > better than 2.18.2.
> > > 
> > > IIUC, the only thing 2.20 is waiting on is for David K. to cherry-pick
> > > some patches.  Is that correct?
> > 
> > And putting out a new prerelease to be sure that those are ok, and
> > waiting for the translators to catch up with cherry-picked patches
> > containing stuff to be translated.
> > 
> > But the current roadblock is David K. cherry-picking some patches.  Here
> > is a remaining list (not completely up to date with current master,
> > though not missing much) to check for possible inclusion (assuming I
> > have not overlooked something important pickable in the sequence
> > before).  If you see something important here (or something not in
> > current master), put in a word for it.
> 
> Thanks for the list of candidates, I processed around half of it for
> now (+ some dependencies as mentioned below).
> All commits that I think should be "picked" are also readily available
> in my branch origin/dev/hahnjo/stable-2.20. Let me know if those are ok
> and I can easily push to stable/2.20.

I've noticed that you picked a handful of commits to stable/2.20 last
week. Does it still make sense for me to maintain my branch (and
continue going through the list) if you're doing the work yourself
anyhow?

Jonas

signature.asc
Description: This is a digitally signed message part