Re: Time for 2.4.30? (Was: Re: 2.4.x STATUS needs you!)

And perhaps sufficient testing of the end result? The number of exceptions at the moment bode ill for a stable long term release. Feature dumps always introduce instability. Maybe a bug fix only freeze for a short period to stabilize that pile of code? On Feb 14, 2018 06:41, "Jim Jagielski"

Re: Time for 2.4.30? (Was: Re: 2.4.x STATUS needs you!)

On 14 Feb 2018, at 2:40 PM, Jim Jagielski wrote: > Yes... there are/were a few backports which are/were lacking > a single vote… We’re down to these ones left: +1: jim, minfrin +1: jailletc36, minfrin +1: minfrin Regards, Graham — smime.p7s Description:

Re: Time for 2.4.30? (Was: Re: 2.4.x STATUS needs you!)

Yes... there are/were a few backports which are/were lacking a single vote... > On Feb 13, 2018, at 1:23 PM, Nic Jansma wrote: > > Are there still plans to push for a 2.4.30 soon? There's a couple bug fixes > in it that I'd love to have in the official builds! > > Thanks, > >

Re: Time for 2.4.30? (Was: Re: 2.4.x STATUS needs you!)

Are there still plans to push for a 2.4.30 soon?  There's a couple bug fixes in it that I'd love to have in the official builds! Thanks, - Nic On 2018/01/04 12:43:12, Jim Jagielski wrote: > As we get settled into the new year, it seems a good time> > to think about a 2.4.30

Re: Time for 2.4.30? (Was: Re: 2.4.x STATUS needs you!)

+1 of course > Am 04.01.2018 um 13:43 schrieb Jim Jagielski : > > As we get settled into the new year, it seems a good time > to think about a 2.4.30 release in the coming week or > so. Lots of good stuff currently in 2.4.30-dev and even > more good stuff in STATUS awaiting a

Time for 2.4.30? (Was: Re: 2.4.x STATUS needs you!)

As we get settled into the new year, it seems a good time to think about a 2.4.30 release in the coming week or so. Lots of good stuff currently in 2.4.30-dev and even more good stuff in STATUS awaiting a single vote! Let's see if we can clean-up STATUS, get 2.4.30-dev into fantastic shape, and