Re: [Ubuntu-bugcontrol] Stop triaging bugs

[Pierre Equoy]

On Wed, Mar 26, 2014 at 12:15 AM, Alberto Salvia Novella <
es204904...@gmail.com> wrote:

> El 25/03/14 17:02, Brian Murray escribió:
>
>  What particular bug number was this message regarding?
>>
> Marc was referring to the following work-flow 
> (security bugs with an status of "new").
>
>
Would it be possible for the security team to update this workflow to:
security bugs with status in ("New", "Triaged")
?

That would be a request like this:
https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&search=Search&field.status%3Alist=NEW&field.status%3Alist=TRIAGED&field.information_type%3Alist=PUBLICSECURITY&field.information_type%3Alist=PRIVATESECURITY&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.component-empty-marker=1&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&orderby=-importance&memo=75&start=0&direction=backwards

(I took the previous one and added issues with a "TRIAGED" status)

Cheers,


-- 
Pierre Equoy
-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: [Bug 1285801] Re: virtuoso-t crashed with SIGSEGV on system startup

[Alberto Salvia Novella]

El 25/03/14 23:32, Brian Murray escribió:

Could you please provide some more information about this particular
situation so we can better provide advice?

Perhaps Obey can.

--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: [Ubuntu-bugcontrol] Stop triaging bugs

[Serge Hallyn]

Switching to using tags instead of status to manage the workflow might
be less likely to get trampled on, but only so much.

Would it interfere with the workflow to have the bugs assigned to Ubuntu
Security Team (regardless of status)?  I don't think anyone would touch
a bug assigned to them...

Quoting Alberto Salvia Novella (es204904...@gmail.com):
> El 25/03/14 17:02, Brian Murray escribió:
> >What particular bug number was this message regarding?
> Marc was referring to the following work-flow
>  (security bugs with an status of
> "new").

> -- 
> Ubuntu-bugsquad mailing list
> ubuntu-bugsq...@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad


-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Fwd: Re: [Bug 1285801] Re: virtuoso-t crashed with SIGSEGV on system startup

[Brian Murray]

On Sun, Mar 23, 2014 at 06:53:18PM +0100, Alberto Salvia Novella wrote:
> What shall be done in this case?

Could you please provide some more information about this particular
situation so we can better provide advice?

--
Brian Murray
Ubuntu Bug Master

-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Fwd: [Ubuntu-phone] Call For Testing: Split Greeter

[Nicholas Skaggs]

 Original Message 
Subject:[Ubuntu-phone] Call For Testing: Split Greeter
Date:   Tue, 25 Mar 2014 09:50:20 -0400
From:   Michael Terry 
To: Ubuntu Touch 



Hello! Â The split greeter feature is almost ready, so I wanted to get 
some wider testing.


The "split greeter feature" refers to moving the welcome screen out of 
the unity8 executable and into its own process, managed by LightDM as a 
proper system greeter. Â (This is necessary for proper security and 
supporting multiple users.)


Note that the only visual change is going to be the boot animation. 
 Everything else is under-the-hood changes.  So prepare to be 
underwhelmed (hopefully -- ideally you're not whelmed by bugs).


I'd especially appreciate testing around interactions between the 
greeter and the rest of the system (phone calls, texts, launching apps, 
unlocking sim card).


Here's how to test:
$ ubuntu-device-flash --channel=trusty-proposed
$ adb shell
# add-apt-repository ppa:ci-train-ppa-service/landing-004
# apt-get update
# apt-get dist-upgrade
# exit
$ adb reboot

Known Mir bugs in this PPA being worked on:
- Screen turns on again by itself after being turned off -- turning back 
on and off will fix temporarily
- Entering text in OSK keyboard "passes through" and also acts as clicks 
in shell. Â And it won't dismiss. Â So be careful about using keyboard.


Other issues not yet represented in that PPA:
- Final boot animation (it will use Ubuntu logo instead of spinner)
- Sliding greeter aside animation will look nicer (right now it looks 
like greeter is a flat sheet on top of session)


--
-mt


-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-ph...@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: [Ubuntu-bugcontrol] Stop triaging bugs

[Alberto Salvia Novella]

El 25/03/14 17:02, Brian Murray escribió:

What particular bug number was this message regarding?
Marc was referring to the following work-flow 
 (security bugs with an status of "new").

--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Stop triaging bugs

[Jack Ramsay]

On Mar 24, 2014 10:02 AM, "Alberto Salvia Novella" 
wrote:
>
> El 24/03/14 14:47, Marc Deslauriers escribió:
>>
>> On 14-03-24 09:37 AM, Alberto Salvia Novella wrote:
>>>
>>> El 24/03/14 13:31, Marc Deslauriers escribió:

 Could you please stop changing statuses of bugs you don't intend on
fixing yourself?

 Marking a bug as "triaged" and changing priorities on them makes
absolutely no
 sense if you aren't tasked to fix them.

 Changing one of my team's bugs to "triaged" means our scripts and
procedures no
 longer consider the bug to be new, hence, nobody will look at it
anymore. It is
 breaking our workflow.
So couldn't launchpad do something about that? Couldn't it be set up to
where triaged bugs still show as new? Honestly that way we can triage bugs
and that way they won't be missed when a team member is looking at the new
bugs. I honestly don't think we should stop triaging bugs.
>>> As said in the bug statuses 
page,
>>> which arbitrates the hole bug management work-flow in Launchpad,
"triaged" means
>>> "a member of UbuntuBugControl 
>>> believes that the report describes a genuine bug in enough detail that a
>>> developer could start working on a fix."
>>>
>>> Moreover, according to lean management
>>> :
>>>
>>>* The first source of flaws (or any waste) is them to remain
invisible (or
>>>  untriaged or with unset priority in the case of bug management).
>>>* Unpredictable work-flow has to be done manually till, after some
continuous
>>>  improvement and waste reduction, it becomes regular.
>>>
>>> So, since your work-flow conflicts with Launchpad's one and with
principal
>>> productivity recommendations, I'm sorry I'm not taking on your request;
except
>>> if I'm missing something.
>>>
>> (...)
>> Modifying in an arbitrary way bug statuses and priorities that teams
depend on
>> to track work is simply a bad idea.
>> (...)
>
> What do you think; Quality, BugSquad and BugControl; about this topic?
>
> --
> Ubuntu-bugsquad mailing list
> ubuntu-bugsq...@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Stop triaging bugs

[Maarten Bezemer]

On Monday 24 March 2014 16:01:48 Alberto Salvia Novella wrote:
> El 24/03/14 14:47, Marc Deslauriers escribió:
> > On 14-03-24 09:37 AM, Alberto Salvia Novella wrote:
> >> El 24/03/14 13:31, Marc Deslauriers escribió:
> >>> Could you please stop changing statuses of bugs you don't intend on
> >>> fixing yourself?
> >>> 
> >>> Marking a bug as "triaged" and changing priorities on them makes
> >>> absolutely no sense if you aren't tasked to fix them.
> >>> 
> >>> Changing one of my team's bugs to "triaged" means our scripts and
> >>> procedures no longer consider the bug to be new, hence, nobody will
> >>> look at it anymore. It is breaking our workflow.
> >> 
> >> As said in the bug statuses 
> >> page, which arbitrates the hole bug management work-flow in Launchpad,
> >> "triaged" means "a member of UbuntuBugControl
> >>  believes that the report
> >> describes a genuine bug in enough detail that a developer could start
> >> working on a fix."
> >> 
> >> Moreover, according to lean management
> >> 
> >> :
> >>* The first source of flaws (or any waste) is them to remain invisible
> >>(or
> >>
> >>  untriaged or with unset priority in the case of bug management).
> >>
> >>* Unpredictable work-flow has to be done manually till, after some
> >>continuous>>
> >>  improvement and waste reduction, it becomes regular.
> >> 
> >> So, since your work-flow conflicts with Launchpad's one and with
> >> principal
> >> productivity recommendations, I'm sorry I'm not taking on your request;
> >> except if I'm missing something.
> > 
> > (...)
> > Modifying in an arbitrary way bug statuses and priorities that teams
> > depend on to track work is simply a bad idea.
> > (...)
> 
> What do you think; Quality, BugSquad and BugControl; about this topic?

Each group uses the status (and other) field(s) for their own use. Depending on 
the bug and where it is send to, one should use the definitions of the group 
responsible. In this case the bugs (apparently) belong to a group that use 
different 'definitions' of the status field, than Bug Squat does.

I have seen information on different uses of the bug fields somewhere on 
wiki.ubuntu.com but I cannot find it anymore..?
I suppose this needs to be made more clear on 
https://wiki.ubuntu.com/Bugs/Bug%20statuses maybe with a list of links to the 
other groups and their descriptions/use of the fields.

Regards,
  Maarten

-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: [Ubuntu-bugcontrol] Stop triaging bugs

[Brian Murray]

On Mon, Mar 24, 2014 at 04:01:48PM +0100, Alberto Salvia Novella wrote:
> El 24/03/14 14:47, Marc Deslauriers escribió:
> >On 14-03-24 09:37 AM, Alberto Salvia Novella wrote:
> >>El 24/03/14 13:31, Marc Deslauriers escribió:
> >>>Could you please stop changing statuses of bugs you don't intend on fixing 
> >>>yourself?
> >>>
> >>>Marking a bug as "triaged" and changing priorities on them makes 
> >>>absolutely no
> >>>sense if you aren't tasked to fix them.
> >>>
> >>>Changing one of my team's bugs to "triaged" means our scripts and 
> >>>procedures no
> >>>longer consider the bug to be new, hence, nobody will look at it anymore. 
> >>>It is
> >>>breaking our workflow.
> >>As said in the bug statuses  
> >>page,
> >>which arbitrates the hole bug management work-flow in Launchpad, "triaged" 
> >>means
> >>"a member of UbuntuBugControl 
> >>believes that the report describes a genuine bug in enough detail that a
> >>developer could start working on a fix."
> >>
> >>Moreover, according to lean management
> >>:
> >>
> >>   * The first source of flaws (or any waste) is them to remain invisible 
> >> (or
> >> untriaged or with unset priority in the case of bug management).
> >>   * Unpredictable work-flow has to be done manually till, after some 
> >> continuous
> >> improvement and waste reduction, it becomes regular.
> >>
> >>So, since your work-flow conflicts with Launchpad's one and with principal
> >>productivity recommendations, I'm sorry I'm not taking on your request; 
> >>except
> >>if I'm missing something.
> >>
> >(...)
> >Modifying in an arbitrary way bug statuses and priorities that teams depend 
> >on
> >to track work is simply a bad idea.
> >(...)
> What do you think; Quality, BugSquad and BugControl; about this topic?

It's hard to have an opinion on something without complete details of
the situation. What particular bug number was this message regarding?

--
Brian Murray

-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Fwd: Trusty Tahr Final Beta Freeze

[Alberto Salvia Novella]

El 25/03/14 03:18, Nicholas Skaggs escribió:

(...)
If you need help testing the images check out the links on the top of the
milestone page, they are there to help. The goal is to verify the images in
preparation for the release. Find those bugs!
(...)

>

Alternatively, if you belong to BugControl, you can help on routing 
these bugs using:



So they get proper attention.

--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Fwd: Trusty Tahr Final Beta Freeze

[Alberto Salvia Novella]

El 25/03/14 03:18, Nicholas Skaggs escribió:

(...)
If you need help testing the images check out the links on the top of the
milestone page, they are there to help. The goal is to verify the images in
preparation for the release. Find those bugs!
(...)

>

Alternatively, if you belong to BugControl, you can help on routing 
these bugs using:



So they get proper attention.

--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality