Re: [Maria-developers] Process suggestion for minor issues

2013-06-14 Thread James Briggs
the fail, hopefully. Thanks, James. --- On Fri, 6/14/13, Elena Stepanova wrote: > From: Elena Stepanova > Subject: Re: [Maria-developers] Process suggestion for minor issues > To: "Sergei Golubchik" > Cc: maria-developers@lists.launchpad.net > Date: Friday, June

Re: [Maria-developers] Process suggestion for minor issues

2013-06-14 Thread Patryk Pomykalski
Dnia 14-06-2013 o 12:27:22 Rasmus Johansson napisaƂ(a): Hi MariaDB Developers, This is a suggestion on how to deal with minor or lower priority bugs and tasks in JIRA, http://mariadb.org/jira . Please provide your thoughts. Do you think it's an OK way to deal with the minors or do you pr

Re: [Maria-developers] Process suggestion for minor issues

2013-06-14 Thread Roberto Spadim
maybe creating a project (in jira) about mariadb docs, could allow do do this, instead using the MDEV project, create a MDOC project to documentation or a MQA (quality) that should do test, documentation and quality features (code standard, benchmark etc etc ) at least if anyone know about somethin

Re: [Maria-developers] Process suggestion for minor issues

2013-06-14 Thread Jean Weisbuch
In my opinion many of the new features of MariaDB lacks some proper documentation/benchmarks and sometimes even testing, there are many features and new variables that could be used but almost nobody knows about these or the possible usecases/downsides are not clear and users will just keep it

Re: [Maria-developers] Process suggestion for minor issues

2013-06-14 Thread Elena Stepanova
(warning: it's a long one) Hi Sergei, On 6/14/2013 6:26 PM, Sergei Golubchik wrote: Hi, Elena! On Jun 14, Elena Stepanova wrote: On 6/14/2013 2:27 PM, Rasmus Johansson wrote: Here is a suggested process to handle the ever growing amount of minors. If a minor issue isn't fixed after two conse

Re: [Maria-developers] Process suggestion for minor issues

2013-06-14 Thread Roberto Spadim
about quality assurance process, what should be done? unit tests? test team? ___ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help :

Re: [Maria-developers] Process suggestion for minor issues

2013-06-14 Thread Roberto Spadim
i like the today jira process, if you want a higher priority, do some job solving the problem, after that we could have NEW FEATURE in JIRA, like: send the patch and marke the issue to "PLEASE REVIEW I HAVE SENT A SOLUTION!" (i don't remember but when this occur i set the issue to major (sorry i wi

Re: [Maria-developers] Process suggestion for minor issues

2013-06-14 Thread Elena Stepanova
Hi Kristian, On 6/14/2013 5:39 PM, Kristian Nielsen wrote: Rasmus Johansson writes: This is a suggestion on how to deal with minor or lower priority bugs and tasks in JIRA, http://mariadb.org/jira . Please provide your thoughts. Do you think it's an OK way to deal with the minors or do you

Re: [Maria-developers] Process suggestion for minor issues

2013-06-14 Thread Kristian Nielsen
Rasmus Johansson writes: > This is a suggestion on how to deal with minor or lower priority bugs > and tasks in JIRA, http://mariadb.org/jira . > Please provide your thoughts. Do you think it's an OK way to deal with > the minors or do you prefer some other way? The whole Jira thing is a farce.

Re: [Maria-developers] Process suggestion for minor issues

2013-06-14 Thread Elena Stepanova
Hi, On 6/14/2013 2:27 PM, Rasmus Johansson wrote: Hi MariaDB Developers, This is a suggestion on how to deal with minor or lower priority bugs and tasks in JIRA, http://mariadb.org/jira . Currently, the process we use makes a clear differentiation between major or higher prioirty issues (calle

[Maria-developers] Process suggestion for minor issues

2013-06-14 Thread Rasmus Johansson
Hi MariaDB Developers, This is a suggestion on how to deal with minor or lower priority bugs and tasks in JIRA, http://mariadb.org/jira . Currently, the process we use makes a clear differentiation between major or higher prioirty issues (called majors altogether after this) and minor or lower pr