[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: why do we need change?
From: |
Adrian Robert |
Subject: |
Re: why do we need change? |
Date: |
Tue, 25 Oct 2005 11:05:51 -0400 |
On Oct 25, 2005, at 7:28 AM, Dennis Leeuw wrote:
To get to 1.0 I think a roadmap is needed. Looking at:
http://savannah.gnu.org/task/?group_id=99
Maybe someone should define which one of those tasks needs to be
completed before GNUstep can be 1.0. And those points should be
made more visible on the website, as to get peoples attention.
All other stuff should be done in a post 1.0 branch or even not
excepted, until after the 1.0 release.
But who is going to take the lead to create a list of things to be
done before we can claim 1.0. And a bigger hurdle for the GNUstep
community how are we going to agree on it. Many of those
discussions tend to go no where on the GNUstep lists.
I suggest that one person (or a very small group) decides what
needs to be done and setup a rough timeframe in which they would
like it to be accomplished.
Despite having our current bug and task lists, I agree that a clear
list of prioritized tasks for 1.0, 1.x, and perhaps 2.0 is
warranted. I kind of like that task list as opposed to using the
wiki for this, assuming we can easily mark tasks on it by targeted
release (as in 1.0, 1.1, 2.0, etc.), and set the coloration of the
list display can be set to match that.
On the other hand, as of now it looks like this is not so easy, as
everything seems to be keyed to dates and/or "priorities" (which are
just semantically-empty numbers). Not sure if this is configurable.
Also, there is the question of how to separate out core vs. no-core
priorities. Right now there is a hodgepodge of tasks ranging from
core library work to GDL2 to Gorm, Jigs, and demo writing. Not that
these tasks shouldn't be listed somewhere, but if we can only display
colors and/or sort by one characteristic, the utility of the list for
aiding the reaching of 1.0 is hindered.
So, maybe it's simpler to just use the wiki?
In any case, from time to time in going through the code I know I've
noticed a few things in GUI and Back (and one or two in Foundation)
that need doing. Once we decide on the medium, I'll try to find some
time go through the places I remember and list them..
- why do we need change?, Riccardo, 2005/10/24
- Re: why do we need change?, Dennis Leeuw, 2005/10/24
- Re: why do we need change?, Nicolas Roard, 2005/10/24
- Re: why do we need change?, Gregory John Casamento, 2005/10/25
- Re: why do we need change?, Dennis Leeuw, 2005/10/25
- Re: why do we need change?,
Adrian Robert <=
- Why Unanimous Consent Doesn't Work (Was: Re: why do we need change?), Alex Perez, 2005/10/25
- Re: Why Unanimous Consent Doesn't Work (Was: Re: why do we need change?), Gregory John Casamento, 2005/10/25
- Re: Why Unanimous Consent Doesn't Work (Was: Re: why do we need change?), Nicola Pero, 2005/10/25
- Re: Why Unanimous Consent Doesn't Work (Was: Re: why do we need change?), Alex Perez, 2005/10/25
- Re: Why Unanimous Consent Doesn't Work (Was: Re: why do we need change?), Andrew Ruder, 2005/10/25
- Re: Why Unanimous Consent Doesn't Work (Was: Re: why do we need change?), Richard Frith-Macdonald, 2005/10/26
- Re: Why Unanimous Consent Doesn't Work (Was: Re: why do we need change?), Nicola Pero, 2005/10/26
- Re: gnustep-make roadmap, Jeremy Bettis, 2005/10/26
- Re: gnustep-make roadmap, Nicola Pero, 2005/10/26
- Re: gnustep-make roadmap, Jeremy Bettis, 2005/10/27