Author Topic: Crash 4.1.1  (Read 6593 times)

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crash 4.1.1
« Reply #30 on: June 04, 2015, 07:47:03 AM »
Alpha/Beta...did that ever matter to anyone what we were calling it? :)  According to Sean's definition we should have never been in beta anyway.  Beta was supposed to mean we think we've found and fixed all the bugs and crashes that we know about.  Well we knew about a lot of the issues on github way before anyone else found them.

Offline gerry

  • Hero Member
  • *****
  • Posts: 695
    • View Profile
Re: Crash 4.1.1
« Reply #31 on: June 04, 2015, 02:53:50 PM »
Yeah but I joked that he was taking the beta testing seriously.  What that means is you do a bunch of outrageous things a normal user wouldn't do to try to break the code.   If your sequencing for your actual show great...but that's not serious beta testing. :)
Ahhh,  I see .  This is my first time using a beta product, mostly by the time I start using something, other early adopters have moved on to the next great thing. I thought beta testing was when those who wished to use it early , used it and then reported issues in .
But this year , am using xlights now , and have a beagle bone black with P10s on order. Must be a renaissance  :)
Gerry

Offline sean

  • Administrator
  • Hero Member
  • *****
  • Posts: 1727
    • View Profile
    • Xlights and Nutcracker Forum
Re: Crash 4.1.1
« Reply #32 on: June 04, 2015, 06:52:47 PM »
here is what i see as our phases of testing

alpha: Code is not complete, bugs everywhere. You cant sequence a complete song. Alpha testers should be highly technical to help describe what they are seeing. testers augment development to get more fingers on the code. For users, they are learning a new look and feel. This code is buggy and incomplete.

beta: code is complete to teh extent that you can make a complete sequence. There are bugs, some significant. A larger test audience. We bring in the "normal" users who are not as technical. The users get the benefit of starting to learn a brand new sequencer but at the cost of "It worked before, now there are new bugs".
Developers get expansive user base to try functionality and UI usefulness.

production: No crashes with normal use. This version can be used for xmas 2015. you , the user, could freeze on this release and you would have a show.
There should be no major bug. This would be bugs blocking you creating a show.
Wide spread user base, stability very high.


for us
alpha: was jan 2015
beta: was mar 2015
prod: estimated june/july 2015. If it is not stable, we will hold on to beta testing maybe an additional month. I do believe we will be in production before expo (July 16th)
Sean
Littleton, CO
Latest releases http://nutcracker123.com/nutcracker/releases
xLights/Nutcracker Forum http://nutcracker123.com/forum/index.php
Fbook [url=https://www.facebook.com/groups/62