I think it was a one off - basically the patch flag gets set to off
if the attached patch isn't sufficient (and the comments should be
enough to reflect it).
cheers,
Brett
On 19/09/2007, at 9:44 AM, William Ferguson wrote:
OH, I thought Maven_Patch_Day was a one off.
In that case can I suggest that the entries be split into separate
tables or documents based on whether they
- are waiting to be applied
- have been applied
- require revision, ie bad or out of date patch.
BTW it seems strange that this information needs to be managed in a
wiki, as JIRA contains most of it already.
Instead of indicating that a patch has been attached to the issue when
the issue was created, IMO what is really needed is the ability to
update the state of a patch on an existing issue. Ie [NoPatch, Patch,
BadPatch].
Then developers could upload a patche and mark the issue as having a
patch that need applying.
And reports could be run directly out of JIRA for OPEN issues with
patches that need applying.
Could JIRA be changed to accommodate this?
William
-----Original Message-----
From: Vincent Siveton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 19 September 2007 8:27 AM
To: Maven Developers List
Subject: [***POSSIBLE SPAM***] - Re: Releasing 2.0.8 - Email has
different SMTP TO: and MIME TO: fields in the email addresses
Hi William,
The best for us is to add it in the Maven Patch Day
http://docs.codehaus.org/display/MAVENUSER/Maven+Patch+Day
Cheers,
Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
