Re: Bodhi 2.4.0 released upstream

On Wed, 15 Feb 2017 22:11:14 -0500 Randy Barlow wrote: > On Wed, 2017-02-15 at 16:58 -0500, Randy Barlow wrote: > > https://github.com/fedora-infra/bodhi/releases/tag/2.4.0 > > I've been unable to build Bodhi in Rawhide, due to a packaging bug > with python-dogpile-cache: > > https://bugzilla

Re: Bodhi 2.4.0 released upstream

On Wed, Feb 15, 2017 at 10:11:14PM -0500, Randy Barlow wrote: > On Wed, 2017-02-15 at 16:58 -0500, Randy Barlow wrote: > > https://github.com/fedora-infra/bodhi/releases/tag/2.4.0 > > I've been unable to build Bodhi in Rawhide, due to a packaging bug with > python-dogpile-cache: > > https://bugzi

Re: Bodhi 2.4.0 released upstream

On Wed, 2017-02-15 at 15:46 -0800, Adam Williamson wrote: > New releases are traditionally deployed direct to production at > 5:30pm > on Friday, just before you leave for a long vacation with no internet > access. Everyone knows this! Sage advice! signature.asc Description: This is a digitally s

Re: Bodhi 2.4.0 released upstream

On Wed, 2017-02-15 at 16:58 -0500, Randy Barlow wrote: > https://github.com/fedora-infra/bodhi/releases/tag/2.4.0 I've been unable to build Bodhi in Rawhide, due to a packaging bug with python-dogpile-cache: https://bugzilla.redhat.com/show_bug.cgi?id=1422716 That package can only be committed t

Re: Bodhi 2.4.0 released upstream

On Wed, 15 Feb 2017 16:58:09 -0500 Randy Barlow wrote: > Hello! > > I've made a release of Bodhi 2.4.0 upstream: > > https://github.com/fedora-infra/bodhi/releases/tag/2.4.0 > > What guidance would this group give about deploying it tomorrow > (Thursday) vs. waiting until next Monday? Sooner

Re: Bodhi 2.4.0 released upstream

On Wed, 2017-02-15 at 16:58 -0500, Randy Barlow wrote: > Hello! > > I've made a release of Bodhi 2.4.0 upstream: > > https://github.com/fedora-infra/bodhi/releases/tag/2.4.0 > > What guidance would this group give about deploying it tomorrow > (Thursday) vs. waiting until next Monday? New relea