On Wed, May 27, 2020 at 02:03:34PM -0700, Brian Murray wrote:
> On Fri, Aug 30, 2019 at 12:29:35PM +0100, Robie Basak wrote:
> > Thank you everyone for the feedback.
> > On Wed, Aug 28, 2019 at 07:41:10PM +0200, Matthias Klose wrote:
> > > afaiu block-proposed tags on bugs are not specific to any
On Fri, Aug 30, 2019 at 12:29:35PM +0100, Robie Basak wrote:
> Thank you everyone for the feedback.
>
> On Wed, Aug 28, 2019 at 07:41:10PM +0200, Matthias Klose wrote:
> > afaiu block-proposed tags on bugs are not specific to any series, so you are
> > blocking updates across all series. Not reall
Discussion seems to have concluded on this thread, and I've seen quite a
bit of use of the block-proposed- tag now.
We (the SRU team) decided to continue with this feature, so I've
adjusted the SRU documentation to match:
Policy:
https://wiki.ubuntu.com/StableReleaseUpdates#Staging_low_priority_u
On Tue, Oct 22, 2019 at 12:30:34PM -0300, Rafael David Tinoco wrote:
> > > afaiu block-proposed tags on bugs are not specific to any series, so you
> > > are
> > > blocking updates across all series. Not really desired.
> > Following the thread you started, it seems that we can all agree to use
>
afaiu block-proposed tags on bugs are not specific to any series, so you are
blocking updates across all series. Not really desired.
Following the thread you started, it seems that we can all agree to use
block-proposed- instead. Does this resolve your concern?
On Wed, Aug 28, 2019 at 09:24:10
Thank you everyone for the feedback.
On Wed, Aug 28, 2019 at 07:41:10PM +0200, Matthias Klose wrote:
> afaiu block-proposed tags on bugs are not specific to any series, so you are
> blocking updates across all series. Not really desired.
Following the thread you started, it seems that we can all
Currently sru-report shows the block icon for both block-proposed and
block-proposed-SERIES. Seeing that block-proposed is indeed
devel-specific, I think it makes sense for us to only block SRU
uploads on the -SERIES tag. I can switch that in a moment if there's
an agreement on that in the SRU team
On Thu, Aug 29, 2019 at 10:33:37AM +0200, Julian Andres Klode wrote:
> On Thu, Aug 29, 2019 at 03:59:04AM +0100, Colin Watson wrote:
> > On Wed, Aug 28, 2019 at 07:41:10PM +0200, Matthias Klose wrote:
> > > afaiu block-proposed tags on bugs are not specific to any series, so you
> > > are
> > > bl
On Thu, Aug 29, 2019 at 03:59:04AM +0100, Colin Watson wrote:
> On Wed, Aug 28, 2019 at 07:41:10PM +0200, Matthias Klose wrote:
> > On 28.08.19 19:32, Robie Basak wrote:
> > > Any comments on this plan? If there are no objections, I'll update the
> > > wiki page documentation to match.
> >
> > afa
On Wed, Aug 28, 2019 at 07:41:10PM +0200, Matthias Klose wrote:
> On 28.08.19 19:32, Robie Basak wrote:
> > Any comments on this plan? If there are no objections, I'll update the
> > wiki page documentation to match.
>
> afaiu block-proposed tags on bugs are not specific to any series, so you are
On Wed, Aug 28, 2019 at 06:32:13PM +0100, Robie Basak wrote:
> Finally, please note that it is essential to carry out SRU verification
> on the bug as usual as soon as it enters proposed because we do not want
> to burden a future SRUer with verification of your bug. If timely
> verification is not
On 28.08.19 19:32, Robie Basak wrote:
Any comments on this plan? If there are no objections, I'll update the
wiki page documentation to match.
afaiu block-proposed tags on bugs are not specific to any series, so you are
blocking updates across all series. Not really desired.
Matthias
--
ubu
Dear Ubuntu Developers,
Some members of the SRU team, myself included, have been reluctant to
accept SRUs that do not solve any specific problem from a user
perspective due to the unnecessary burden this would impose on users. An
example of this is an autopkgtest fix.
We wrote this up recently at
13 matches
Mail list logo
