Le 17 févr. 07 à 20:22, Nicolas Roard a écrit :
On 2/17/07, Quentin Mathé <[EMAIL PROTECTED]> wrote:
Le 17 févr. 07 à 17:37, Yen-Ju Chen a écrit :
> As for targeting GNUstep stable release,
> I would say it is impossible for GUI application.
> We often find GNUstep bugs when writing applications and report
it.
> Then it get fixed in GNUstep svn.
> Therefore, the applications has to work with GNUstep svn version.
> So my proposal is that -stable work against GNUstep /trunk,
> and -release work against GNUstep stable.
> Whenever GNUstep make a release,
> that is a good time for us to make a release, too,
> or probably 1-2 months later to focus on bugs.
>
> A summary so far is:
>
> 1. -trunk: developers' playground
> 2. -stable: 'works for me' version, targeting GNUstep svn,
target of
> bug reports.
> 3. -release: 'works for everyone' version, targeting GNUstep
stable.
I think we won't avoid to handle gnustep-gui releases ourself time to
time :-/
What do you mean by that ?.. fork gnustep-gui ?
Huh not at all :-)
I just mean someone (who has commit access to gnustep svn) will have
to make a release, mostly to avoid having to delay our own release by
four months or more. It depends if gnustep-gui releases occur more
often in the future or not.
We are going to use almost all features available in gnustep-gui and
even push them beyond expectations time to time, then we will
encounter bugs and missing features quite often.
See recent bug reports by Guenther on gnustep-dev about NSOutlineView
for an example.
Quentin.
_______________________________________________
Etoile-dev mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-dev
