maria-developers team mailing list archive

[Roberto Spadim <roberto@xxxxxxxxxxxxx>]

a example of MDEV using Optimizer:
https://mariadb.atlassian.net/browse/MDEV-6696

2014-09-22 14:51 GMT-03:00 Roberto Spadim <roberto@xxxxxxxxxxxxx>:

> please include a new compenent
> Optimizer/Parser
>
> 2014-09-22 10:04 GMT-03:00 Rasmus Johansson <rasmus@xxxxxxxxxxx>:
>
> Hello all,
>>
>> I will later today switch on the usage of Components in Jira.
>> Components are a way of grouping issues inside a project. The idea is
>> to map every issue in Jira, being it a bug or a new feature to a
>> component which describes to what area of MariaDB the issue belongs.
>> For example a bug in Aria would be marked with the component "Storage
>> Engine - Aria". Currently there are 37 components defined in Jira that
>> should cover many areas, but I'm sure there are a few missing. There
>> is one generic to which you can assign issues that doesn't fall into
>> any other category, called OTHER. I'll include the list of components
>> here in the end of this email.
>>
>> * What do you need to do? *
>> The Component field will be a mandatory field when closing an issue.
>> Therefore if a component (or several components) haven't been
>> specified earlier for an issue, you'll have to choose at least one
>> when closing an issue. The field has autocompletion so if you start
>> typing for example "Galera" you'll be presented with the alternatives
>> "Galera", "Galera Arbitrator garbd", and "Galera SST". If you don't
>> find a suitable component then choose the component called "OTHER".
>>
>> * What is the benefit of using components? *
>> It's a way of organizing issues inside a project, so that you easily
>> can pull out all issues related to a certain area of MariaDB, e.g. if
>> I wanted to know all bug fixes for replication I would click on the
>> Replication component and get a list. There is the possibility to set
>> up automatic assignees based on components and components can be used
>> in filters and reports throughout Jira.
>>
>> I hope this won't be a burden. All feedback is of course welcome.
>>
>> BR,
>> Rasmus
>>
>> * Components in the MariaDB Server project in JIRA *
>> Data Definition - Alter Table
>> Data Definition - Procedure
>> Data Definition - Temporary
>> Data Manipulation - Insert Delayed
>> Data Manipulation - Subquery
>> Dynamic Columns
>> Events
>> Full-text Search
>> Galera
>> Galera Arbitrator garbd
>> Galera SST
>> GIS
>> Locale Settings
>> OTHER
>> Platform Debian
>> Platform FreeBSD
>> Platform Power
>> Platform Windows
>> Plugin - Audit
>> Plugins
>> Query Cache
>> Replication
>> Show Profile
>> sql_error_log
>> SSL
>> Storage Engine - Aria
>> Storage Engine - Cassandra
>> Storage Engine - Connect
>> Storage Engine - InnoDB
>> Storage Engine - OQGRAPH
>> Storage Engine - Spider
>> Storage Engine - XtraDB
>> Storage Enging - TokuDB
>> Time zones
>> Triggers
>> Views
>> XML Functions
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~maria-developers
>> Post to     : maria-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~maria-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Roberto Spadim
> SPAEmpresarial
> Eng. Automação e Controle
>



-- 
Roberto Spadim
SPAEmpresarial
Eng. Automação e Controle