On Thu, Jan 17, 2013 at 11:51 AM, Martin Gräßlin mgraess...@kde.org wrote:
On Thursday 17 January 2013 11:22:04 David Edmundson wrote:
This morning I spent an hour going through the list of general, I
found a few problems.
There were several bugs I looked at where the relevant component
On Sunday 13 January 2013 15:50:25 Martin Gräßlin wrote:
*Restrict the available version numbers*
At KWin we only allow bugs to be reported for:
* the latest beta/RC
* the last two minor versions of the current stable
* the last two minor version of the last stable
I just implemented this
On Sun, Jan 13, 2013 at 2:50 PM, Martin Gräßlin mgraess...@kde.org wrote:
Hi all,
*warning* long mail! Please take time reading it. Given how long I am now
writing on it: schedule half an hour or so ;-)
I will try to formulate some thoughts on what I think might help to improve
the Quality
In data giovedì 17 gennaio 2013 11:22:04, David Edmundson ha scritto:
backtrace it's impossible to see who's at fault. The backtrace only
shows some timer firing, or a python binding call or something generic
- it's impossible to tell what's at fault. I have no idea how we can
fix this.
On Thursday 17 January 2013 11:22:04 David Edmundson wrote:
This morning I spent an hour going through the list of general, I
found a few problems.
There were several bugs I looked at where the relevant component
didn't exist (webslice plasmoid, timer plasmoid).
All plasmoids should have a
On Thursday 17 January 2013 12:30:03 Luca Beltrame wrote:
In data giovedì 17 gennaio 2013 11:22:04, David Edmundson ha scritto:
backtrace it's impossible to see who's at fault. The backtrace only
shows some timer firing, or a python binding call or something generic
- it's impossible to
On Monday, January 14, 2013 17:11:31 Martin Gräßlin wrote:
On Monday 14 January 2013 16:24:28 Aaron J. Seigo wrote:
Whoever is maintainer of a component, should become the
default assignee for bugs in that component. No longer a one address for
all assignee.
i think the maintainer
On Monday, January 14, 2013 17:22:14 Martin Gräßlin wrote:
On Monday 14 January 2013 16:24:28 Aaron J. Seigo wrote:
a merge commit can document exactly what it is merging, feature or bug
fix,
and that can also be used to generate a changelog.
that's a good point. Sounds like a reasonable
On Monday, January 14, 2013 23:03:03 David Edmundson wrote:
On Mon, Jan 14, 2013 at 3:24 PM, Aaron J. Seigo ase...@kde.org wrote:
we need some people who use master, but aren't responsible for writing
(much) code, doing this work. otherwise those writing the code will
simply get nothing
of course I have forgotten to mention one suggestion.
In KWin we added a totally awesome feature to get introspection on the running
instance. If you have not seen it yet, just try:
qdbus org.kde.kwin /KWin supportInformation
This significantly improved the time we spent on bug reports. Instead
On 14/01/13 10:22, Martin Gräßlin wrote:
I think this would also be interesting for Plasma:
* which Plasmoids are running
* which containments are present
* what are the settings of each Plasmoid
Note that there are potential privacy issues here. Unlike KWin, there is
a fair chance that
On Monday 14 January 2013 11:42:10 Alex Merry wrote:
On 14/01/13 10:22, Martin Gräßlin wrote:
I think this would also be interesting for Plasma:
* which Plasmoids are running
* which containments are present
* what are the settings of each Plasmoid
Note that there are potential privacy
Not going to quote... Long emails are long :p
I pretty much agree and will feel comfortable working with this process,
besides the bug for feature part, we have been doing the same in solid, for
example in kscreen right now we have:
6 bugs as NeedInfo, waiting
3 wishes in Unconfirmed
Similar
On Sunday 13 January 2013 15:50:25 Martin Gräßlin wrote:
*Every commit should be referenced to a bug*
What is the motivation for a commit? It's either a bug fix or it is a new
feature/improvement. If it's a bug it's clear that there has to be a bug
report for it (out of experience: there is
On Sunday, January 13, 2013 15:50:25 Martin Gräßlin wrote:
I think the problem with our QM process is, that we don't have a tool to
support it. Our bugtracker is (in it's current state) totally useless. Let
me just show a few stats for Plasma:
the difference betwen Plasma and KWin components
On 14/01/13 15:21, Alex Fiestas wrote:
On Sunday 13 January 2013 15:50:25 Martin Gräßlin wrote:
*Every commit should be referenced to a bug*
What is the motivation for a commit? It's either a bug fix or it is a new
feature/improvement. If it's a bug it's clear that there has to be a bug
report
On Monday 14 January 2013 16:21:04 Alex Fiestas wrote:
On Sunday 13 January 2013 15:50:25 Martin Gräßlin wrote:
*Every commit should be referenced to a bug*
What is the motivation for a commit? It's either a bug fix or it is a new
feature/improvement. If it's a bug it's clear that there has
On Monday 14 January 2013 16:24:28 Aaron J. Seigo wrote:
Whoever is maintainer of a component, should become the
default assignee for bugs in that component. No longer a one address for
all assignee.
i think the maintainer should be added as a default CC, but if each
component goes to a
On Monday 14 January 2013 16:24:28 Aaron J. Seigo wrote:
*Every commit should be referenced to a bug*
What is the motivation for a commit? It's either a bug fix or it is a new
feature/improvement. If it's a bug it's clear that there has to be a bug
report for it (out of experience: there
On 14/01/13 15:24, Aaron J. Seigo wrote:
* it means adopting bugzilla as our One True Workflow tool. that doesn't just
sound beaurocratic, it is beaurocratic. if someone appears with a patch fixing
some bug or implementing some feature that isn't in bugzilla, do we first send
them to create one
On Tue, Jan 15, 2013 at 5:11 AM, Martin Gräßlin mgraess...@kde.org wrote:
On Monday 14 January 2013 16:24:28 Aaron J. Seigo wrote:
Whoever is maintainer of a component, should become the
default assignee for bugs in that component. No longer a one address for
all assignee.
i think the
On Mon, Jan 14, 2013 at 3:24 PM, Aaron J. Seigo ase...@kde.org wrote:
On Sunday, January 13, 2013 15:50:25 Martin Gräßlin wrote:
I think the problem with our QM process is, that we don't have a tool to
support it. Our bugtracker is (in it's current state) totally useless. Let
me just show a
Hi all,
*warning* long mail! Please take time reading it. Given how long I am now
writing on it: schedule half an hour or so ;-)
I will try to formulate some thoughts on what I think might help to improve
the Quality Management in Plasma. Some ideas are based on what works well in
KWin.
23 matches
Mail list logo
