1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 05/01/14 23:05, Sebastian Luther wrote: |
5 |
> I like this workflow because it makes it easy to see what has been |
6 |
> fixed since the last release. The only thing I have no use for, is |
7 |
> this InVCS keyword. I do not know what Zac used it for. Does |
8 |
> anyone have a use for it? |
9 |
I'm not sure what your confusion is. When a fix is pushed, it is InVCS. |
10 |
The bug is not SOLVED, because it only InVCS, not in a release. |
11 |
|
12 |
> Another topic is the bug status for open bugs, i.e. CONFIRMED, |
13 |
> UNCONFIRMED, IN_PROGRESS. I've never bothered with changing them |
14 |
> and haven't found them useful, but Brian suggested to use |
15 |
> IN_PROGRESS at times. What are your thoughts? |
16 |
My interpretation is that CONFIRMED bugs are bugs that a developer is |
17 |
able to reproduce, and IN_PROGRESS bugs are bugs that a developer is |
18 |
presently working on a fix for. |
19 |
|
20 |
CONFIRMED is, in my opinion, very useful. IN_PROGRESS is not that |
21 |
interesting. |
22 |
- -- |
23 |
Alexander |
24 |
alexander@××××××.net |
25 |
http://plaimi.net/~alexander |
26 |
-----BEGIN PGP SIGNATURE----- |
27 |
Version: GnuPG v2.0.22 (GNU/Linux) |
28 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
29 |
|
30 |
iF4EAREIAAYFAlLJ2lYACgkQRtClrXBQc7WCUgEApkPtEfm+NbZ6h61++6LmBlUa |
31 |
NXqlny20ZRtEqHFIDWMBAIl0meIaehTKe9Y/ZJZFhViCz/P9YOI0A2eJykPjLNdn |
32 |
=ffkw |
33 |
-----END PGP SIGNATURE----- |