On Sat, 24 Jun 2006, Peter Eisentraut wrote:
> The current cdbs should go to testing first. The python team is not the
> only one we have to cater to.
If you change only the python class, you can reupload with an increased
urgency to have it enter testing at the same time than the current
version.
> The experience of the past week or two makes me wonder just how well this
> Python transition was planned. How do I know that by the time you have
> prepared a patch, the policy hasn't changed again already? We cannot be
The policy hasn't really changed, however python-support has been extended
to cover more cases. And this update is to let CDBS user benefit from this
enhancement.
> expected to jump in circles at every request within days or hours. When
> new proposals for features or enhancements come in, we sit back and
> consider them duly. If you need them tomorrow, you should have planned
> better yesterday. Again, I have no problem with these changes but we
> cannot throw away our development process because some people change their
> mind every few days.
Release early, release often. Considering the python transiton, I don't
expect any more changes however.
Cheers,
--
Raphaël Hertzog
Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
