On Tue, 26 Sep 2000, John Levon wrote:
> On Tue, 26 Sep 2000, Allan Rae wrote:
>
> > Then perhaps we need an extra state: Pending
> > to distinguish stuff that is present in the codebase and being worked on
> > (in progress) from stuff that has a patch pending or is being worked on
> > but not in the codebase yet (pending).
> >
> > Allan. (ARRae)
> >
>
> I'm not sure I see the point :
>
> Blank -> not being worked on porting
> In progress -> someone is working on it, not yet in tree, can't yet be
> ported to kde/gnome
> Completed -> in tree, can be ported
>
> After all, even if work has "finished", it won't be perfect will it ?
> That would mean everything stays "in progress" forever ;)
Here's a really simple example:
Preferences is in the xforms tree. Only half the lyxrc variables are in
the dialog. The dialog will be completely redesigned to limit the
possiblity of segfaults caused by tabs not fitting in the dialog width.
It's listed in the GUII page as "completed".
Does that make sense to you? It looks like it should be called "In
Progress" or at least "In Codebase" to distinguish it from something which
has been completed and will only be fine-tuned in future.
Then again a better explanation in guii.php3 of what you really mean by
the different states would also help.
Allan. (ARRae)
