On Wed, Sep 24, 2008 at 11:34 PM, Phillip J. Eby <[EMAIL PROTECTED]>wrote:
> In other words, I don't recommend mixing fork goals. If the goal is merely > to have more-frequent releases of setuptools, it would be better to have a > snapshot facility for same, and release dev-tagged eggs. Conversely, if the > goal is to prototype new features, then it doesn't make a lot of sense to > advertise it as a stable or up-to-date setuptools. > > So, my personal hope is that the persons doing the fork will make it clear > to their users which it is: unstable feature prototype, or simple release > snapshots? (Where the latter could just as easily be automated.) The point is that the stability you are claiming means that the whole community depends on your actions. The fact that you were busy lately made things even slower. That is my whole point. Even if you set up a snapshot facility, the only person that is able to make changes in setuptools is you and only you. Distribute will be driven by more people, and its trunk will be more unstable for sure. But it think we can do some valuable test-driven work all together, and our releases can be quite good. So I'll make it clear to our users: it will be a project with stable releases, and unstable features in branches, and a trunk to merge everything, like all the open source project out there. Best Regards Tarek > > > _______________________________________________ > Distutils-SIG maillist - [email protected] > http://mail.python.org/mailman/listinfo/distutils-sig > -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
