On 04/10/2014 09:46 PM, Niels de Vos wrote:
On Thu, Apr 10, 2014 at 11:43:46AM -0400, Kaleb KEITHLEY wrote:
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 t
On Thu, Apr 10, 2014 at 11:43:46AM -0400, Kaleb KEITHLEY wrote:
> 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
> >> mast
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 interes
On 04/10/2014 04:22 PM, Niels de Vos wrote:
Hi all,
recently we have started to document the "Bug report life cycle"
(http://www.gluster.org/community/documentation/index.php/Bug_report_life_cycle).
The document contains quite some actions that are needed by engineers
and reporters. There does n
On 04/10/2014 04:22 PM, Niels de Vos wrote:
> Hi all,
>
> recently we have started to document the "Bug report life cycle"
> (http://www.gluster.org/community/documentation/index.php/Bug_report_life_cycle).
>
> The document contains quite some actions that are needed by engineers
> and repor
Hi all,
recently we have started to document the "Bug report life cycle"
(http://www.gluster.org/community/documentation/index.php/Bug_report_life_cycle).
The document contains quite some actions that are needed by engineers
and reporters. There does not seem to be any existing gatekeeper to
