No worries Brett, thanks for getting back to me.  :)

-m

----- Original Message ----
From: Brett Porter <[EMAIL PROTECTED]>
To: Maven Developers List <[email protected]>
Sent: Sunday, October 28, 2007 11:56:56 PM
Subject: Re: When I submit a patch for a bug, how do I get someone's attention 
to merge it


Generally, prodding is enough. Sometimes, it might require multiple  
attempts.

Archetype is particularly problematic, though, as the current trunk  
has a limited future as there is some work ongoing to rewrite it, but  
with no timeline for it replacing the current implementation. It's  
obviously not an ideal situation. The patch should be noticed and  
ported to the new code at a more suitable time later. Otherwise, if  
someone puts together another release on the current code it should  
dropped in there.

Apologies for the confusion.

Cheers,
Brett

On 29/10/2007, at 5:49 PM, Matthew Flower wrote:

> Does anybody have an answer for this?  I enjoy submitting patches,  
> but I'm not really willing to do them if they are going into a  
> black hole.
>
> Thanks,
> Matt
>
> ----- Original Message ----
> From: Matthew Flower <[EMAIL PROTECTED]>
> To: [email protected]
> Sent: Wednesday, October 24, 2007 3:46:05 PM
> Subject: When I submit a patch for a bug, how do I get someone's  
> attention to merge it
>
>
> Hi Guys,
>
> I recently submitted a patch to a problem listed in JIRA
>  (http://jira.codehaus.org/browse/ARCHETYPE-35) but I didn't hear any
>  response after a few weeks.  Do I need to post here to bring it to
>  someone's attention?  Maybe an email?
>
> I don't want to be a pest, I just don't know if there is some  
> unwritten
>  procedure I'm unaware of.  I have been following the instructions at
>  http://maven.apache.org/guides/development/guide-m2- 
> development.html#Creating_and_submitting_a_patch.
>
> Thanks,
> Matt
>
>
>
>

--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Reply via email to