On Wed, May 31, 2017 at 10:09:26AM +0200, Lukas Slebodnik wrote:
> On (31/05/17 08:19), Lachlan Musicman wrote:
> >Hi all,
> >I noticed a while ago that 1.15.3 was versioned in the repo but I've not
> >seen anything released? I'm mostly looking on the COPR
c/ 012ee7c3fe24a5e75d9b0465268c1b b8187b8337?branch=master
> Version is immediately increased in git to simplify life for developers.
> 1.15.3 is still a devel version and not official.
> BTW 1.15.2 is in copr for some time
> >This is purely selfish - I love all that you do, and I'm aware that there
> >has been some fairly comprehensive infrastructural change.
> >I'm just waiting on that one fix and have no roadmap visibility :)
> Which fix do you mean?
I suspect it's #3382 -- this bug hit quite a few people, do you think
it's a good idea to regenerate the copr with 1.15.2 and this fix?
on the other hand, 1.15.3 is not far away (promise :-))