bugPSPP - Bugs: bug #47266, Release after 0.8.5 / 0.9.0

 
 

bug #47266: Release after 0.8.5 / 0.9.0

Submitter:  Friedrich Beckmann <beckmanf>
Submitted:  Thu 25 Feb 2016 09:28:40 PM UTC
   
 
Category:  None Severity:  9 - Blocker
Status:  Fixed Assigned to:  None
Open/Closed:  Closed Release:  Before 0.10.0
Effort:  0.00
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 18 Mar 2016 02:19:04 PM UTC, comment #10: 

Yes, I guess so. I closed it.

Friedrich Beckmann <beckmanf>
Group Member
Fri 18 Mar 2016 10:35:44 AM UTC, comment #9: 

I committed a new file called Bug-administration to the repository.

Can we close this item now?

John Darrington <jmd>
Group administrator
Sun 13 Mar 2016 05:23:36 PM UTC, comment #8: 

John, your comment #7 is about the same as my understanding too.   I wonder whether we should write this down in the Git repository somewhere.

Ben Pfaff <blp>
Group administrator
Tue 01 Mar 2016 07:08:45 PM UTC, comment #7: 

I always considered the procedure to be:

Bugs which we think must be fixed before a release get their "Release" field set accordingly.

Bugs which need not be fixed before any particular release, get their "Release" field set to "Future".

Bugs where we have not get decided are left at "None".


Feature requests have their "Severity" field set to "Wishlist".
Bugs which cause a crash or other unwanted effects when incorrect
input is given are "Average".
Bugs which cause a crash when correct input is given are "Major"
Bugs which render the software unusable are "Blocker"


Obviously some cases are unclear and judgement has be be used.

John Darrington <jmd>
Group administrator
Tue 01 Mar 2016 09:01:59 AM UTC, comment #6: 

Hi John,

I would use this to track the outstanding bugs. Maybe we can close this once a procedure is clear that will allow to track the bugs which

a) we think should be fixed before a release
b) do not need to be fixed before a release
c) are under discussion

so we use Release: "Before 1.0" to say that we have looked at a bug and decided that it does not stop the current 0.10.0 release, right?

What is about:  bug #47251

? I would not fix it.

Friedrich

Friedrich Beckmann <beckmanf>
Group Member
Tue 01 Mar 2016 08:55:19 AM UTC, comment #5: 

This item is a "metabug". Do we need a "bug to discuss bugs"?  We can continue the discussion on -email is unavailable-

John Darrington <jmd>
Group administrator
Fri 26 Feb 2016 07:53:52 AM UTC, comment #4: 

O.k. I have to select the "Intermediate" selection.

Friedrich Beckmann <beckmanf>
Group Member
Fri 26 Feb 2016 07:51:50 AM UTC, comment #3: 

I cannot find a way to browse the bugs depending on the release field. The severity is shown when I used this "Advanced" browsing.

Friedrich Beckmann <beckmanf>
Group Member
Fri 26 Feb 2016 07:44:19 AM UTC, comment #2: 

Release field sounds as if it could be used for this... :-)

Friedrich Beckmann <beckmanf>
Group Member
Fri 26 Feb 2016 05:49:05 AM UTC, comment #1: 

Another way is to use the "Release:" field.  Set the items to "Before 0.10.0" if they need to be resolved before the next release.

John Darrington <jmd>
Group administrator
Thu 25 Feb 2016 09:28:40 PM UTC, original submission:  

I propose to track the decisions and ideas regarding the requirements for a release here. My idea would be to use the bug tracking severity option to name the bugs that we consider blocking a release.

John named those two:

Bug #42086: "DATASET COPY" don't copy cases
Bug #47090: Running a procudure on a dataset with a large number of variables takes an unreasonably long time.

I tested Bug #42086, set it to confirmed and severity "Blocker".

Regarding Bug #42086 I tried Johns proposed patch and could not immediately see a negative consequence...

What is about

Bug #47251: partly editing of text in the data sheet is not possible - only all or nothing

In my view this is related to sheet view and will be fixed once Johns magic code is in place. So I would leave it as it is. But is not nice when you edit something real.

Friedrich Beckmann <beckmanf>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by blp (Posted a comment)
  • -email is unavailable- added by jmd (Posted a comment)
  • -email is unavailable- added by beckmanf (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-03-18 beckmanf StatusNone Fixed
        Open/ClosedOpen Closed
    2016-02-26 beckmanf ReleaseNone Before 0.10.0

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code