Jump to content

We use now RC3 on this forum...


Guest WoLeRiNe`

Recommended Posts

  • Replies 83
  • Created
  • Last Reply

they usually release it after giving it to their closed beta test group



Which, if I'm not mistaken, whether or not RC3 makes it here depends on how well it goes there. So if there are no real bugs reported in RC3 with them, couldn't it go strait to final?

It usually goes: Developer -> Private Testers -> Here -> Customer Testing

And depending how far along the releases are I think the "Private Testers" and "Here" step can be done at the same time, or very close.

I say this because "Release Candiate" means it's a "Candidate" for "release". So if RC3 does make it to public customer testing, you can be sure there will be an RC4... You just don't know if RC4 will make it to customer testing or not :P
Link to comment
Share on other sites

Which, if I'm not mistaken, whether or not RC3 makes it here depends on how well it goes there. So if there are no real bugs reported in RC3 with them, couldn't it go strait to final?



It usually goes: Developer -> Private Testers -> Here -> Customer Testing



And depending how far along the releases are I think the "Private Testers" and "Here" step can be done at the same time, or very close.



I say this because "Release Candiate" means it's a "Candidate" for "release". So if RC3 does make it to public customer testing, you can be sure there will be an RC4... You just don't know if RC4 will make it to customer testing or not :P



In theory you are correct, but we don't generally follow that method, RC3 will likely see customer release just to get wider testing, even if Final turns out to be RC3 + minor changes :)
Link to comment
Share on other sites

If RC15 is required, they release so many RC. (Then the RC1 most have been unstable :P ). Just hang on with pations.. You know you will get a nice board with the upcoming 2.2 release...



I thought of that too. Mabye it will be RC50 you couldn't know it but it's will be with many improvements :o
Link to comment
Share on other sites

I'd rather wait through 10 RC's than have to upgrade my board 10 times after final...



*is a patient little angel*


Exactly. What's the point of having a final release, if the day after there will already be a security update, like there was with 2.1.x? If having 10 RC releases means the final release is stable for half a year, isn't that worth the wait? People moan and complain that IP.Board is getting hacked, and yet they still complain when IP.Board is going through too many RC stages?
Link to comment
Share on other sites

In theory you are correct, but we don't generally follow that method, RC3 will likely see customer release just to get wider testing, even if Final turns out to be RC3 + minor changes :)


Isn't that how Firefox 2 was ultimately released? The final is RC3, which was released for further testing.
Link to comment
Share on other sites

Exactly. What's the point of having a final release, if the day after there will already be a security update, like there was with 2.1.

x

? If having 10 RC releases means the final release is stable for half a year, isn't that worth the wait? People moan and complain that IP.Board is getting hacked, and yet they still complain when IP.Board is going through too many RC stages?




I don't think. I think that they (staff) will explain us by the final board.
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...