Thanks for unblocking 3.1-2. That should go a long way towards providing users with a proper version in squeeze.
(Short version: unblocking 3.3 will make following upstream much easier for security / stable upgrades) However, that version is not maintained for security upgrades upstream. I have took over maintainership of the upstream stable branch after the 3.3 release, which is a critical bugfix release of the 3.2 release, which was itself a cosmetic release, introducing non-critical or security changes. That policy of including only security and critical patches to the Drush 3 branch will now be enforced more strictly by myself. I hope to be able to maintain drush3 in a manner that would be compatible with the way Debian handles upgradse in stable. But for that to work, I need that final release (3.3) to be allowed into squeeze. This will make following upstream *much* easier. From there on, I will maintain 3.x for stable/squeeze and 4.x for experimental. When 4.x is officially released upstream, I will then push it to unstable/testing and backport it to stable, if squeeze+1 happens after 4.x is released. The patchset for 3.1-2 -> 3.3-1 itself is not that huge either and while it does contain silly output changes, I have been careful *not* to include trivial changes to the debian/ directory that are waiting in my queue. Let me know if I can improve anything here to make your job easier, but I strongly believe drush would be best as 3.3 in stable. Thanks! A.
signature.asc
Description: Digital signature
