On 04/10/2014 11:25 AM, Lalatendu Mohanty wrote:
QUESTION for #2:
- Shall we change the "Bug report life cycle" and advise to file
separate bugs per release? This makes it easier to track changes in
master (should go to MODIFIED), and copy/clone bugs for releases that
users are interested in (well, or copy the other way around, that does
not really matter).
IMO it is not right to ask the user to file separate bugs per release,
because most of the time users just use one version of glusterfs and
there is high probability that they don't know if the bug exists in
other releases. But when developer fix the bug, he/she can track if the
code (which is causing the issue) is present in other releases as well.
So developer should clone the bug for other releases and use the release
specific bugs for the patch.
+1
--
Kaleb
_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
