When you say merge, do you mean into trunk, or also the submerges into
my own feature/review branch? The big problem I can think of is that
interfaces are something you should probably have a rough idea about
way before any code gets written, but under this system branches get
reviewed per feature
On May 27, 2010, at 4:27 PM, Laurens Van Houtven wrote:
> I have diagrammed the quantum-transmogrifier example that I tried to
> explain in the last email.
OK. With this diagram in mind, I can see that what you're proposing is nearly
identical to what I've already proposed, except that you are
For clarity: I think Launchpad replacing Trac is a good thing. I realize
that's a huge ordeal. However, I don't think the basic ideas are so
different that it'd be impossible. As discussed on IRC, the main
downside (aka why we can't do it right now) is lack of notifications, so
it's hard to integra
On May 26, 2010, at 9:53 AM, exar...@twistedmatrix.com wrote:
> On 08:44 am, gl...@twistedmatrix.com wrote:
>>
>> On May 24, 2010, at 7:42 AM, Jonathan Lange wrote:
>>> Also, +1 on the documentation.
>>
>> I think we should continue this discussion after somebody has done at
>> least one branch
On May 26, 2010, at 5:41 AM, Laurens Van Houtven wrote:
> Major stuff could be a blueprint on Launchpad. Blueprints match a branch for
> the "big feature". So, we have the Twisted blueprint
> quantum-transmogrification and a branch
> lp:~lvh/twisted/quantum-transmogrification.
So, while I can
On 08:44 am, gl...@twistedmatrix.com wrote:
>
>On May 24, 2010, at 7:42 AM, Jonathan Lange wrote:
>>Also, +1 on the documentation.
>
>I think we should continue this discussion after somebody has done at
>least one branch like this.
Well, we did #886, right?
Jean-Paul
__
It would already be a big step forward if the naming convention could
be addressed. Unfortunately the web vs. web2 thing really puts code
archeologists in a confusion if the incremental numbered module policy
is applied, because it appears that web2 > web but it is actually not.
code archeology cou
I've said something in #twisted but I hadn't read this reply yet, so for
sake of saving this for posterity, I agree with jml here. I think we're
mostly being bitten because of a lack of software tools, in the form of svn
and trac. Disclaimer: I really dislike svn since I never figured out how
Combi
On May 24, 2010, at 7:42 AM, Jonathan Lange wrote:
> FWIW, we've been doing this on Launchpad for some years and it works out well.
Good to know.
> As a rule, we don't have the final "sanity check" review, since we
> have robot minions that check for conflicts and that the tests pass.
This is
On May 23, 2010, at 10:35 PM, exar...@twistedmatrix.com wrote:
> On 23 May, 12:26 am, gl...@twistedmatrix.com wrote:
>> So: thoughts? Does this make sense as a policy change for facilitating
>> the development of major new features or consolidating behavior-
>> changing fixes into easier-to-un
On Mon, May 24, 2010 at 3:35 AM, wrote:
...
>>So: thoughts? Does this make sense as a policy change for facilitating
>>the development of major new features or consolidating behavior-
>>changing fixes into easier-to-understand units?
>
> So, to summarize, we could stage our code using more than
On 23 May, 12:26 am, gl...@twistedmatrix.com wrote:
>The nice thing about Twisted's compatibility policy is that developers,
>and even users, very rarely have problems when installing a new version
>of Twisted. While this is a nice benefit, the current strategy of
>developing features in a comp
The nice thing about Twisted's compatibility policy is that developers, and
even users, very rarely have problems when installing a new version of Twisted.
While this is a nice benefit, the current strategy of developing features in a
compatible way does have a couple of costs, and I'd like to
13 matches
Mail list logo
