Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id F4159200D3E for ; Thu, 2 Nov 2017 00:25:57 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id F2978160BFA; Wed, 1 Nov 2017 23:25:57 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6B9AD160BEA for ; Thu, 2 Nov 2017 00:25:57 +0100 (CET) Received: (qmail 61354 invoked by uid 500); 1 Nov 2017 23:25:56 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 61343 invoked by uid 99); 1 Nov 2017 23:25:56 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Nov 2017 23:25:56 +0000 Received: from mail-qk0-f173.google.com (mail-qk0-f173.google.com [209.85.220.173]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 435381A0217 for ; Wed, 1 Nov 2017 23:25:56 +0000 (UTC) Received: by mail-qk0-f173.google.com with SMTP id r64so4768132qkc.1 for ; Wed, 01 Nov 2017 16:25:56 -0700 (PDT) X-Gm-Message-State: AMCzsaVjKWsgCAfg36H1nKAJwrPd5hRWfPkDl5o8KYOZNJOcFCiso8A4 kYaM6J39x4RA0dbU5/Huy3/ERvk3XKUMBvhpTb/1Rg== X-Google-Smtp-Source: ABhQp+T83XlUKYiN4jql/3X+CM9Ywwzi9dMqxsDCr/3vYNB5SyYAsb/25C8Azv+VggDciSds4jbgrN9/fPle59TvBOU= X-Received: by 10.55.136.67 with SMTP id k64mr2470786qkd.26.1509578755618; Wed, 01 Nov 2017 16:25:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.28.3 with HTTP; Wed, 1 Nov 2017 16:25:14 -0700 (PDT) From: Dmitriy Setrakyan Date: Wed, 1 Nov 2017 16:25:14 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: [DISUCSS] Ticket filing process To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="94eb2c06d8b87d59d8055cf43180" archived-at: Wed, 01 Nov 2017 23:25:58 -0000 --94eb2c06d8b87d59d8055cf43180 Content-Type: text/plain; charset="UTF-8" Igniters, Currently, most new Jira tickets do not get reviewed and often get lost unless some user complains about it. In my view, the community must review all recently filed ticket and make sure that we address most critical or most useful ones. Often an issue is not critical from correctness standpoint, but is very useful from usability stand point. What if we always assigned the next release version to all the newly filed tickets. This will force someone to look at the tickets before every release and move some of them to the next release. Thoughts? D. --94eb2c06d8b87d59d8055cf43180--