On Sun Apr 20 19:01:44 2008, [EMAIL PROTECTED] wrote: > > I would like to propose both short-term and long-term remedies. > > Short-term: If you are proposing a new configuration step, or doing > a significant overhaul of any existing step, please post an RT with > the code and with a [TODO] tag several days ahead of time. This will > give people a chance to run it on different OSes right away, without > compromising trunk. And if I get advance notice of any new config > step, I pledge to work with you to develop tests for that step. >
Since I filed this RT, two completely new configuration step classes have been added -- neither of which was preceded by an RT. So it is evident that the committers do not like this suggestion. > Long-term: We need a Parrot design document on configuration. Such > a document should cover what configuration is, why we have decided to > include the configuration steps already there, what we need and what > we don't need. Such a document should distinguish between what we > need between now and 1.0 OTOH and post-1.0 OTO. > There has been no support for this suggestion from the key people. So I am withdrawing this ticket and classifying it as rejected. kid51
