Feature documentarion - was: Re: Todo questions
oritemis.frc at gmail.com
Tue Nov 13 17:22:42 CET 2007
How is the process of decision, between the devs, of what features will, or
will not, being included into a release? There is certain level of
formality? I mean, they decide that into a wiki, forum, or something? How
they organize the work load? How they analyze suggestion of new features,
for example, and decide if that will, or not, be included in next release?
Thanks a lot,
On Nov 13, 2007 2:00 PM, Harald Sitter <harald at getamarok.com> wrote:
> Am Dienstag 13 November 2007 16:40:23 schrieb Lydia Pintscher:
> > > There are feature documentation for 2.0 version? My experience says me
> > > that some too hard to code features are postponed sometimes, but
> > > proper documentation some of this features are lost. With proper
> > > documentation we could plan further releases (as Mozilla does, for
> > > example). I don't know if this is already done or not, then is a
> > > question.
> > I don´t know what is done here currently besides Harald´s list in the
> > where we are collecting features that need to be done before we can
> > release. Maybe someone else can say more about that.
> It's hard to get the devs document all their thoughts/actions... I'm
> quite happy that I have a somewhat usable feature progress list now -.-
> Harald Sitter
> Amarok team Project Manager Mail: harald at getamarok.com
> amarok.kde.org Good news everyone! Jabber:
> apachelogger at kdetalk.net
> Amarok-promo mailing list
> Amarok-promo at kde.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Amarok-promo