Gürkan Sengün wrote: > > The current RC bug (#552913) has nothing to do with GNUstep,
> I didn't look into the details of this bug, I just tried the latest Gorm > tarball with the latest GNUstep tarball release, and that builds and works > fine. Did you check that the documentation is still in place? > Do we need to fix this bug, Well, at least theoretically, every bug has to be fixed. RC bugs even more so, otherwise the package may miss the release. > or can we just close it with the newer Gorm version, when we get the > latest gnustep-(make,base,gui,back) into sid? I suggest to fix it in your tree and mark the bug as pending (so that people looking at the RC bug list don't spend time on it), and upload the new gorm.app release when the transitions begins (we'll notify the release team to exclude it from the binNMUs, as previously done for such cases). Alternatively -- if you have a sponsor ready and willing -- it's always a good time to fix such a bug, so you can upload right away. In any case, it has to be fixed before or during the forthcoming GNUstep transition, and of course for Squeeze. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
