From ooo-dev-return-18087-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org Mon May 7 22:29:22 2012 Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 16CBEC2A0 for ; Mon, 7 May 2012 22:29:22 +0000 (UTC) Received: (qmail 6436 invoked by uid 500); 7 May 2012 22:29:21 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 6346 invoked by uid 500); 7 May 2012 22:29:21 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 6337 invoked by uid 99); 7 May 2012 22:29:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 May 2012 22:29:21 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of marcus.mail@wtnet.de designates 213.209.103.7 as permitted sender) Received: from [213.209.103.7] (HELO smtp2.wtnet.de) (213.209.103.7) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 May 2012 22:29:12 +0000 X-WT-Originating-IP: 84.46.106.163 Received: from f9.linux (pop8-672.catv.wtnet.de [84.46.106.163]) (authenticated bits=0) by smtp2.wtnet.de (8.14.4/8.14.4) with ESMTP id q47MStnJ019105 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Tue, 8 May 2012 00:28:55 +0200 Message-ID: <4FA84CA3.8000907@wtnet.de> Date: Tue, 08 May 2012 00:28:51 +0200 From: "Marcus (OOo)" User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.2.20) Gecko/20110804 Thunderbird/3.1.12 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: What do we need to do in BZ after AOO 3.4 is released? References: <50AD66855C014E13A09322D50A0395F4@googlmail.com> <4FA03963.80604@wtnet.de> In-Reply-To: <4FA03963.80604@wtnet.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Am 05/01/2012 09:28 PM, schrieb Marcus (OOo): > Am 05/01/2012 06:24 PM, schrieb Juergen Schmidt: >> On Tuesday, 1. May 2012 at 16:41, Rob Weir wrote: >>> Today, among the 100 version strings the users need to scroll through >>> in BZ, we have "AOO340-dev". >>> >>> What do we want after we release AOO 3.4? >>> >>> Add AOO340? (Or just rename AOO340-dev to AOO340?) >> Renaming sounds good to me and all issues with AOO340-dev should be >> moved to AOO350-dev. >> Only some special issues that we propose and discuss for a 3.4.1 >> should get the AOO341-dev version >>> >>> Add AOO341-dev? >>> >> +1 >>> >>> Add AOO450-dev? >>> >> you mean AOO350-dev, correct? >> If yes then +1 >> >>> >>> Also, are there any "products" that can be removed or demoted to >>> "components" under another product? What we have now is simpler than >>> what we had with OOo, but it is still very complicated with a lot of >>> "dead wood" at the top level. > > From JIRA I know the "Affect Version" and "Fix Version" fields which > are used to describe where the problem was seen first and where it will > be fixed. > > In BZ the "Version" field is used to describe in which version the issue > happens. The follow webpage talks about a "Target" field: > > > > https://issues.apache.org/ooo/docs/en/html/bug_page.html > > 13. *Target: (a.k.a. Target Milestone) A future version by which the bug > is to be fixed. e.g. The Bugzilla Project's milestones for future > Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not > restricted to numbers, thought - you can use any text strings, such as > dates. > > > > It would be very helpful to organize and keep the overview about issues > for specific versions in the future. So, could this field be enabled? > > Marcus > > > >> We should upgrade BZ to the newest version where we get more >> flexibility to disable not longer used products, versions etc. >> >> And then we should cleanup the whole BZ. >> >> Juergen >>> >>> -Rob was the BZ instance already updated? I now can see a target field in issues. :-) Marcus