On Feb 20, 2010, at 8:10 PM, Scott Gray wrote: >> >> Again, I agree with you and I also agree that documenting this change is a >> good idea. >> But I still think that this specific issue could be discovered and fixed >> (even without documentation) by a decent developer in less than 20 minutes >> after a system upgrade. >> If there is a document it is even better... >> >> Jacopo > > That's why I was in favor of using deprecation, it's a fantastic form of > documentation. Every time you compile it's there in your face telling you > that you need to change something and what to change it to. > 20 minutes may sound fine, but it's the accumulation of at least years worth > of these types of changes multiplied by the number of people affected by > them. When you look at it in those terms it is a fairly expensive strategy. >
Agreed. This is also one of the reasons I would like to issue more frequent releases (at least one per year). Regards, Jacopo > Regards > Scott >
