Mailinglist Archive: opensuse-project (146 mails)
| < Previous | Next > |
Re: [opensuse-project] Feature implementation details
- From: Jan Kupec <jkupec@xxxxxxx>
- Date: Tue, 17 Feb 2009 17:22:14 +0100
- Message-id: <499AE436.7050505@xxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Klaas Freitag wrote:
Stano, i'm not sure what you mean with "how", but i guess you mean "what
will be the outcome" of implementation...
+1 vote!
IMHO we should (at least try to) specify exactly (in some appropriate
level of detail) when we can consider the feature done. And this should
be done in the feature (openFate) itself and it should be done _before_
the implementation starts.
It might not be easy for some cases, but it's important. Except knowing
when to close the feature as done it will help us to better estimate the
efforts, and QA and users testing the feature will know what to test/expect.
I pretty much hope this will become a standard part of the process :O)
- --
cheers,
jano
Ján Kupec
YaST team
- ---------------------------------------------------------(PGP)---
Key ID: 637EE901
Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901
- ---------------------------------------------------------(IRC)---
Server: irc.freenode.net
Nick: jniq
Channels: #zypp #yast #suse #susecz
- ---------------------------------------------------------(EOF)---
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkma5DYACgkQgEhGpmN+6QHh/gCeLdfJwupRON1CrY/uEKXfHTxS
puoAnR8Jk2nmHjAqYR5WtpCiYPUaym/t
=N/MU
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
Hash: SHA1
Klaas Freitag wrote:
Am Montag, 9. Februar 2009 15:59:39 schrieb Stanislav Visnovsky:
Hi Stano,
As we now have openFate, it is finally much clearer what will end up in the
next release. However, Fate lacks one part of the information - how is a
feature implemented.
Stano, i'm not sure what you mean with "how", but i guess you mean "what
will be the outcome" of implementation...
I believe the best way to provide this information is using openSUSE wiki.I disagree. The best place for this information is Fate. The description
field gives us all we need to structure the text and add a paragraph
"And this is how this is implemented:".
Adding this to the features' description helps all involved parties such
as documenter and tester dealing with features. And all in all this kind
of information should really be part of a DONE feature.
+1 vote!
IMHO we should (at least try to) specify exactly (in some appropriate
level of detail) when we can consider the feature done. And this should
be done in the feature (openFate) itself and it should be done _before_
the implementation starts.
It might not be easy for some cases, but it's important. Except knowing
when to close the feature as done it will help us to better estimate the
efforts, and QA and users testing the feature will know what to test/expect.
I pretty much hope this will become a standard part of the process :O)
- --
cheers,
jano
Ján Kupec
YaST team
- ---------------------------------------------------------(PGP)---
Key ID: 637EE901
Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901
- ---------------------------------------------------------(IRC)---
Server: irc.freenode.net
Nick: jniq
Channels: #zypp #yast #suse #susecz
- ---------------------------------------------------------(EOF)---
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkma5DYACgkQgEhGpmN+6QHh/gCeLdfJwupRON1CrY/uEKXfHTxS
puoAnR8Jk2nmHjAqYR5WtpCiYPUaym/t
=N/MU
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
| < Previous | Next > |