From zeta-dev-return-835-apmail-incubator-zeta-dev-archive=incubator.apache.org@incubator.apache.org Fri Dec 9 16:13:47 2011 Return-Path: X-Original-To: apmail-incubator-zeta-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-zeta-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 9F4FA7C2E for ; Fri, 9 Dec 2011 16:13:47 +0000 (UTC) Received: (qmail 94418 invoked by uid 500); 9 Dec 2011 16:13:47 -0000 Delivered-To: apmail-incubator-zeta-dev-archive@incubator.apache.org Received: (qmail 94352 invoked by uid 500); 9 Dec 2011 16:13:46 -0000 Mailing-List: contact zeta-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zeta-dev@incubator.apache.org Delivered-To: mailing list zeta-dev@incubator.apache.org Received: (qmail 94344 invoked by uid 99); 9 Dec 2011 16:13:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Dec 2011 16:13:46 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of flyingmana@googlemail.com designates 209.85.161.47 as permitted sender) Received: from [209.85.161.47] (HELO mail-fx0-f47.google.com) (209.85.161.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Dec 2011 16:13:40 +0000 Received: by faaa20 with SMTP id a20so870512faa.6 for ; Fri, 09 Dec 2011 08:13:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=dCZFhS+lFQHWPK9sYbR7OOMmyh+Az4sGvN/cKMhKZxc=; b=kX8cGDyG0VY1vqn927RuUM4cTtZboK9Oi1McWKSH9XrIoCcqK7tLqjoO8dboZ21fm/ j2LQnVy4NN8rbbzB7VTX2HxqqsMOOmt7pFhNK6evOBFGd4y1ElNgM9zSVhb1eeJK8IT2 oYGBr1Q+MD4ZrI1wrEMB4cz7hEIGsUTXJUgI4= MIME-Version: 1.0 Received: by 10.180.92.169 with SMTP id cn9mr11074288wib.62.1323447200120; Fri, 09 Dec 2011 08:13:20 -0800 (PST) Received: by 10.180.6.199 with HTTP; Fri, 9 Dec 2011 08:13:20 -0800 (PST) Date: Fri, 9 Dec 2011 17:13:20 +0100 Message-ID: From: Daniel Fahlke To: zeta-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=f46d0435c0683dfddf04b3ab10af X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [zeta-dev] Zeta Components Release on 2011-12-22 - Issue Management --f46d0435c0683dfddf04b3ab10af Content-Type: text/plain; charset=UTF-8 Hi, related to my mail from before i want to change some Issue states and asign Issues to certain Releases (primary the upcomming one) So, I dont have a clue how the upcomming Version should be named ( I remember a discuss about it but not the result. ) Anyone who can Answer this, or have I to reread the discuss about it? Assign to the upcomming Version i would the following Issues #102 #95 #74 #65 #62 #25 #22 Than, close #92 as duplicate of #21 Would be nice if someone could do this for me or give me the rights to do this. Regards, Daniel Fahlke aka Flyingmana --f46d0435c0683dfddf04b3ab10af--