In a perfect world I agree with Brane. But there is top class from each igniter to trust each others on the 1000% and always to be ready that something go sideways. This process take time.
So I think that our Jira process should be flexible because Ignite is young project. As a first step we can get together to commit simple fixes without review and take as a "simple" issues in Jira with "trivial" priority. When our community credit of trust will grows up we can review Jira process and decide to take as a "simple" issues in Jira with "minor" priority or find some new solution. Etc... Regards, Vasilisa -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Jira-Process-tp1816p1917.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
