Return-Path: Delivered-To: apmail-commons-user-archive@www.apache.org Received: (qmail 14898 invoked from network); 27 Jan 2009 20:18:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jan 2009 20:18:14 -0000 Received: (qmail 8042 invoked by uid 500); 27 Jan 2009 17:31:34 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 8000 invoked by uid 500); 27 Jan 2009 17:31:34 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 7989 invoked by uid 99); 27 Jan 2009 17:31:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jan 2009 09:31:34 -0800 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [216.82.241.227] (HELO mail122.messagelabs.com) (216.82.241.227) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jan 2009 17:31:26 +0000 X-VirusChecked: Checked X-Env-Sender: GGregory@seagullsoftware.com X-Msg-Ref: server-3.tower-122.messagelabs.com!1233077462!42631058!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [137.134.240.188] Received: (qmail 12804 invoked from network); 27 Jan 2009 17:31:03 -0000 Received: from unknown (HELO postal.rocketsoftware.com) (137.134.240.188) by server-3.tower-122.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jan 2009 17:31:03 -0000 Received: from HQMAIL.rocketsoftware.com ([172.16.37.60]) by RS1063.rocketsoftware.com ([172.16.37.63]) with mapi; Tue, 27 Jan 2009 12:30:51 -0500 From: Gary Gregory To: Commons Users List Date: Tue, 27 Jan 2009 12:30:50 -0500 Subject: RE: [VFS] Status of current snapshot build Thread-Topic: [VFS] Status of current snapshot build Thread-Index: AcmAoJQ8lCQ1tT6PTzWvK4/Ldl+z6wABCObw Message-ID: <94C476C03BFF5E42AC3518FDAC9643C4AB57243CAF@HQMAIL.rocketsoftware.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi Arjen: The best approach would be to file Bugzilla tickets for each issue with pat= ches to the code and unit tests. You can then wait for the fixes to be reviewed and integrated or discussed.= You can then pick up a nightly-build or build from sources. Then you can pick up the next release. Gary -----Original Message----- From: Arjen van Staalduinen [mailto:arjen.van.staalduinen@gmail.com]=20 Sent: Tuesday, January 27, 2009 5:09 AM To: user@commons.apache.org Subject: [VFS] Status of current snapshot build Hello, We've been making serious use of the VFS in a current project that I work on, but in the current 1.0 release there seem to be some very nasty concurrency issues. I've come across some issues in the bugtracking system that I've also encountered, and a self build snapshot version seems to have those issues resolved. Now I'm facing the question if I want to put that snapshot build in a production environment or remove VFS from our project and rebuild that functionality with self build code. All my unit tests work fine with the this snapshot build, but I still need some extra courage:). Can someone provide me some kind of info that makes my confidence in this snapshot buil= d grow? On a related note. From what I've seen it seems like a smart move to atleas= t prepare a new release, as the 1.0 build is basicly not usuable in a multi threaded environment. Thanx in advance, Arjen --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@commons.apache.org For additional commands, e-mail: user-help@commons.apache.org