I am thinking on line like this:
current version will read upgrade notice for new version in advance AND guide user BEFORE upgrade about issues they may run into.
In buddypress-media 2.2 release @gagan0123 added some php 5.3 specific codes out of the blue, which broke sites that were running old versions.
On sidenote - either take php5.3 route from the start or don't take it all in the middle. If u need to go php5.3 way in the middle, we must have a mechanism in place to inform users in ADVANCE.
See: http://wordpress-hackers.1065353.n5.nabble.com/Upgrade-Notice-on-readme-txt-td36608.html
and http://wordpress.org/extend/plugins/changelogger/
I am thinking on line like this:
current version
will readupgrade notice
for new version in advance AND guide user BEFORE upgrade about issues they may run into.In buddypress-media 2.2 release @gagan0123 added some php 5.3 specific codes out of the blue, which broke sites that were running old versions.
On sidenote - either take php5.3 route from the start or don't take it all in the middle. If u need to go php5.3 way in the middle, we must have a mechanism in place to inform users in ADVANCE.
@yapapaya please explore this...