Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

CaptureONE PRO Beta: An Appeal Towards Public Beta

Kommentare

3 Kommentare

  • Paul Steunebrink
    Hi Ronald,

    Regarding the public beta, it only makes sense for Phase One when the have the feedback process in place to control the feedback. When this is not the case the entire process is counterproductive. An alternative to a public beta is a bunch of selected users with different background for hardware, software and use of the program (like a mix of data back and DSLR users). This gives more controlled and manageble kind of feedback which can be a much more efficient beta test. I believe Phase One has chosen this approach for CO 5 and 6.

    Regarding the free upgrade to CO 4 you mention, I believe this came from the fact the in the past CO 3 Pro included 2 free upgrades (to 4 and even 5) and CO 3 LE included 1 free upgrade (to CO 4 only) or none if you had a more recent purchase.
    0
  • Jim MSP
    [quote="Paul_E" wrote:
    .......
    Regarding the public beta, it only makes sense for Phase One when the have the feedback process in place to control the feedback. When this is not the case the entire process is counterproductive....

    I too have used CO since 3.x
    And I agree with Paul - only release it as a public if CO is set to handle the feedback in a timely fashion.

    If that were the case, and if it had already been tested operationally within a more limited test environment, I would be happy to play with a beta version and give feedback. I would not expect my next release to be free; perhaps discounted some if I provided sufficient feedback.
    0
  • ronaldnztan
    Hi Paul and Jim,

    Thanks for the clarification; the "public beta" I am referring is that, a public beta. Usually a public beta is released once P1 had undergone internal and controlled testing.

    It is like saying, "OK, we have profiled the possible hardware configurations from the selected group of archetypal users. Let's try widening the testing scope to real-world usage to see if things would break or stand up to real tests." Does my augmentation make more sense? I agree with the controlled testing in a laboratory setting, e.g "closed testing with NDA signed."

    I feel that each new release from C1PRO will benefit from the real-world, public testing so that any future version is smooth and less buggy.
    0

Post ist für Kommentare geschlossen.