Dag Sverre Seljebotn | 19 Aug 11:44

[Cython] Repository usage

There's been some talk already but now seems the time to make votes etc.

I propose that bugfixes that a) are relatively simple, and b) doesn't rely
on or interfere features implemented since the last release, are coded
against and pushed to "cython" and then merged into "cython-devel".

"cython" should still be considered relatively stable, so every commit
there is like a micro-patch-release of Cython.

This should take some pressure off cython-devel (although keeping it as
stable as possible is still good). Cython 0.9.8.2 may then come entirely
from "cython" if it is primarily a bugfix release, or from "cython-devel"
if it stabilizes.

One should think about some of the things that may be done to cython-devel
soon, especially import Greg's result_code-calculation-in-generation-phase
changes, and the other refactorings related to/made possible by that.
These are mildly dangerous (at least they lead to changes "everywhere")
but also needs to be in the main stream of development.

An alternative would perhaps be renaming "dagss" to "experimental" (but
IMO all new features as well as new framework changes so go into it then).

Thoughts?

Dag Sverre

Robert Bradshaw | 22 Aug 09:51

Re: [Cython] Repository usage

On Aug 19, 2008, at 2:45 AM, Dag Sverre Seljebotn wrote:

> There's been some talk already but now seems the time to make votes  
> etc.
>
> I propose that bugfixes that a) are relatively simple, and b)  
> doesn't rely
> on or interfere features implemented since the last release, are coded
> against and pushed to "cython" and then merged into "cython-devel".
>
> "cython" should still be considered relatively stable, so every commit
> there is like a micro-patch-release of Cython.

+1

> This should take some pressure off cython-devel (although keeping  
> it as
> stable as possible is still good). Cython 0.9.8.2 may then come  
> entirely
> from "cython" if it is primarily a bugfix release, or from "cython- 
> devel"
> if it stabilizes.
>
> One should think about some of the things that may be done to  
> cython-devel
> soon, especially import Greg's result_code-calculation-in- 
> generation-phase
> changes, and the other refactorings related to/made possible by that.
> These are mildly dangerous (at least they lead to changes  
> "everywhere")
(Continue reading)

Dag Sverre Seljebotn | 22 Aug 11:29

Re: [Cython] Repository usage

Robert Bradshaw wrote:
> On Aug 19, 2008, at 2:45 AM, Dag Sverre Seljebotn wrote:
> 
>> There's been some talk already but now seems the time to make votes  
>> etc.
>>
>> I propose that bugfixes that a) are relatively simple, and b)  
>> doesn't rely
>> on or interfere features implemented since the last release, are coded
>> against and pushed to "cython" and then merged into "cython-devel".
>>
>> "cython" should still be considered relatively stable, so every commit
>> there is like a micro-patch-release of Cython.
> 
> +1
> 
>> This should take some pressure off cython-devel (although keeping  
>> it as
>> stable as possible is still good). Cython 0.9.8.2 may then come  
>> entirely
>> from "cython" if it is primarily a bugfix release, or from "cython- 
>> devel"
>> if it stabilizes.
>>
>> One should think about some of the things that may be done to  
>> cython-devel
>> soon, especially import Greg's result_code-calculation-in- 
>> generation-phase
>> changes, and the other refactorings related to/made possible by that.
>> These are mildly dangerous (at least they lead to changes  
(Continue reading)


Gmane