From jdo-dev-return-102-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org Mon Feb 28 17:02:52 2005 Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 32945 invoked from network); 28 Feb 2005 17:02:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 28 Feb 2005 17:02:52 -0000 Received: (qmail 45289 invoked by uid 500); 28 Feb 2005 17:02:51 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 45274 invoked by uid 99); 28 Feb 2005 17:02:51 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from mail.spree.de (HELO miraculix.spree.de) (62.154.194.149) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 28 Feb 2005 09:02:50 -0800 Received: from [172.16.1.21] (rhein.spree.de [172.16.1.21]) by miraculix.spree.de (8.11.6/8.11.6) with ESMTP id j1SH2gO14925 for ; Mon, 28 Feb 2005 18:02:43 +0100 Message-ID: <42234EB4.20709@spree.de> Date: Mon, 28 Feb 2005 18:02:44 +0100 From: Michael Bouschen Organization: Tech@Spree Engineering User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jdo-dev@db.apache.org Subject: Re: jdo tck meeting minutes 25 February, 2005 References: <421FA218.8090809@sun.com> <79883528771b12eeea513fda26f84c43@gluecode.com> In-Reply-To: <79883528771b12eeea513fda26f84c43@gluecode.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi Dain, thanks a lot for the info. This is what I was looking for. I copied some text from the geronimo wiki. Regards Michael > On Feb 25, 2005, at 2:09 PM, Michelle Caisse wrote: > >> Michael notes that the Apache JDO subversion repository cannot be >> reached from SWAN. This is not an issue for Michael or Michelle, but >> anyone who works from a Sun campus and needs to regularly access the >> repository will need to figure out a work-around. [SOCKS seems to be >> the key word -- maybe this helps: >> http://javaweb.eng/~jeffpk/USING_SOCKS/using_socks.html.] > > > Can't you just use https to access the repo? This works for most people > that have proxying firewalls. > >> We discussed the directory structure of the repository. Michael >> wonders if there is a standard for Apache projects that we should >> follow. He will query jdo-dev about this. Also, how will we >> integrate jpox in the jdo2 project? Will it be the ri or an iut? Will >> we provide a jar in the jdo repository, or provide instructions to >> users for obtaining the jar? > > > Most projects I have seen use something like this: > > jdo/ > trunk - main development line > branches - branches for developers and releases > tags - tagged releases > >> We agreed to keep wiki pages for completed tasks as a record of work >> performed. We will prominently note on the page that the described >> work is complete. > > > Most projects use JIRA for this. It a pretty powerful search and > reporting system. Geronimo uses it for auto generated changed logs (we > also provide a hand written one in releases). > >> He suggested posting the subversion connect procedure on the wiki for >> newbies. Michael will do this once he figures out what is required. > > > Feel free to swipe the text from the geronimo wiki (I swiped it from > some other project and update it): > > http://wiki.apache.org/geronimo/GettingSourceCode > > > -dain -- Michael Bouschen Tech@Spree Engineering GmbH mailto:mbo.tech@spree.de http://www.tech.spree.de/ Tel.:++49/30/235 520-33 Buelowstr. 66 Fax.:++49/30/2175 2012 D-10783 Berlin