You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by William Ferguson <Wi...@yarris.com> on 2007/09/19 00:13:59 UTC
Releasing 2.0.8
Now that it seems a release of 2.0.8 is imminent.
What is the protocol for agitating for issues that have been patched to
be included in 2.0.8?
Eg http://jira.codehaus.org/browse/MNG-2123
William
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing 2.0.8
Posted by Jason van Zyl <ja...@maven.org>.
Has a patch attached so I changed the fix version to 2.0.8 and we'll
see where we get with it.
On 18 Sep 07, at 3:13 PM 18 Sep 07, William Ferguson wrote:
> Now that it seems a release of 2.0.8 is imminent.
>
> What is the protocol for agitating for issues that have been
> patched to
> be included in 2.0.8?
> Eg http://jira.codehaus.org/browse/MNG-2123
>
>
> William
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing 2.0.8
Posted by William Ferguson <Wi...@yarris.com>.
The problem in the current system is that it is not possible (for a
non-committer at least) to set the patch flag to true except when the
issue is first created.
So issues that get raised and have a patch subsequently attached never
get flagged as having a patch.
William
-----Original Message-----
From: Brett Porter [mailto:brett@apache.org]
Sent: Wednesday, 19 September 2007 10:09 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
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:vincent.siveton@gmail.com]
> 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: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing 2.0.8
Posted by Brett Porter <br...@apache.org>.
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:vincent.siveton@gmail.com]
> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing 2.0.8
Posted by William Ferguson <Wi...@yarris.com>.
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:vincent.siveton@gmail.com]
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing 2.0.8
Posted by Vincent Siveton <vi...@gmail.com>.
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
2007/9/18, William Ferguson <Wi...@yarris.com>:
> Now that it seems a release of 2.0.8 is imminent.
>
> What is the protocol for agitating for issues that have been patched to
> be included in 2.0.8?
> Eg http://jira.codehaus.org/browse/MNG-2123
>
>
> William
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org