Kia ora
Everything is moved, there is just an issue with the dns, but once
that is sorted the new site should be available
Chris
On Mon, 9 Jun 2025 at 09:18, Chris Cormack wrote:
>
> Mōrena
>
> Bugzilla will be down for a bit today as I shift it to the new server.
> I will email with updates wh
Kia ora anō
The move is completed, please let me know if you spot anything weird happening
Chris
On Mon, 9 Jun 2025 at 10:47, Chris Cormack wrote:
>
> Kia ora
>
> Everything is moved, there is just an issue with the dns, but once
> that is sorted the new site should be available
>
> Chris
>
> O
On 20-06-09 19:47, Jonathan Druart wrote:
> To not have this status now? What do you mean?
> The status exists, you can switch to oldoldstable only if pushed to oldstable.
I see, the status wasn't updated with "pushed to oldstable", that why I
couldn't see it.
No worries then.
--
Victor Grouss
To not have this status now? What do you mean?
The status exists, you can switch to oldoldstable only if pushed to oldstable.
Le mar. 9 juin 2020 à 19:38, Victor Grousset/tuxayo
a écrit :
>
> Hi,
>
> I suppose there is a reason to not have this status now?
> Since oldoldstable is used since a lon
Hi Barton,
That could certainly be done easily using Greasemonkey.
Let me know if you need help.
Cheers,
Jonathan
Le mar. 27 nov. 2018 à 20:26, Barton Chittenden
a écrit :
>
> Is there any way to change the default statuses on the bugzilla advanced
> search page? https://bugs.koha-community.org/b
Thanks Katrin and Jonathan!
That is a much better way.
David
David Nind | david.n...@gmail.com
PO Box 12367, Thorndon, Wellington, New Zealand 6144
m. +64 21 0537 847
On 14 April 2018 at 02:11, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:
> As Katrin said, you should refer
As Katrin said, you should refer to the release notes instead:
https://gitlab.com/koha-community/koha-release-notes/blob/master/release_notes_17_12_00.md
I generate them after (almost) each push
On Thu, 12 Apr 2018 at 19:26 Katrin Fischer
wrote:
> Hi David,
>
> a few enhancements have been back
Hi David,
a few enhancements have been back ported, so they will be 'pushed to
stable'. When including "pushed to stable" the number goes up from 209
to 361, which seems a bit much.
Maybe working from pre-release notes would be easier as it reads the
bugs pushed from git. Let me know if I ca
* Chris Cormack (ch...@bigballofwax.co.nz) wrote:
> Hi All
>
> Linode have discovered a hardware issue on the machine my linode is hosted
> on, they are working on a fix, but things will be up and down until then
>
All back now
Chris
--
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-05
* Chris Cormack (ch...@bigballofwax.co.nz) wrote:
> Hi All
>
> I will be taking the bugs.koha-community.org server down for some
> maintenance, it is behaving a bit oddly.
>
> I will let you know when things are back
>
Things are back now, I think it is behaving better
Please let me know if you
* Chris Cormack (ch...@bigballofwax.co.nz) wrote:
> Hi All
>
> I will be taking the bugs.koha-community.org server down for some
> maintenance, it is behaving a bit oddly.
>
> I will let you know when things are back
>
Further to this,
I was seeing segfaults, so while investigating this, I too
Its amazing how much of our world Linode controls. :-)
Chris
On Mar 2, 2015 10:44 AM, "Galen Charlton" wrote:
> Hi,
>
> On Sun, Mar 1, 2015 at 9:54 PM, Chris Cormack
> wrote:
> > Linode are rebooting all of their xen servers which will mean the VM that
> > bugzilla and a bunch of other Koha sit
Hi,
On Sun, Mar 1, 2015 at 9:54 PM, Chris Cormack wrote:
> Linode are rebooting all of their xen servers which will mean the VM that
> bugzilla and a bunch of other Koha sites and tools run on will disappear for
> a couple of hours.
>
> It will be rebooted at
> 2015-03-07 6:00:00 PM UTC
>
> They
The Koha website, also in Linode, will also experience an outage:
* 2015-03-07 2:00:00 AM UTC
It also has a 2 hour window, but it may not be down that long.
Cheers,
Liz
On 02/03/15 15:54, Chris Cormack wrote:
> Hi All
>
> Linode are rebooting all of their xen servers which will mean the VM that
>
>
> It's much easier to remember to set the complexity setting if you use
> git-bz, so I recommend it!
>
> If anyone who submits patches doesn't use git-bz yet please give it a
> try and ask for help if you run into trouble. It's really worth the
> effort.
>
>
Is there a complete list of options
> In the process of signoff or QA, it is helpful to see rightaway the author
> of the report and its supposed complexity (size).
It's much easier to remember to set the complexity setting if you use
git-bz, so I recommend it!
If anyone who submits patches doesn't use git-bz yet please give it a
t
On 19 April 2014 21:18, Chris Cormack wrote:
> Bugzilla has released a security update which has been applied
>
> http://www.bugzilla.org/security/4.0.11/
>
> This means that git-bz will need to be patched to work correctly using the
> token, until then git bz attach will not work.
>
This is the
Hi,
On Sun, Oct 27, 2013 at 11:29 PM, Chris Cormack wrote:
> There was another security issue with bugzilla that has been fixed,
> unfortunately it was a CSRF issue, which has meant that git bz needs
> to be updated to deal with tokens better.
>
> Until git-bz is fixed, the attach will no longer
Thanks, Galen -- that did it.
I'd seen that but it wasn't clear that it would also change the login.
Should have simply tried it!
Cheers,
Cab Vinton
On Thu, Sep 12, 2013 at 3:36 PM, Galen Charlton wrote:
> Hi Cab,
>
>
> On Thu, Sep 12, 2013 at 12:29 PM, Cab Vinton wrote:
>>
>> The login appe
Hi Cab,
On Thu, Sep 12, 2013 at 12:29 PM, Cab Vinton wrote:
> The login appears to be locked to my old work email address, however.
>
If you log into Bugzilla, go to Preferences, then to Account Information,
it should give you an option to set a new email address. Please let me
know if this d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've noticed on some websites (including Koha), pasting in without
putting something in manually like a space doesn't seem to activate the
submit buttons. You might try pasting, then hitting the space bar or
something and see if that helps.
Cheers,
L
Le 03/07/2013 13:59, Marcel de Rooy a écrit :
> Hi all,
> I recently (last update?) and regularly have trouble with Reply on Bugzilla.
> It does sometimes no longer paste the comment in the text box.
> Anyone else having this too? Or found a way to resolve it?
Yep, I sometimes have this problem as
On Mon, Nov 26, 2012 at 8:44 AM, Paul Poulain wrote:
> bugzilla > Preferences > General Preferences > After changing a bug
> "Show the updated bug"
>
Thank you so much I thought it was just the way Koha's bugzilla was :)
Nicole
___
Koha-devel maili
Hi Nicole,
check your permissions – there is a setting where you can change what happens
after you save a change.
Hope that helps,
Katrin
From: koha-devel-boun...@lists.koha-community.org
[mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Nicole Engard
Sent: Mon
Le 26/11/2012 14:39, Nicole Engard a écrit :
> Right now when you comment on a bug in Bugzilla it saves your change and
> shows the next bug in the search on the screen. Often I need to make a
> couple edits and this makes me change the wrong bug report (an error
> I've seen others make as well).
Paul Poulain
> What about adding separating "enhancements" in "enhancement" (of an
> existing feature) and "New feature" by adding the "new feature" to
> severity list ?
OK, but I fear it makes it even more confusing for users that aren't
also developers. Can they be next to each other and maybe
On Thu, Nov 15, 2012 at 11:49 AM, Paul Poulain wrote:
> What about adding separating "enhancements" in "enhancement" (of an
> existing feature) and "New feature" by adding the "new feature" to
> severity list ?
> The script generating release notes would be trivial to update to
> reflect that. Of
Am 15.11.2012 17:49, schrieb Paul Poulain:
> What about adding separating "enhancements" in "enhancement" (of an
> existing feature) and "New feature" by adding the "new feature" to
> severity list ?
> The script generating release notes would be trivial to update to
> reflect that. Of course tha
Paul,
-first of all, BibLibre is still facing problem with mails on this list:
> it seems we can post, but don't recieve any mail from it. That's why I
> missed the "Upgrading Koha license" thread, (I say +1 for GPL 3 of
> course). So if you answer this mail, would you be kind to add me
> directly
I query at db level as bugzilla is running on my linode server.
I query the status of bugs changed in the db and who changed them.
Chris
Marcel de Rooy wrote:
> To that end, I have been creating the statistics of signoffs
> http://blog.bigballofwax.co.nz/2012/07/01/bugzilla-statistics-for-jun
> To that end, I have been creating the statistics of signoffs
> http://blog.bigballofwax.co.nz/2012/07/01/bugzilla-statistics-for-june-2012/
Interesting statistics. I was trying to get these results from Bugzilla too.
So I tried this search:
Changed: (is greater than or equal to) 2012-06-01
Stat
All fine by me :)
Liz Real...@nekls.org
On Jun 11, 2012, at 4:00 PM, Paul Poulain wrote:Le 11/06/2012 19:34, Ian Walls a écrit :It would probably be best to take me off as default assignee for anycomponents, since I have little time for coding lately, and what time Ido have is going towards QA.I r
Le 11/06/2012 19:34, Ian Walls a écrit :
> It would probably be best to take me off as default assignee for any
> components, since I have little time for coding lately, and what time I
> do have is going towards QA.
I removed you from Hold requests and Self checkout
--
Paul POULAIN
http://www.bi
It would probably be best to take me off as default assignee for any
components, since I have little time for coding lately, and what time I do
have is going towards QA.
Cheers,
-Ian
On Mon, Jun 11, 2012 at 9:32 AM, Nicole Engard wrote:
> > On Sat, Jun 9, 2012 at 11:21 AM, Paul Poulain
> wro
> On Sat, Jun 9, 2012 at 11:21 AM, Paul Poulain
> wrote:
>>
>> OWEN & NICOLE & LIZ & CHRIS_N
>> We haven't changed the components you're default, because you said last
>> month it was OK for you.
A- OK with me.
Nicole
___
Koha-devel mailing list
Koha-
On Sat, Jun 9, 2012 at 11:21 AM, Paul Poulain wrote:
>
> OWEN & NICOLE & LIZ & CHRIS_N
> We haven't changed the components you're default, because you said last
> month it was OK for you.
>
That sounds good.
Kind Regards,
Chris
___
Koha-devel mailing l
Marcel de Rooy schreef op wo 02-05-2012 om 12:10 [+]:
> If the default assignee wants to be informed on reports of that
> category, moving him/her to the default CC list of that component
> would perhaps be better?
I'd like to remain on the packages. It doesn't bother me whether it's CC
or def
> Probably we can still wait a while and then ask the other ones if they
> still want to remain listed as assignees or be moved to CC?
For me, CC is enough.
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/
-community.org
[koha-devel-boun...@lists.koha-community.org] namens Fischer, Katrin
[katrin.fisc...@bsz-bw.de]
Verzonden: woensdag 2 mei 2012 16:51
To: Chris Nighswonger; koha-devel@lists.koha-community.org
Onderwerp: Re: [Koha-devel] Bugzilla component categories
Perhaps the answer is to blank only those
Perhaps the answer is to blank only those modules, where the default assignee
does not say he/she wants to keep it?
This way we will start again from a clean state and can add new module
maintainers later on if someone volunteers.
Katrin
From: koha-devel-boun...@lists.koha-community.or
I'll keep my default assignment for Website issues. :)
Liz Real...@nekls.org
On May 2, 2012, at 7:10 AM, Marcel de Rooy wrote:Hi all, Recently we discussed in the QA team to make the default QA contact empty. (Ian cleared this field for all components now [for new reports].) In the process the QA
--Original Message-
> From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-
> boun...@lists.koha-community.org] On Behalf Of Marcel de Rooy
> Sent: Wednesday, May 02, 2012 2:36 PM
> To: Owen Leonard
> Cc: koha-devel@lists.koha-community.org
> Subject: Re: [Koha-
-community.org
Onderwerp: Re: [Koha-devel] Bugzilla component categories
> Having someone in
> the Assignee field who is not working on that report, could be a misleading
> signal for an unaware Bugzilla user.
I like being the default assignee for OPAC, browser compatibility, and
template bu
> Having someone in
> the Assignee field who is not working on that report, could be a misleading
> signal for an unaware Bugzilla user.
I like being the default assignee for OPAC, browser compatibility, and
template bugs, and I make every effort to try to address those bugs.
What might be nice is
Le 02/03/2012 15:29, MJ Ray a écrit :
> Have any other site defaults been changed? (If so, could they be
> reset to what they used to be, please?)
I've read the release notes, and haven't noticed anything that has
consequences.
--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres p
Paul Poulain
> You'll see the change in the mails you recieve, they have changed a lot,
> and are in HTML. If you don't like that, you can switch back to "text
> mode" in your account preferences
That's at the bottom of
http://bugs.koha-community.org/bugzilla3/userprefs.cgi
Have any other site d
Le 22/02/2012 20:22, MJ Ray a écrit :
> Paul Poulain
>> I recieve a lot of mails from bugzilla when someone changes something
>> and i'm in the cc or have added a comment or am assignee.
>>
>> Sometimes i'm not sure if I'm the assignee or not.
>> Could it be possible to have that added to the emai
Paul Poulain
> I recieve a lot of mails from bugzilla when someone changes something
> and i'm in the cc or have added a comment or am assignee.
>
> Sometimes i'm not sure if I'm the assignee or not.
> Could it be possible to have that added to the email sent ?
Isn't it already there? I think i
't it? )
Thanks.
-Oorspronkelijk bericht-
Van: koha-devel-boun...@lists.koha-community.org
[mailto:koha-devel-boun...@lists.koha-community.org] Namens Paul Poulain
Verzonden: donderdag 19 januari 2012 14:29
Aan: koha-devel@lists.koha-community.org
Onderwerp: Re: [Koha-devel] Bugzilla: My B
Le 19/01/2012 13:42, Marcel de Rooy a écrit :
> Hi,
>
> Jared already asked this question earlier on, but could My Bugs be
> adjusted (after the change of status) ? By someone having the necessary
> permissions ..
Done. Please confirm it's OK
--
Paul POULAIN
http://www.biblibre.com
Expert en Lo
Le 18/01/2012 13:16, Marcel de Rooy a écrit :
> I would favor removing Patch-sent. The modification date has been updated for
> a lot of reports anyway because of the last change.
>
> And repeating my question of a few days ago to Ian and the list: Could we add
> a field for creation date of la
I would favor removing Patch-sent. The modification date has been updated for a
lot of reports anyway because of the last change.
And repeating my question of a few days ago to Ian and the list: Could we add a
field for creation date of last attachment? This would be even more accurate
than la
Le 16/01/2012 19:09, Galen Charlton a écrit :
> Hi Paul,
>
> On 01/16/2012 12:53 PM, Paul Poulain wrote:
>> we don't speak of bug display page, but of result list after a search.
>> (before reaching bug display page then)
>
> Thanks for clarifying. I've increased the width of that column; please
On Mon, Jan 16, 2012 at 02:49:39PM +0100, Paul Poulain wrote:
> Le 16/01/2012 14:29, Marcel de Rooy a écrit :
> >
> > I personally would like to have a wider Status column in Bugzilla.
> I also like to change that. I've digged in bugzilla admin, and could not
> find how to change this.
>
> > Now
Hi Paul,
On 01/16/2012 12:53 PM, Paul Poulain wrote:
we don't speak of bug display page, but of result list after a search.
(before reaching bug display page then)
Thanks for clarifying. I've increased the width of that column; please
take a look.
Regards,
Galen
--
Galen Charlton
Director
Le 16/01/2012 15:40, Galen Charlton a écrit :
> Hi Marcel,
>
> On 01/16/2012 08:29 AM, Marcel de Rooy wrote:
>> I personally would like to have a wider Status column in Bugzilla.
>
> It looks like somebody has gone ahead and made the template change, at
> lest for the bug display page. Can you c
-devel@lists.koha-community.org
Onderwerp: Re: [Koha-devel] Bugzilla
Hi Marcel,
On 01/16/2012 08:29 AM, Marcel de Rooy wrote:
> I personally would like to have a wider Status column in Bugzilla.
It looks like somebody has gone ahead and made the template change, at
lest for the bug display p
Hi Marcel,
On 01/16/2012 08:29 AM, Marcel de Rooy wrote:
I personally would like to have a wider Status column in Bugzilla.
It looks like somebody has gone ahead and made the template change, at
lest for the bug display page. Can you confirm that it's now looking wider?
Thanks,
Galen
--
G
I don't believe this is something you can edit in administration; you have
to set it directly in the template. This link has some information on
that:
http://groups.google.com/group/mozilla.support.bugzilla/browse_thread/thread/8acead76b18c224a?pli=1
-Ian
On Mon, Jan 16, 2012 at 8:49 AM, Paul P
Le 16/01/2012 14:29, Marcel de Rooy a écrit :
> Hi all,
>
>
>
> I personally would like to have a wider Status column in Bugzilla.
I also like to change that. I've digged in bugzilla admin, and could not
find how to change this.
> Now I have to know that e.g. “Patc” means Patch does not appl
Paul Poulain
> And the workflow would finally be:
> NEW > Patch sent > signed-off > passed QA > resolved (pushed) > fixed
>
> many/most projects work this way I think. Once a patch has been applied,
> the problem is resolved from dev point of view. The reporter just
> confirm by marking "FIXED".
Le 12/01/2012 18:00, Chris Nighswonger a écrit :
> On Thu, Jan 12, 2012 at 10:51 AM, Paul Poulain
> mailto:paul.poul...@biblibre.com>> wrote:
> Question to RMaint = is it worth having one more status I would set, to
> tell you, after pushing on master, that you should/must apply the bug
>
On Thu, Jan 12, 2012 at 10:51 AM, Paul Poulain wrote:
>
> Question to RMaint = is it worth having one more status I would set, to
> tell you, after pushing on master, that you should/must apply the bug
> also on stable ?
>
>
That would be fantastic! I'll even buy you lunch sometime for it.
Sorry
Le 12/01/2012 16:41, MJ Ray a écrit :
> Maybe the task is misdescribed and the patch writer should set it
> RESOLVED, then the bug closer sets it to VERIFIED, which would be
> more like as described in
> http://bugs.koha-community.org/bugzilla3/page.cgi?id=fields.html
So the workflow would be:
NEW
Chris Cormack
> Quite simple really, the bug submitter has not tested and marked it resolved.
> We are at step 8 of
> http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow
>
> (Bug closer: the person who checked that the bug is now fixed. Can be
> the reporter, it's preferred that th
Le 12/01/2012 09:59, Chris Cormack a écrit :
> On 12 January 2012 21:55, Zeno Tajoli wrote:
>> Why ?
>>
> Quite simple really, the bug submitter has not tested and marked it resolved.
> We are at step 8 of
> http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow
>
> (Bug closer: the p
On 12 January 2012 21:55, Zeno Tajoli wrote:
> Hi to all,
>
> this questyion is about Bugzilla workflow.
> The bug 7245 is fixed, code is updated in HEAD and in 3.6.x
>
> But the status is ASSIGNED and no 'RESOLVED'.
>
> Why ?
>
Quite simple really, the bug submitter has not tested and marked it r
Liz Rea
> I think more likely people are forgetful - would be nice to add this
> to git-bz as a flag so it was "forget proof."
It is already possible with git bz attach -e BUGNUM BRANCHPOINT
which is documented on
http://wiki.koha-community.org/wiki/Git_bz_configuration#Signing_off
but our bugzil
Right you are, I didn't know about that when I sent my message. So - everybody,
obsolete your patches when you attach them using git bz!
It's easy and fun!
Liz Rea
l...@nekls.org
<>
On Dec 16, 2011, at 10:30 AM, Paul Poulain wrote:
> Le 16/12/2011 17:22, Liz Rea a écrit :
>> I think more like
Le 16/12/2011 17:22, Liz Rea a écrit :
> I think more likely people are forgetful - would be nice to add this to
> git-bz as a flag so it was "forget proof."
???
git bg attach -e
=> the -e will show you the commit, with #obsoletes at the end.
Just remove the # and you'll obsolete the old
I think more likely people are forgetful - would be nice to add this to git-bz
as a flag so it was "forget proof."
Liz Rea
l...@nekls.org
<>
On Dec 16, 2011, at 8:18 AM, Magnus Enger wrote:
> On 16 December 2011 14:08, Paul Poulain wrote:
>> (feel free to add this to the wiki if you think it'
On 16 December 2011 14:08, Paul Poulain wrote:
> (feel free to add this to the wiki if you think it's worth it)
Done, and thanks!
http://wiki.koha-community.org/wiki/Bugzilla#To_mark_a_patch_obsolete
Best regards,
Magnus Enger
libriotech.no
___
Koha-de
Le 24/10/2011 18:46, Ian Walls a écrit :
> Everyone,
> *Versions: * I think the versions in this list should correspond to the
> main branches on the Koha Git repo. So, we'd have 3.2.x, 3.4.x, 3.6.x
> and master. A bug report should be connected to the most current
> version (if it's a problem i
Le 24/10/2011 18:20, Owen Leonard a écrit :
> Oh, and my vote for the most urgently-needed change to Bugzilla?
>
> Please change "Rel_3_8" to "rel_3_8" like all the other "rel_*_*"
> entries, it's driving me crazy!!
(Thanks to chris that gave me access) It's done.
I also have moved all rel_3_8 b
Le 24/10/2011 18:46, Ian Walls a écrit :
> *Versions: * I think the versions in this list should correspond to the
> main branches on the Koha Git repo. So, we'd have 3.2.x, 3.4.x, 3.6.x
> and master. A bug report should be connected to the most current
> version (if it's a problem in 3.6.x and m
Everyone,
First off, Paul, thanks for getting this rolling. I've been thinking a lot
about optimizing our Bugzilla set up to match today's current practices.
ByWater Solutions uses Bugzilla internally for partners support needs, so
I'm pretty well-versed in some of the configuration changes that
Le 24/10/2011 18:12, Owen Leonard a écrit :
>> • The priority is used to set "patch sent". This is a problem as we
>> completly lose Priority field usage.
>
> I don't mind that we lose Priority. Priority is completely arbitrary:
> a bug which is high priority for me might not be high priority for
Le 24/10/2011 18:20, Owen Leonard a écrit :
> Oh, and my vote for the most urgently-needed change to Bugzilla?
>
> Please change "Rel_3_8" to "rel_3_8" like all the other "rel_*_*"
> entries, it's driving me crazy!!
Agreed, I saw this small-but-very-annoying detail today, but can't
change it yet (
Oh, and my vote for the most urgently-needed change to Bugzilla?
Please change "Rel_3_8" to "rel_3_8" like all the other "rel_*_*"
entries, it's driving me crazy!!
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
___
Koha
> • The priority is used to set "patch sent". This is a problem as we
> completly lose Priority field usage.
I don't mind that we lose Priority. Priority is completely arbitrary:
a bug which is high priority for me might not be high priority for the
release manager. I ignore this setting altogethe
On 2 August 2011 17:09, Paul Poulain wrote:
> Le 02/08/2011 16:56, Mahesh T Pai a écrit :
>> Paul Poulain
>> writes:
>>
>> > My question : what should I do to discard this entry from my list ? I
>> > tried to remove me as assignee, but bz don't want "no assignee". Should
>> > we have a virtual
Le 02/08/2011 16:56, Mahesh T Pai a écrit :
> Paul Poulain
> writes:
>
> > My question : what should I do to discard this entry from my list ? I
> > tried to remove me as assignee, but bz don't want "no assignee". Should
> > we have a virtual assignee for this kind of entry ? Should I close the
Paul Poulain
writes:
> My question : what should I do to discard this entry from my list ? I
> tried to remove me as assignee, but bz don't want "no assignee". Should
> we have a virtual assignee for this kind of entry ? Should I close the
> bug entry as it's an enhancement, no-one plan to ta
Ian Walls wrote:
> Closing bug reports just because they're old or not recently updated doesn't
> seem right to me. Bug 2389, for example, seems like it's still relevant,
> even though no work has been done on it in a while.
>
> Are we just trying to get the number of 'open' reports down? Or to
On Tue, May 17, 2011 at 9:11 AM, Owen Leonard wrote:
>> I've added a custom search "very old" displaying bugs that haven't been
>> updated for more than 1 year. That's 295.
I still don't know how you got 295. I've been working from list with
the following criteria:
* Severity: blocker, criti
k bericht-
> Van: koha-devel-boun...@lists.koha-community.org [mailto:
> koha-devel-boun...@lists.koha-community.org] Namens Paul Poulain
> Verzonden: woensdag 18 mei 2011 18:11
> Aan: koha-devel@lists.koha-community.org
> Onderwerp: Re: [Koha-devel] bugzilla old entries
>
>
jk bericht-
Van: koha-devel-boun...@lists.koha-community.org
[mailto:koha-devel-boun...@lists.koha-community.org] Namens Paul Poulain
Verzonden: woensdag 18 mei 2011 18:11
Aan: koha-devel@lists.koha-community.org
Onderwerp: Re: [Koha-devel] bugzilla old entries
Le 17/05/2011 14:19, Paul Poula
Le 17/05/2011 14:19, Paul Poulain a écrit :
> Hello,
>
> I've checked what is very old on bugzilla.
>
> There are 1603 bugs open as of today.
> I've added a custom search "very old" displaying bugs that haven't been
> updated for more than 1 year. That's 295.
>
> I feel we will never be able to tak
Paul Poulain
> I feel we will never be able to take care of all those bugs, and many if
> not most of them are related to problems on now-unmaintained versions of
> Koha.
> So i'd like to close all of them and mark them "wontfix". Does anyone
> think it's a bad idea ?
I think it's a good idea to
koha-devel-boun...@lists.koha-community.org im Auftrag von Owen Leonard
Gesendet: Di 17.05.2011 15:11
An: Paul Poulain
Cc: Koha Devel
Betreff: Re: [Koha-devel] bugzilla old entries
> I've added a custom search "very old" displaying bugs that haven't been
> updated for mo
> I've added a custom search "very old" displaying bugs that haven't been
> updated for more than 1 year. That's 295.
I don't see your saved search. Did you share it?
> I feel we will never be able to take care of all those bugs, and many if
> not most of them are related to problems on now-unmai
Le 22/02/2011 13:42, Chris Nighswonger a écrit :
> I understand what you are thinking now.
>
> I think if we just followed the use of the status and resolution
> fields (see
> http://bugs.koha-community.org/bugzilla3/page.cgi?id=fields.html#status)
> then in the case you suggest we would just re-op
On Tue, Feb 22, 2011 at 6:59 AM, Paul Poulain wrote:
> Le 22/02/2011 12:46, Chris Nighswonger a écrit :
> > Chris can correct me if I'm wrong
> >
> > Once the patch has been pushed to a QA branch it is "Pushed for QA."
> >
> > If it fails QA it should be "Failed QA."
> >
> > If it passes it s
Le 22/02/2011 12:46, Chris Nighswonger a écrit :
> Chris can correct me if I'm wrong
>
> Once the patch has been pushed to a QA branch it is "Pushed for QA."
>
> If it fails QA it should be "Failed QA."
>
> If it passes it should be "Needs sign off" or "Signed off."
>
> Once pushed to master it
On Tue, Feb 22, 2011 at 6:04 AM, Paul Poulain wrote:
> Hello,
>
> On http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3495, chris
> has pushed a patch, it's now "patch pushed" "please test".
> I tested and have found a problem (see comment 3)
> Should I modify the patch status ? which val
Hi,
2010/11/4 Marcel de Rooy :
> Couldn’t find this on the wiki. Should I leave a bug on resolved/fixed,
> resolved/invalid etc. or should they always go to closed in the end?
>
> Just some number: resolved+fixed=2636 bugs. Closed/fixed= only 78.
See
http://bugs.koha-community.org/bugzilla3/page
Hi,
2010/9/14 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" ???
Chris and Robin explained it well - a "regression" is a bug where that
which was working now
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.
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 wh
2010/9/15 Irma Birchall :
> 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
previousl
1 - 100 of 101 matches
Mail list logo
