Here I agree 100% - I'm not sure if current description brings always "desired" audience to the project... Yet, it's really a *minor* (minorish minor) issue, and if CSSU would have only such problems, I would be happy penguin.
Also, woody14619 provided some nice links with detailed changelogs. + I totally agree with his rationale about compatibility - sorry szopin, but I remember crawling through pages and pages of discussions, about how PR1.3 resulted in some package being incompatible. You ask, if maintainers should fork their applications? IMO no, they should write it to work well on latest upstream version (being CSSU Stable now), which 99% of the times meant working well on experimental (CSSU-testing). If it also works nice on PR1.31, PR1.3, PR1.2, PR1.1 and so goes on, it's great. If not, it's generally problem of user refusing to upgrade - after all, it's FOSS, and you don't need to pay for new version... Of course, if maintainer want to fork program for different (C)SSU's - that's great. As it was stated, it happened many times, when PR1.3 was young. If not maintainer, but someone else want to backport things to older (C)SSU's, that's also great. But, it isn't required. /Estel