1.17 > 1.18 = 3+ months. 1.18 > 1.19 = ???

A slight concern of mine:

For the first half of the year, developers have been low-profile in regards to what is being developed and what is being implemented. 1.15 to 1.17 have been lackluster relative to what you would expect out of the patches within that time period.

Now we are finally supposedly getting to the point where the developers are about to catch up to the speed that better matches what is expected of them in the long run.

But something is slowing them down here. 3+ months to get a patch out after being developed for another 5 months? Few weeks of that are forgiven due to the disaster, but either way..

Honestly, it sounds like this patch will have content justifying the <3 months of development, but hardly enough to justify the low profile January-May period. The devs need to start catching up and putting out patches at an increasingly rapid rate or with increasingly larger size before the year ends.

So, are we looking at 2+ months of waiting between 1.18 and 1.19? If not, good, you guys might still make it, but if this is the case, either something is wrong in the development process or 1.19 will have to blow 1.18 out of the water in size and scope (which it honestly might).

If latter is the case, let us know. The sooner the better.

Yoshida mentioned accelerated schedual after 1.18...

Quote:

---

Originally Posted by Betelgeuzah

A slight concern of mine:

For the first half of the year, developers have been low-profile in regards to what is being developed and what is being implemented. 1.15 to 1.17 have been lackluster relative to what you would expect out of the patches within that time period.

Now we are finally supposedly getting to the point where the developers are about to catch up to the speed that better matches what is expected of them in the long run.

But something is slowing them down here. 3+ months to get a patch out after being developed for another 5 months? Few weeks of that are forgiven due to the disaster, but either way..

Honestly, it sounds like this patch will have content justifying the <3 months of development, but hardly enough to justify the low profile January-May period. The devs need to start catching up and putting out patches at an increasingly rapid rate or with increasingly larger size before the year ends.

So, are we looking at 2+ months of waiting between 1.18 and 1.19? If not, good, you guys might still make it, but if this is the case, either something is wrong in the development process or 1.19 will have to blow 1.18 out of the water in size and scope (which it honestly might).

If latter is the case, let us know. The sooner the better.

---

+3 months= Setting the Foundation down
Next patches in Quicker Succession = setting those pieces on top of that Foundation

That is all

A little brainstorming here, but it kinda looks like it's not as much of a problem on the actual development side of things as it is an issue when it comes to Quality Assurance. Lots of features which are nearing completion, but not enough bug-squashers to polish them up technically.

This would be good in a way, as the QA team doesn't hinder the developers' work. But it'll keep the patches further apart than they could be.

I'm hoping. The link in my sig says it all, it's been a relative snail's pace thus far, but Yoshi - and the base - have been arguing for a long time that 1.18 is just the start, and things should be going a lot faster after that. I would love to be surprised and have 1.19 (chocobos!) and 1.20 out the door in the next couple months, but I'm honestly expecting about a five, six month span between 1.18 and 1.20.

But if I disagree with acceptability of the pace, I like some of the changes that are being made, so prove me wrong, Yoshi, I won't complain!

Quote:

---

Originally Posted by ShinChuck

I'm hoping. The link in my sig says it all, it's been a relative snail's pace thus far, but Yoshi - and the base - have been arguing for a long time that 1.18 is just the start, and things should be going a lot faster after that.

---

Yep, but that's precisely why I am concerned. It doesn't seem like everything is optimized on their end. Rather it seems something is bottlenecking them.

What is the expected timeframe to be able to figure out and successfully implement a method to change the wheels on a moving racecar?

Quote:

---

Originally Posted by SunZhi

What is the expected timeframe to be able to figure out and successfully implement a method to change the wheels on a moving racecar?

---

Great analogy! Except that they're working on a clone of the racecar. Parked. In a garage.

Quote:

---

Originally Posted by trinta

Great analogy! Except that they're working on a clone of the racecar. Parked. In a garage.

---

More like a clone of the racecar barreling down a hill about to go off a cliff...

Quote:

---

Originally Posted by SunZhi

More like a clone of the racecar barreling down a hill about to go off a cliff...

---

Aye. Point is, they're not changing the wheels on a moving racecar.