| 1 |
On 30.04.2012 22:13, Dirkjan Ochtman wrote: |
| 2 |
> On Mon, Apr 30, 2012 at 20:17, Kacper Kowalik <xarthisius@g.o> wrote: |
| 3 |
>> 1) how long are we supposed to keep old version of Python in Portage? |
| 4 |
>> 2) how many version should we actively maintained? |
| 5 |
> |
| 6 |
> I'm not sure we need hard rules here. IMO the current approach (i.e. |
| 7 |
> just talking about it and dropping as we decide it makes sense) is |
| 8 |
> just fine. In particular, some version bumps are just harder than |
| 9 |
> others, and adoption of new versions is always different (i.e. for 3.x |
| 10 |
> and 2.x versions is obviously a very different story right now). From |
| 11 |
> the other side (for example, in Mercurial depends), it also depends |
| 12 |
> how big of a boon new features are. |
| 13 |
> |
| 14 |
> So let's just decide on a case-by-case when we deprecate a version? As |
| 15 |
> for 2.5, are we seeing increased incompatibility yet? Any recent |
| 16 |
> examples? I think 2.5 is close to deprecation, but I'm personally not |
| 17 |
> getting the impression it's getting to be a big PITA just yet. |
| 18 |
|
| 19 |
10% of packages that restrict Python abi in any way, restrict 2.5 (I've |
| 20 |
grepped for "\(2.\[45\]\|2.5\)") That's the only statistics I could |
| 21 |
think of. |
| 22 |
|
| 23 |
I'm not aware of any security bugs related to 2.5 branch |
| 24 |
|
| 25 |
Cheers, |
| 26 |
Kacper |
Archives