Announcement

Collapse
No announcement yet.

Unresolved BETA issues seems manageable

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • napy8gen
    replied
    I agree with stryka.
    Looking at the first question. There is no intention or misleading question. And the customer is right about highlighting the question. He being positive since the start.

    I hope Wayne you can defence customer first before your sub employee. I think this thread could forward to high IB administrator in here. So to see how communication between customers has been held.

    Leave a comment:


  • stryka
    replied
    Originally posted by Wayne Luke View Post
    Large bold text is the equivalent of yelling. You would have had better response just creating a post with those two lines in it to emphasize them.
    Or it could've simply meant that i was trying to help emphasize what Mark couldn't interpret... anyhow... its semantics... you can close this thread now..

    Leave a comment:


  • Wayne Luke
    replied
    Originally posted by stryka View Post
    why would someone warn about "yelling"
    Large bold text is the equivalent of yelling. You would have had better response just creating a post with those two lines in it to emphasize them.

    Leave a comment:


  • stryka
    replied
    Wow... why are you guys so overly sensitive today... can someone read my thread/post before answering and threatening infractions... actually, as i review the thread... mark's answers were actually useles... no offence.. but read them yourself... or something was lost in the translation...

    You can't assume the tone of a message because i bolded and enlarged a font... i specifically said i was going to bold and highlight the questions because it seems that he wasn't able to extract the question... why would someone warn about "yelling"

    Anyhow.. you answered my question with a detailed and relevant response

    Originally posted by Wayne Luke View Post
    First, to get answers you should not Yell at the staff. In the future, this will gain you infractions or reduced posting privileges.

    To answer your questions, all betas are considered release candidates until they aren't anymore and then the next beta is built. We haven't used the Release Candidate name on versions for quite a while now. The goal is to fix high priority bugs before release. This is a combination of tier (feature importance), priority (data and platform stability) and visibility (how many customers it affects). This means a minor issue that affects all users can be fixed before a major issue that affects one user. We feel by adding visibility to the mix, we will better be able to determine how an issue affects a very broad customer base with broad needs. So just looking at priorities of Major, Critical, etc... doesn't show the entire picture.
    Last edited by stryka; Mon 21 Jan '13, 12:06pm.

    Leave a comment:


  • Wayne Luke
    replied
    Originally posted by stryka View Post
    ahhhh man.... not sure why you are misinterpretting the intent of this thread/post... let me re-write the question in BOLD

    I am not asking if VB5 is in RC stage... the status of that is pretty apparent

    QUESTION:

    1. In the past... has VB went to RC with "Major" issues still open
    2. Is the goal to have 0 MAJOR, CRITICAL and SHOWSTOPPER issues before going to RC?

    First, to get answers you should not Yell at the staff. In the future, this will gain you infractions or reduced posting privileges.

    To answer your questions, all betas are considered release candidates until they aren't anymore and then the next beta is built. We haven't used the Release Candidate name on versions for quite a while now. The goal is to fix high priority bugs before release. This is a combination of tier (feature importance), priority (data and platform stability) and visibility (how many customers it affects). This means a minor issue that affects all users can be fixed before a major issue that affects one user. We feel by adding visibility to the mix, we will better be able to determine how an issue affects a very broad customer base with broad needs. So just looking at priorities of Major, Critical, etc... doesn't show the entire picture.

    Leave a comment:


  • Aakif N.
    replied
    RC is an abbreviation for Release Candidate. It traditionally comes before Gold release of a software.

    Leave a comment:


  • Mark.B
    replied
    RC = Release Candidate.
    vB5 will be released when it's considered ready. That's the only information we have at this time.

    Leave a comment:


  • mrwhitee
    replied
    What is RC ?

    Leave a comment:


  • stryka
    replied
    ahhhh man.... not sure why you are misinterpretting the intent of this thread/post... let me re-write the question in BOLD

    I am not asking if VB5 is in RC stage... the status of that is pretty apparent

    QUESTION:

    1. In the past... has VB went to RC with "Major" issues still open
    2. Is the goal to have 0 MAJOR, CRITICAL and SHOWSTOPPER issues before going to RC?





    Originally posted by Mark.B View Post
    Well if you're asking "has vB5 gone to RC stage?", the answer is no.
    However I could not tell you if there will even be an RC stage, that hasn't been announced yet.
    Last edited by Wayne Luke; Mon 21 Jan '13, 11:36am. Reason: removed "shouting"

    Leave a comment:


  • Mark.B
    replied
    Well if you're asking "has vB5 gone to RC stage?", the answer is no.
    However I could not tell you if there will even be an RC stage, that hasn't been announced yet.

    Leave a comment:


  • stryka
    replied
    I think you are so accustomed to that question you didn't realize that i am not asking that question

    Please check again... it was just a generic question based on previous RC releases or dev trends with VB.

    Originally posted by Mark.B View Post
    No vB5 is still in Beta at this time and it is not currently known how many betas there will be before the software moves into the next stage - whatever that will be.

    Leave a comment:


  • Mark.B
    replied
    No vB5 is still in Beta at this time and it is not currently known how many betas there will be before the software moves into the next stage - whatever that will be.

    Leave a comment:


  • stryka
    started a topic Unresolved BETA issues seems manageable

    Unresolved BETA issues seems manageable

    Just noticed the Beta 27 has already been worked on.... looks like great progress.... just curious though... since VB said that no new features will be implemented before RC .. has VB went to RC with "Major" issues still open? Is the goal to have 0 major, critical and showstopper issues?

    I am pretty sure that the issues list with be exponential in RC because of the larger user base trying on live sites and getting better feedback.

    As of today... summary of Issues:
    Showstopper = 2
    Critical = 36
    Major = 417

Related Topics

Collapse

Working...
X