11 Dec
2014
11 Dec
'14
7:55 p.m.
On Wednesday 10 of December 2014 05:51:40 Michele Calgaro wrote:
On 12/10/2014 04:11 AM, Slávek Banko wrote:
I expected it with meta-bugs a little differently. I had an idea that meta-bug
for each release will be used in the same manner as it was now used meta-bug
2014 == for adding bugs that "we want to fix" in appropriate release. I will
try to illustrate reason on concrete example - bug in 2234 - is related to
previous example from http://trinity-devel.pearsoncomputing.net/?0::14181
Bug 2234 at first glance looked like a serious problem that needs to be fixed
quickly by adding "unconditional" retract yakuake window when the screen is
locked => include to R14.0.1. Upon further examination, it appeared that the
problem is not related to yakuake, but is related to a bug 2222. Bug report
was closed 2234. However, retract yakuake window when screen is locked seem
like a good idea - could be added as a new option == new feature => include
to R14.1.0. If the meta-bug for R14.0.1 and R14.1.0 were used as was now used
meta-bug 2014 for R14.0.0, there would be no problem. But common
meta-bug "Next version bug request list" is for such cases totally
insufficient. And I would anticipate that there will be more such cases.
Therefore, my suggestion is to use meta-bugs 2246 and 2247 in exactly the same
manner as was used meta-bug 2014. And 2233 will be wasted.
What is your opinion?
--
Slávek
Regarding the meta-bug for R14.0.x. I would
suggest for each 'patch'
release separate meta-bug. Thus, one for R14.0.1, separate for R14.0.2,
and as well as for next patch releases. It allows to plan assignment bug
reports for each patch release. A meta-bug also will then be an overview
of bugs fixed in any particular patch release.
Dear all,
I have renamed and created the following meta bugs.
1) Bug 2246 - R14.0.1 resolved bug list (meta bug)
2) Bug 2247 - R14.1.0 resolved bug list (meta bug)
3) Bug 2233 - Next version bug request list (meta-bug)
Each "resolved bug list" meta bug will list the bugs solved in the
corresponding TDE release version. Later meta bug for R14.0.2, R14.0.3,
etc... will be created.
Bug 2247 will depend on all R14.0.x meta bugs.
Bug 2233 should serve as "request list" for bugs to be fixed in the next
TDE version. Once solved, each bug should be moved to the appropriate
"resolved bug list" meta bug.
These meta bugs will serve as a good tool to keep track of what is fixed in
each release.
Cheers
Michele