Thread: Concerns about Content Patch 2.1

Originally Posted by silverhope

This has zero to do with the OP.. Hes not talking about bugs hes talking about delaying content

Actually it does. In a branch model, new content is being created independent of the main line. Bug fixes on the other hand are implemented on the mainline as well as the branch.

What this means is that bug fixes can be rolled out simply through the QA process, while new features require substantial patch releases and testing cycles because it isn't merely a fix to mainline but an entirely different branch.

This is why they sometimes mention that they would like to release things sooner but cannot because of the work involved in breaking out one new feature from the branch, and merging it back into the mainline.

Releases that are designed around regular patches typically have this kind of structure.

You have a mainline (2.0) and a development (2.1) which is where major changes go into. You maintain 2.0 for bugfixes, but only occasionally backport changes from the development line (2.1) because the differences can be substantial in the code base, making it very difficult to safely do. Usually backports only occur for substantial flaws like security patches, where the current design is fundamentally flawed.

Once 2.1 is rolled out, they branch again (2.2) where again major changes will be going, and the process will continue. 2.1 will be hardened and only changed for bug-fixes or minor changes which are implemented simultaneously, or very rarely a backport.

Trying to implement substantial changes into both branches would require a significantly more aggressive QA progress and instead of speeding up patches, would slow them down. (or would involve releasing less tested software... Which nobody wants)

I wouldn't worry too much about it. Doomsayer threads will continue to pop up with increasing frequency leading up to 2.1 as more and more people feel the need to whine as if making these threads will somehow cause new contents to come out faster (they don't). Once 2.1 is out we'll have some reprieve for a week or so until the whiners return to whine more about the same old crap until 2.2.

Standard MMO forum culture. Nothing to see here. Move along.

[QUOTE=Maxthunder;1549810]

Originally Posted by Taemek

snip


SE could do the following: make open world mobs viable meaning they pose a threat, add open world grind parties, open world hnm's that actually give something of use (unlike behemouth and odin currently), use grand company seals to buy hnm pop items (1 time use win or lose), bcnm's (again gc seals for the item or the um beastman if you can call them that will drop them). There is so much more that could be done with the open world to improve all players experiences.

yeah i like this idea! was discussing this with a friend the other day. these systems alone gave you A LOT to do in 11. competition for NM's is also frustrating as hell but keeps palyers playing XD. love the idea for GC seals!!

competition for NM's is bad because of distance from servers and bots. No thank you! keep that **** out of this game.

besides, as is the case with most software, if you touch something, something else breaks! Therefore, for a patch like this they have to put all they have in one build and test it all together, bug fixes and new content. That way you can see if one of the new content is colliding with a bug fix or viceversa. Testing takes a while.