Probably the best thing to do to monitor progress is to monitor the changelogs and the code of the various bits of code you are pulling in.
I'm sure you understand that in a development release, most of the work goes into the actual development. If there is a fair amount of work to do, it's unlikely that the devs will have the time to offer granular updates on blogs or on bug reports. It's also likely that they will disable certain segments to focus on others. Certain fragments will change unexpectedly and things might appear to get worse before appearing to get better. Don't expect your view of "progress" to actually match up with the development view.
I'm sure you understand that in a development release, most of the work goes into the actual development. If there is a fair amount of work to do, it's unlikely that the devs will have the time to offer granular updates on blogs or on bug reports. It's also likely that they will disable certain segments to focus on others. Certain fragments will change unexpectedly and things might appear to get worse before appearing to get better. Don't expect your view of "progress" to actually match up with the development view.
Comment