Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 63839 invoked from network); 6 Mar 2009 05:32:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Mar 2009 05:32:59 -0000 Received: (qmail 11563 invoked by uid 500); 6 Mar 2009 05:32:58 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 11512 invoked by uid 500); 6 Mar 2009 05:32:58 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 11497 invoked by uid 99); 6 Mar 2009 05:32:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Mar 2009 21:32:58 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of John_Ballment@pacificnational.com.au designates 203.21.178.32 as permitted sender) Received: from [203.21.178.32] (HELO mail.pacificnational.com.au) (203.21.178.32) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Mar 2009 05:32:50 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Bug 46326 - StarTeam: Use Cache Agent for Checkouts Date: Fri, 6 Mar 2009 16:32:26 +1100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Bug 46326 - StarTeam: Use Cache Agent for Checkouts Thread-Index: AcmeGlDWZTgoTGfMRP2d9b6LPnNJ3QAATBHg References: From: "Ballment, John" To: "Ant Developers List" Received-SPF: none X-Virus-Checked: Checked by ClamAV on apache.org Hi Stefan, Believe it or not I have at least one tester, Paul Coste. He requested some of the enhancments and gave suggested code. I've tested/verified his code and I've asked him to verify mine. Sorry about the cases, in Starteam, setting cases to fixed only flags that they need to go to UAT for verification and once successfully validated the status is changed to Fixed Verified. This then flags it for a production release and once it is released the status goes to Fixed Closed. I guess my next question is, is it my responsibility to get distribute these patches to some parties that are using Starteam and Ant to verify or does it get added to the sandbox for others to checkout/build and verify? Regards,=20 ____________________________________________ =20 Pacific National Pty Ltd John Ballment BIT(IS) Senior Systems Analyst=20 john_ballment@pacificnational.com.au=20 Phone: (02) 9893 2618=20 Fax: (02) 9893 2698=20 Mobile: 0418 740 871=20 www.pacificnational.com.au =09 Level 4, 2-12 Macquarie Street=20 Parramatta NSW 2150 Australia -----Original Message----- From: Stefan Bodewig [mailto:bodewig@apache.org]=20 Sent: Friday, 6 March 2009 16:13 To: dev@ant.apache.org Subject: Re: Bug 46326 - StarTeam: Use Cache Agent for Checkouts Hi John On 2009-03-06, Ballment, John wrote: > I've integrated some patches from Paul Coste and added the following > fixes: > 39926 - StarTeam tasks to identify themselves as Ant + version number > 40995 - StarTeam checkout support Promotion State > 46326 - Use Cache Agent for Checkouts > 46327 - Use cache credentials (optional) for logging in rather than=20 > having scripts with hardcoded passwords You shouldn't resolve any of these bugs in bugzilla before the patches have actually been applied to Ant's code base - you lose visibility to the committers. > How quickly can we get these patches added to a build? The main problem with many of the optional SCM tasks (among others) is that no single Ant committer (still) has an environment around to actually test it. What we have now is your patch and your word that it works - and the only test we have ourselves would be "it compiles". If you could any other Starteam user to test your patched version, it would help tremendously. Even then, you'd be bound to waiting for the next Ant release, which may be several months away even if your patches were applied immediately. A Starteam Antlib that could be released separately from Ant would be the best option, but we'd have a hard time getting this released for the same reasons that you have a hard time finding anybody to apply your patch - no current committer could test the code. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org ****************************************************************** This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal. Opinions, conclusions, views and other information in this message that do not relate to the official business of Pacific National are the views of the individual sender and shall be understood as neither given nor endorsed by Pacific National. ****************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org