| 1 |
On Wed, May 02, 2007 at 12:55:05AM +0100, Ciaran McCreesh wrote: |
| 2 |
> You're talking implementation details. This isn't the time for that! |
| 3 |
> No-one has worked out what, if anything, is to be done, so you can't |
| 4 |
> know how much work whatever it is is. |
| 5 |
> |
| 6 |
> Having said that, there's no need to figure it out for the whole tree |
| 7 |
> in one go if it's an EAPI change. |
| 8 |
|
| 9 |
Please stop stating that fallacy; binding it into an EAPI version |
| 10 |
means you *have* to plan for the whole tree (meaning figure it out up |
| 11 |
front). |
| 12 |
|
| 13 |
Skipping the whole "plan the fall out of it" bit of EAPI versioning |
| 14 |
means you wind up pushing multiple versions out (fragmenting the |
| 15 |
format), or forcing changes on folks while claiming "yeah, won't |
| 16 |
affect ya". |
| 17 |
|
| 18 |
~harring |
Archives