[Twisted-Python] Subproject releases
David Reid
dreid at dreid.org
Wed Oct 12 00:30:29 MDT 2005
On Oct 11, 2005, at 10:49 PM, glyph at divmod.com wrote:
> I remember participating in this initial discussion.
>
> I remember taking some side in it, and arguing strongly for that side.
>
> I'm not sure which one it was, so if I'm responsible for rejecting
> it I've changed my mind, but if I was arguing in favor of it I'm
> now even more vociferous :).
Just in the interest of clarity, I'm fairly certain you argued
against this, because of the pain it would cause the developer
involved in all aspects of Twisted as opposed to just one or two
subprojects. Then I wrote pthy, to try to make that kind of thing
easier, no one used it, and now apparently you've written Combinator
to do the same thing in a different and all together better way. So
I support this kind of change.
As to when it should take place it's probably a good idea to discuss
it for at least one release to try and avoid releases getting even
more bogged down. I seem to recall one of the major reasons it took
2.0 so long to get released was the logistics of making the initial
split actually work. On that note, I do seem to recall that you
(glyph) suggested splitting the package distribution and doing the
repository reorganization with a few releases in between.
-David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/twisted-python/attachments/20051011/96948689/attachment.html>
More information about the Twisted-Python
mailing list