Return-Path: Delivered-To: apmail-incubator-empire-db-dev-archive@minotaur.apache.org Received: (qmail 94445 invoked from network); 24 Mar 2009 22:19:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Mar 2009 22:19:58 -0000 Received: (qmail 8155 invoked by uid 500); 24 Mar 2009 22:19:58 -0000 Delivered-To: apmail-incubator-empire-db-dev-archive@incubator.apache.org Received: (qmail 8113 invoked by uid 500); 24 Mar 2009 22:19:58 -0000 Mailing-List: contact empire-db-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: empire-db-dev@incubator.apache.org Delivered-To: mailing list empire-db-dev@incubator.apache.org Received: (qmail 7871 invoked by uid 99); 24 Mar 2009 22:19:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Mar 2009 22:19:57 +0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [217.7.226.111] (HELO mail.esteam.de) (217.7.226.111) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Mar 2009 22:19:48 +0000 Content-class: urn:content-classes:message Subject: Re: Call for planning of new release MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C9ACCE.9717EA5E" Date: Tue, 24 Mar 2009 23:17:10 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Call for planning of new release Thread-Index: Acmsayr8IAELosPmSeaV/Qa7g53icgAYxu1Q References: <3ab983230903171507y463aeb36g8fa482b07a18a255@mail.gmail.com><3ab983230903191331i413f81acx1eac5465d70a006f@mail.gmail.com> <3ab983230903240327ua014250m6c6ce773a2ab6cc0@mail.gmail.com> From: =?iso-8859-1?Q?Rainer_D=F6bele?= To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C9ACCE.9717EA5E Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Franics, I am sorry but I have been away and thus not been able to respond = earlier. I guess I will have time tomorrow to look at the assembly. Good to hear, that we can upload it to the central repository once the = release has been approved by the incubator PMC. As with our previous release we have to add "incubating" as long as we = are in the incubator. Unfortunately we don't have a wiki. All we have at the moment are static non editable pages. More infos tomorrow. Regards Rainer Francis De Brabandere wrote: > Betreff: Re: Call for planning of new release > =20 > Do we have a wiki available? I'd like to set up a page for the release > procedure. >=20 > On Thu, Mar 19, 2009 at 9:31 PM, Francis De Brabandere > wrote: > >>> I don't think we can release to the central repo as we are in > >>> incubation. The incubator has it's own repository for releases = where > >>> we can push our releases to. I'll try to make some time later this > >>> week or this weekend for getting acquainted with the actual = release > >>> procedure and configuration. > >> > >> Is this so? I thought the central maven repo was not restricted to = (top level) Apache projects but open to > anyone. Wouldn't that mean = that someone who wants to use empire-db would have to add the incubator = repository > to the maven settings first? And would this not be too = complicated for some? > >> > > > > the policy for this seems to have changed recently: > > http://www.nabble.com/Maven-for-incubating-projects-td22104374.html > > > > we need to add -incubating to the version string: > > = http://incubator.apache.org/guides/releasemanagement.html#best-practice-m= aven > > > > more this weekend > > > > -- > > http://www.somatik.be > > Microsoft gives you windows, Linux gives you the whole house. > > ------_=_NextPart_001_01C9ACCE.9717EA5E--