Quoting David Rothstein <dmr37@cornell.edu>:
Perhaps the root of the problem here is that -dev versions can be used in *two* different ways... --8<--
I haven't looked at all into the implementation, but if this turned out to be feasible, I think it might go a long way towards solving the problem mentioned here.
I think the best thing is to remove the confusion of what -dev means. A -dev release is only to be used to allow developers an easy method to know what the package will look like from an installation process. A -dev release isn't meant to be a "for general use" release. The "big red "X"" is there because of this and ppl just need to stop using -dev for anything else. If you have a stable bug fix release then release it. If you are planning more changes then wait and release it later. The point of Derek's original mail was to say, don't let every CVS change be a new release if there are planned changes in the near future. Planning is what should happen before a release is released. Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/