Fred Kiefer schrieb: > why do you expect the next release to break ABI compatibility? What I > wanted to do is a bug fix release and this is why I restricted myself to > non ABI breaking changes. Looking back through the ChangeLog file I > noticed that Greg has added an attached sheet ivar to NSWindow, this > will break ABI even though there still is no functionality behind that ivar. > > The idea of doing a release before your change landed was to give your > code some time to mature while it is exposed to multiple users with > different setup. Two months will be the minimum for that, we should > rather give it a bit more time, given the slow speed at which people > pick up GNUstep SVN changes. This would result in no GNUstep release for > that time and I really would have loved to see the bug fixes out there. > For example the cairo scrolling fix is something that the Etoile people > have been waiting for a long time. > > In the meantime Greg has commit some more of his attached sheet changes, > code which I find of limited quality. There also hasn't been any sign of > him fixing the NIB loading issues for NSTextView he introduced two > months ago. I started to work on a fix here myself, but really I at the > moment I am not able to stop the gui code from degrading. > > OK, I stop complaining and come up with a way forward. I will give Greg > time until this weekend to fix his sheet change, otherwise I will clean > up myself and after about a week of test we should be able to make a gui > and back release. Somebody else will have to speak up whether base is > ready for a release.
Greg did some clean up here, that should make us ready for a release. As Greg didn't undo his ivar change, I expect that he wants a full release with changed soname, not just a bug fix release. This is rather unfortunate as the next release after this will also be an ABI breaking one. Fred _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
