Yep, if it's currently merged it's in. I mean, I guess we could find a
horrible bug in testing that would force us to back it out, but I doubt
that will happen.
On Wed, Sep 20, 2017 at 10:51 AM, Ralph Bean <rbean(a)redhat.com> wrote:
On Tue, Sep 19, 2017 at 09:44:53PM -0400, Michael McLean wrote:
> We're finishing up the 1.14.0 release this week. We're not planning any
> more significant changes. The rest of this week we'll be focused on final
> release prep, mainly docs and testing.
>
> Unfortunately, a few things did not land in time. These will be
prioritized
> in 1.15.0.
>
> Here's the current roadmap for the release:
>
https://pagure.io/koji/roadmap?status=all&milestone=1.14&all_ston...
>
> Here are the issues that have been deferred to 1.15
> -
https://pagure.io/koji/issue/458 pypi
> -
https://pagure.io/koji/issue/457 dist repo expire
> -
https://pagure.io/koji/issue/495 Makefile cleanup
> -
https://pagure.io/koji/issue/409 dist repos enhancements
Thanks Mike!
Will the repo_include_all option make it in?
https://pagure.io/koji/pull-request/590
_______________________________________________
koji-devel mailing list -- koji-devel(a)lists.fedorahosted.org
To unsubscribe send an email to koji-devel-leave(a)lists.fedorahosted.org