Nils Faerber wrote:
> Hi all!
> What about finally finishing a release?
[...]
>
> What do you think?
> In that manner we would have to decide on three dates
>
> 1. feature freeze
> 2. code freeze
> 3. release finishing, maybe the above mentioned hacking weekend
>
Hi,
sorry for jumpin' in - but
what features have been planned for a potential release yet?
It is also not clear to me which features have which priorities.
As I am more a user than a programmer concerning ipaq/gpe I propose
there should be something like a roadmap. This makes it a lot easier for
users (!) to know what the next steps will be and what features will be
available. The calendar-app is a very good example for that because what
do I need a calendar-app if there is no alarm-framework available?
To make a long story short:
Set up a list of features that you think is sensible for daily usage of
a PDA, track down the dependencies and set up a list of priorities. Put
that list as a status/roadmap/milestone on the gpe-web-pages to make
very clear what has to be expected. When it comes to releases I propose
to set up somebody as a "release manager" for this certain release who
is in charge of the structure.
This transparency is important because it is part of some kind of
self-marketing the gpe-project. I think you guys really do a great job
with gpe. But there are also other GUI alternatives you are "competing"
with.
Cheers,
Matthias
--
Matthias Wientapper
m.wientapper@gmx.de
http://mattzz.dyndns.org
I'll get you yet, you kwazy wabbit!
Received on Wed Aug 21 14:53:22 2002
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:41:29 EDT