I think there's an underlying development assumption here. The JIRA issue would just be a notification of an issue. The investigation and eventual fix for the issue requires the creation of a regression test case to recreate the scenario. Then when a fix is applied, this regression test will continue to make sure that the issue is fixed.
-Nathan > -----Original Message----- > From: Geir Magnusson Jr [mailto:[EMAIL PROTECTED] > Sent: Monday, July 24, 2006 7:09 AM > To: harmony-dev@incubator.apache.org > Subject: Re: [general] App-driven Improvement > > > > Anton Luht wrote: > > Good day, > > > > Are there any licensing limitations for those applications? > > No > > > Someone > > can find a bug in an application licensed under GPL, then minimize it > > to a test made of a couple of classes from that application and submit > > it to JIRA. It's likely that such test can sneak in the test suite. > > We just have to be careful that we don't get the test code from a GPL-ed > source, but simply independently get the bug to trigger. > > > > > There's an option for an attachment to grant a license or mark as > > non-licenseable, but as far as I understand, there's no such flag for > > text and code in the issue body. > > We don't want anything like that in our codebase. > > geir > > > > > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
