This is a pet peeve of mine, so I'll just vent some steam. B-) On Mon, 9 Jul 2007 01:50:44 +0300 "Hisham Mardam Bey" <[EMAIL PROTECTED]> wrote:
> So what if we have an API break? We can take care of it - we have not > even made a stable release yet! If a developer takes the time to > improve something that no one else has the time (or will) to work on, > and it results in an API break, lets get his code into CVS (on the > condition that he fixes the core libraries and applications that are > affected). What are the core libraries and applications? Thats a good > question that we need to answer as a community and as a group of > developers. I've brought up the topic before, particularly with respect to ETK and EWL. Those that break an API in E's CVS should fix everything in E's CVS that gets broken by it. Despite all protestations to the contrary, it's not that hard. Whenever I've brought up this topic before, it's always "it's too hard, there are thousands of things to change". After getting annoyed and fixing things myself, I usually find the fixes are trivial. If it's trivial for me, a person that didn't change the API and has to figure things out by careful inspection of the commit email, then it will be even more trivial for the person that changed the API, as they will already understand the change. We like to take pride in the stability of our CVS, any random snapshot is likely to just compile and work. We have a reputation amongst our users for having an unreleased, constantly changing code base that is more stable and usable than v3.5 releases of other projects. This is why some Linux distros are not only happy to use E17 as an officially supported WM, they make loud noise about using E17. Whatever development environment you use, they often come with tools that make these sort of fixes easy. It's not rocket science, it's business as usual computer science. Computer programmers change APIs all the time, and we have written many tools to help with this change process. Please use them. End of rant.
signature.asc
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
