> We did not *predict* a release date, we *set* a release *target*. It's true > that etch won't be released until it's ready, but treating "when it's ready" > as the only target is a cop-out; the only way a project as large as Debian > can ever *be* ready is if a sufficiently large fraction of our members agree > to pull in the same direction at the same time in order to make that happen. > How do you expect such agreement without even setting a goal that developers > can choose to support? I feel the need to point out that this decision of setting up a release goal is certainly one of the best ideas proposed by the release team and it seems clear that it is one of the reasons which will make us release now too much time after that release goal. I even tend to believe that even those people who are not happy with the Dunc-Tank process (some even claiming quite loudly their partial happiness about the release delay) would agree that having a releas target well known since the beginning of the development of etch has helped most of us to organize their work in the etch release cycle.
Attachment:
signature.asc
Description: Digital signature