The 1.1.5 + RM 1.0.1 Discussion Thread

Was there a specific reason that 1.1.5 was released rather than waiting for 1.2? (e.g. a major bug/vulnerability?)

Unless there's something critical fixed in 1.1.5 it maybe makes sense for us to wait until 1.2 rather than going through the whole style update/fixing process twice in a couple of weeks.
 
It's a standard maintenance release.
You don't have to upgrade if you don't want to, but all of the bugs marked as fixed since 1.1.4 will still be present in your installation.
 
Was there a specific reason that 1.1.5 was released rather than waiting for 1.2? (e.g. a major bug/vulnerability?)

Unless there's something critical fixed in 1.1.5 it maybe makes sense for us to wait until 1.2 rather than going through the whole style update/fixing process twice in a couple of weeks.

Some items are just better suited to be done in a minor release. But there would be no issue waiting until 1.2 to upgrade.
 
But remember that we're only talking about a beta of 1.2 coming out in June, as Biker mentioned. There may even still be a 1.1.6 down the line. As always, it is not recommended to run a beta in production. Maybe 1.2 will only be considered stable in August or even later -- it depends on how the beta process goes.

I've said this before, but 1.1.x and 1.2.x releases have no bearing on each other. They are separate branches in our code. If a 1.1 release is necessary, the state of 1.2 doesn't change anything. Even after 1.2 is released (stable), 1.1.6 could still be released (for security or bug fixes).
 
Unless there's something critical fixed in 1.1.5 it maybe makes sense for us to wait until 1.2 rather than going through the whole style update/fixing process twice in a couple of weeks.
There aren't much template edits here. It should take no longer than 30 minutes to update templates.
 
Top Bottom