Bugzilla change - adding regression as a keyword
Hi, At Chris Nighswonger's request, I've set up a way to mark a bug as a regression. Specifically, I've defined a bugzilla keyword, "regression". This has the effect of adding a keyword field on the bug entry form and the bug search form. Please see bug 4867 for an example. There are a couple other ways we could choose to mark bugs as regressions, e.g., by defining a new severity or priority. Feedback welcome. Regards, Galen -- Galen Charlton gmcharlt@gmail.com
Galen, By "regression" do you intend it to mean: "arrested development: an abnormal state in which development has stopped prematurely" OR do you mean: "currently on hold" ??? Thanks, Irma On 15/09/2010 1:21 AM, Galen Charlton wrote:
Hi,
At Chris Nighswonger's request, I've set up a way to mark a bug as a regression. Specifically, I've defined a bugzilla keyword, "regression". This has the effect of adding a keyword field on the bug entry form and the bug search form. Please see bug 4867 for an example.
There are a couple other ways we could choose to mark bugs as regressions, e.g., by defining a new severity or priority. Feedback welcome.
Regards,
Galen
-- Irma Birchall CALYX information essentials Koha & Kete implementations and services T:(02) 80061603 M: 0413 510 717 _irma@calyx.net.au_ <mailto:irma@calyx.net.au> _www.calyx.net.au_ <http://www.calyx.net.au/> _http://koha-community.org/_ _http://kete.net.nz/_
2010/9/15 Irma Birchall <irmalibraries@gmail.com>:
Galen, By "regression" do you intend it to mean: "arrested development: an abnormal state in which development has stopped prematurely" OR do you mean: "currently on hold" ???
Hi Irma In computer science parlance, a regression bug is one that has broken previously functional behaviour. It has actually regressed "regressed" past participle, past tense of re·gress (Verb) 1. Return to a former or less developed state. In that sense. When you get a code base the size of Koha, you often to see these type of bugs, where someone has fixed, or added something new and in the process broken something that previously worked. Whenever this happens, we should do two things, 1/ revert the change that broke it, fix that and then re apply it 2/ write a unit test so that we can test programmatically that the previous broken thing is now working (and can test it is still working from now and into the future. Chris
Op woensdag 15-09-2010 om 11:43 uur [tijdzone +1000], schreef Irma Birchall:
By "regression" do you intend it to mean: "arrested development: an abnormal state in which development has stopped prematurely" OR do you mean: "currently on hold" ???
In software development, a "regression" is when something has regressed. That is, gone from working to not working. So, if adding new borrowers works now, and you upgrade and it stops, that's a regression. So, of your two, it's closest to the first one. They're usually considered to be pretty important because everyone hates when things that did work break, compared to some new feature that you weren't relying on not being quite right. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
Hi, 2010/9/14 Irma Birchall <irmalibraries@gmail.com>:
By "regression" do you intend it to mean: "arrested development: an abnormal state in which development has stopped prematurely" OR do you mean: "currently on hold" ???
Chris and Robin explained it well - a "regression" is a bug where that which was working now does not, to much wailing and gnashing of teeth. :) Regards, Galen -- Galen Charlton gmcharlt@gmail.com
Le 14/09/2010 17:21, Galen Charlton a écrit :
Hi,
At Chris Nighswonger's request, I've set up a way to mark a bug as a regression. Specifically, I've defined a bugzilla keyword, "regression". This has the effect of adding a keyword field on the bug entry form and the bug search form. Please see bug 4867 for an example.
There are a couple other ways we could choose to mark bugs as regressions, e.g., by defining a new severity or priority. Feedback welcome.
Regards,
Galen I warmly welcome this new status.
participants (5)
-
Chris Cormack -
Galen Charlton -
Irma Birchall -
LAURENT -
Robin Sheat