Your suggestion for "API CHANGE" notes is a good one.
On Thursday 17 August 2006 1:36, Jim Hunter wrote: > I do not fully agree. They want US to test the code, they want US to help > write the docs but you don't think they should let US know when they change > things that would effect US helping them? If they want our full continued > support with new development, then I feel a little heads up would be nice. > > Jim > > On 8/17/06, Izaak Branderhorst <[EMAIL PROTECTED]> wrote: > > If they're making API changes to releases, I agree that we need to know > > about > > it on this list. > > > > However if you're living on the bleeding edge by using SVN snapshots of a > > development branch, it's your responsibility to pay attention to what > > they're > > doing. > > > > On Thursday 17 August 2006 12:13, Jim Hunter wrote: > > > OK, lets say that we all buy into the new changes. It would be very > > > nice > > > > if > > > > > that when changes to the API are made that will break code, these > > > > changes > > > > > are posted to the list so that we know about them BEFORE we update our > > > local copy of the code, regenerate and break our applications. A simple > > > heads up would have saved me a lot of time wondering why my borders no > > > longer worked and then trying to figure out how to make them work. I > > > > looked > > > > > through the SVN logs and see when you changed the borders but it's not > > > immediately apparent that the API changed. A possible enhancement might > > > > be > > > > > to add a simple "API CHANGE" to the first line of the notes so that > > > once > > > > we > > > > > look at the log we can immediately see that we have code changes to > > > make > > > > on > > > > > our side. This could make the transition to the new code easier. > > > > > > Thanks, > > > Jim > > > > > > On 8/17/06, Sebastian Werner <[EMAIL PROTECTED]> wrote: > > > > Hi Jim! > > > > > > > > I'm sorry about the problems with the changes to the border system > > > > (BorderPresets). > > > > > > > > To the documentation issue. Yes I think it's true, that each change > > > > requires additional work for the writers of documentation. But this > > > > is also true for the switch between major release to major release. I > > > > don't > > > > > > know a nice solution for this in a highly active project like > > > > qooxdoo. > > > > > > > > Cheers, > > > > > > > > Sebastian > > > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job > > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache > > Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > > qooxdoo-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
