Return-Path: Delivered-To: apmail-repository-archive@www.apache.org Received: (qmail 89158 invoked from network); 5 Dec 2006 22:34:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Dec 2006 22:34:31 -0000 Received: (qmail 3723 invoked by uid 500); 5 Dec 2006 22:34:39 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 3649 invoked by uid 500); 5 Dec 2006 22:34:39 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: repository@apache.org List-Id: Delivered-To: mailing list repository@apache.org Received: (qmail 3638 invoked by uid 99); 5 Dec 2006 22:34:39 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Dec 2006 14:34:39 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of wsmoak@gmail.com designates 66.249.92.170 as permitted sender) Received: from [66.249.92.170] (HELO ug-out-1314.google.com) (66.249.92.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Dec 2006 14:34:28 -0800 Received: by ug-out-1314.google.com with SMTP id 32so4181ugm for ; Tue, 05 Dec 2006 14:34:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=A6zlJ+dtXjcRJ1zcCwM6ONsHIOZThR6oW2lIPIFx6+E46QSb6CeFBD+rX7vYGqvrq1pIRUDk6eVfkZn0bs+WwTalgWkf0E2FuRzV26LLprhf+VAt8Csp85hQ7WOszyjlWWVWBrUmOFnrzVWn0mY0tC+GO8N3+8LWNl3r2INMFc0= Received: by 10.78.170.17 with SMTP id s17mr6282hue.1165358046821; Tue, 05 Dec 2006 14:34:06 -0800 (PST) Received: by 10.78.203.4 with HTTP; Tue, 5 Dec 2006 14:34:01 -0800 (PST) Message-ID: Date: Tue, 5 Dec 2006 15:34:01 -0700 From: "Wendy Smoak" To: repository@apache.org Subject: Re: Sync Request: Apache MINA 1.0.1 In-Reply-To: <4575EE46.8070709@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <768dcb2e0612042213r7a11a844te9d81dcc125fafaf@mail.gmail.com> <1a5b6c410612042237o2ec47063sfc7d13bdd9f6eab1@mail.gmail.com> <4575EE46.8070709@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org On 12/5/06, Jorg Heymans wrote: > I don't know if this came up before, but is it documented somewhere at > which times this automatic sync occurs? It would help projects to avoid > releasing during a sync. It's not formalized yet, but opinion is leaning towards "projects shouldn't release directly to the rsync repos". There was talk at ApacheCon US and on dev@maven about staging releases and then promoting them to the release/rsync repo after a vote. (I'm not sure how your project is handling releases, but your concern about releasing during a sync made me think you're concerned about not having a chance to review it before it syncs.) -- Wendy