Here is the original post: http://us.battle.net/d3/en/forum/topic/5969147067
In general we tend to not provide release dates or specific timeframes for patches due to the complexity of the updates, and the possibility that we’ll discover an issue that keeps us from releasing it on time. We discovered a few such issues late into the testing of 1.0.3b, which means it won’t hit this week as previously mentioned.
However, we know that a number of changes in 1.0.3b have been highly anticipated, and so we spent the better part of today pulling specific changes that did not run into testing issues out of 1.0.3b, and turning them into hotfixes. These include the Inferno drop increases among a couple others, and will be applied with off-peak rolling restarts tomorrow morning. We’ll also be updating the June hotfix blog with specific changes (including new drop rates) tomorrow morning after we manage to wrangle up a cup of coffee.
The thread itself is still active, but it was removed as a sticky once we announced the release date for 1.0.3b (which occurred here: http://us.battle.net/d3/en/forum/topic/6036676877
). With the patch just around the corner and the patch notes up, we felt it was okay to go ahead and remove the sticky.
The reason 1.0.3b was delayed was because we experienced issues with some of the changes while testing the patch for release. This is not uncommon, and we elected to postpone the patch until those issues could be addressed. Since not all of the changes were causing issues, though, we decided to implement them via hotfix. This is described in the thread above. The changes we pulled from patch 1.0.3b and added as hotfixes are listed here under "June 28": http://us.battle.net/d3/en/blog/6214196/
Keep in mind that when Bashiok said "due to the complexity of the updates," he was referring to the patching process itself, rather than any specific, individual changes. The process itself is pretty complex, and (as evidenced with patch 1.0.3b) there are times when we have to adjust our original development schedules to accommodate emergent issues discovered during testing.