As I write my tag builder script is busy cranking out an RC 03 tag for the upcoming Sakai 2.5.3 maintenance release. The tag was cut from the 2.5.3 branch which was itself earlier generated from the 2.5.x maintenance branch. Unlike previous beta and RC tags that were created directly from the *x branch using a single SVN revision number (e.g. 2.5.x r48404 for the ill-fated 2.5.1 release), 2.5.3 represents a targeted approach that provides fixes to specific sets of tools and services. This strategy allows QA to better harness their resources and focus their testing on limited areas of the code base. 2.5.4 and succeeding maintenance releases will reflect this pattern.
Regarding the 2.5 maintenance series, 2.5.1 included over 120 fixes but was never released officially due to the discovery of a nasty portfolio bug during final testing of the release artifacts. 2.5.2 was the ...