Haku2

I wouldn't say it's nonsense. This blog entry seems more like philosophical ramblings than product marketing to me. One could write a blog entry such as this one without ever being involved in software development.

Stop this pls.
You spend time on blogs and not on the dev.

Totally agree, my subscription year ends 31st March each year. Many real associations and clubs do it this way. I have people joining throughout the year and I constantly have to manually edit their invoices.

I am so disappointed that a simple feature I've been requesting since IP.Subscriptions/Nexus/Commerce is not included in this upgrade.  Again.
IPB has always assumed subscriptions need to be on a rolling calendar basis.  I totally understand there are a large number of communities that use that method.  However, an equal number of communities would love to have subscriptions expire on a set calendar date, configurable in the package.  My membership year is not on a rolling basis and and settinga hard expiration date in each transaction is very time-consuming. 
It's one additional setting in the renewal options to set an expiration date for the package.  That's it.  How hard can this be?  What is the rationale for not including it?
 

Oh, and one other thing - I assume that existing Commerce tools like coupons can also apply to subscription purchases and renewals?

Another cool feature I wish was implemented is the ability to upload/edit and view block templates like you do with other templates. Pardon if I'm missing it or something, but out of 4-5 different sites I've had to work on strictly with pages. I was able upload database templates, page templates and such
I can upload a block template, but then after I do so, I can only select it when creating block to view it, and then edit it from there. Is there no way to upload a block template like all the other methods?
 

SUPERB!
So does the new relational field thingy now support importing a 3.x database with relational fields and does it have all the features of the 3.x field?

Thank you @Ryan Ashbrook, sorry my sincerity but that method is quite ill-designed and not the same as the 3x. It has several flaws:
- It is a javascript controller "show/hide", not a full page reload that matters to increase pageviews and ad reloads.
- If you edit again the article, you cannot edit the page "cuts" as it "spoils" your article - try to do it and you'll see what i mean. For example if you decide to set the page break on a different point of the article, you need to edit the html of the post, remove all the divs and the mention to the JS crontroller and then place the new page tag where you wanted. This is not a practical method. 
Both features (full page reload, edition of article page cuts) were present in 3x and they are fundamental. Please try to put yourselves in the skin of the final user to understand this. A real CMS needs effectively allow multiple pages per article.
This makes us using Pages in competitive disadvantage with others - less pageviews, worse SEO ranking, less revenue.

Could you provide some further guidance on the range of 3rd party integrations please, I haven't seen anything about these and they sound very useful.  Thanks.

It already does that