Am 09.02.2011 07:55, schrieb Riccardo Mottola: > perhaps we should make a list of things to do before the release of each > core component. Maybe on the wiki? > > Something on the line: > > For base: > * finalize FHS decision (or not) > * test working with/without ICU > For gui: > * fix bug 32166 (theme switching) > * finalize Gnome-theming
This is not needed for a GNUstep release. Greg needs only to make sure no additional changes to GUI are required. > * correct theming for Thematic in the definitive way (32056) Again not strictly necessary for a gui release. > * veryfiy bug 27782 That has been committed so long ago, that we should be rather sure it is at least not worse than before. > For back: > * xxxx > > For all core: > * do compilation test on most platforms > * verify libobjc1/libobcj2/gcc/clang... Yes and it would be great to have another set of static analysis for GNUstep. If David doesn't come up with that I will have to install Clang myself. Which probably will use up all the time I have for GNUstep this month. :-( > Generally, we could add on this list both tasks as well a certain bugs > to be checked (or discarded) for the release. > > Riccardo > > Gregory Casamento wrote: >> Before we do any release we should give some time for current efforts >> to complete and stabilize. >> >> I would like to complete the work on the GNOME theme prior to the >> release to make sure that there's no additional changes which must be >> made in gnustep-GUI in order to support it fully. >> >> GC >> >> On Tue, Feb 8, 2011 at 3:46 PM, Ivan Vučica<[email protected]> wrote: >> >>> On Wed, Feb 2, 2011 at 11:43, Nicola >>> Pero<[email protected]> >>> wrote: >>> >>>> gnustep-make needs a bit of work before release too; trunk >>>> contains a migration to the unix filesystem layout as default _______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
