News Beyond - Chapter Four - Beta Announcement

Rob At Work

R
***Rob365 Power Red***

Confirmed bets available

Q4 - Being renamed Q19/1 (or similar)
Sandro to start a rumour that they are considering something that will never be included
Ed to go on a biscuit diet
FDev actually hitting all the dates they have set
Space Legs
The promised Powerplay update actually happening
The forum turning 2.8% positive
3.3 being bug free - 2m/1 :)
Alec Turner adhering to the NDA (He's gonna burst at some point - lol)
 
Last edited:

elkiller

E
Sir.Tj said:
I'd say they are testing each part in sequence. seems sensible to me it's a very very big update.
Click to expand...

when you introduce a feature usually comes with bugs. why would you bring one feature at the time that might add bugs to the previous ones. that why you release everything and then you tackle all the bugs.
 

who?

who?
elkiller said:
when you introduce a feature usually comes with bugs. why would you bring one feature at the time that might add bugs to the previous ones. that why you release everything and then you tackle all the bugs.
Click to expand...

That's probably why the last week is 'ships', at that point most everything will be in and catch any new issues introduced during the beta phase.

The beta periods can be carnage, with huge numbers of bugs logged, and lots of players just sneak-peeking instead of offering any feedback. This structuring makes sense for me, provides some focus.
 

metatheurgist

metatheurgist
elkiller said:
when you introduce a feature usually comes with bugs. why would you bring one feature at the time that might add bugs to the previous ones. that why you release everything and then you tackle all the bugs.
Click to expand...

Nah, that doesn't make any sense because they usually don't fix bugs found in beta, unless they're show stoppers. Even with beta expect the release to be full of bugs. :)
 

aybkamen

aybkamen
elkiller said:
...but it makes no sense form a developer standpoint is better to release all the features at once to have enough time to fix it if anything goes bad.
Click to expand...

I'm quite sure you are not a developer, because what you say makes no sense.

As a developer I prefer to always release in chunks as small as possible. The user is usually the one that wants all at once so he just does one update. But in terms of Betas, it makes perfect sense to focus on groups of features and incrementally add more in sucessive betas.

Actually I just did that this week, beta testing some features yesterday, and beta testing the other bunch today.
 

elkiller

E
Factabulous said:
Makes perfect sense from a 'we want to tell you about stuff and get feedback on specific changes' POV.

Though it's a bit of a worry that they think we won't be able to figure out the cool new stuff without being told how to ;)
Click to expand...

we have content creators that know how to play the game better than them. the whole showing is just to extend and buy time.
 

Nagual

Nagual
elkiller said:
when you introduce a feature usually comes with bugs. why would you bring one feature at the time that might add bugs to the previous ones. that why you release everything and then you tackle all the bugs.
Click to expand...

In order to get more feedback on the features that are released at the time.
 

thistle

T
elkiller said:
when you introduce a feature usually comes with bugs. why would you bring one feature at the time that might add bugs to the previous ones. that why you release everything and then you tackle all the bugs.
Click to expand...
Yo get people to test the individual parts for a week.

edit - I see this point has been made many many times in the intervening posts :D
 

elkiller

E
aybkamen said:
I'm quite sure you are not a developer, because what you say makes no sense.

As a developer I prefer to always release in chunks as small as possible. The user is usually the one that wants all at once so he just does one update. But in terms of Betas, it makes perfect sense to focus on groups of features and incrementally add more in sucessive betas.

Actually I just did that this week, beta testing some features yesterday, and beta testing the other bunch today.
Click to expand...

you are not going to get a job with that mentality. my coworkers are software developers and they release in "packages" to tackle of the bugs presented. every time you release a new feature it comes with bug but not only that they have to see how the other features react to the new feature. why would you release chunks that has guarantee bugs + might make other features buggy??? how as a dev you don't know what cross feature bugs are a thing.
 
You must log in or register to reply here.
Back
Top Bottom