Hi, I'm rebuilding my webserver, with sarge, because I figure it's going to release sooner rather than later.
So I've got the version of SquirrelMail that's in sarge, namely 1.5.0-1, and I proceed to go and get all the various plugins that I have installed in the version I'm currently running on my webserver, namely 1.4.0-1, and a lot of the plugins that are intrusive (i.e. require patching) to work, are having their patches failing left, right and centre, because the code's obviously not what they're expecting. So I dig some more, and I discover that 1.5.0 is not released yet, it's not a lot more than a CVS snapshot. So let's say that sarge releases, sooner rather than later (because I'm an optimist). There's going to be a lot of woody users dist-upgrading to a new squirrelmail that isn't supported by some of their plugins, even if they go off and get the latest versions of them. This is not a good way to be. I can't think of a way forward here, that isn't going to make a mess for a group of users. If you want to think about the users upgrading from stable, you should probably epoch squirrelmail, and upload 1.4.3, which is the latest stable squirrelmail release. This is of course, going to result in sarge users downgrading next time they dist-upgrade, with potentially unexpected results. I'm inclined to think the users upgrading from woody to sarge are more important than the users tracking a pre-release version of stable, (even though I fall into the second group in this case), but others may have different opinions. I'm Cc'ing this to the QA and release management groups for their input. regards Andrew
signature.asc
Description: Digital signature
