Also, I don't think Trac sends out email notifications when a file is  
uploaded to a ticket, only when a comment is added. We may want to add  
a note to the wiki about posting a comment after uploading a patch, so  
the owner is notified.

Kris

On Oct 15, 2008, at 1:56 AM, Fabien Potencier <[EMAIL PROTECTED] 
 > wrote:

>
> We definitely need more people able to triage the tickets. Fabian and
> Carl have done this in the past and it is a great way to contribute  
> back
> to symfony as well.
>
> Sometimes, the ticket is not a bug or a feature enhancement, but more
> like a question and can be closed right away (by asking the  
> submitter to
> ask his question on the ML).
>
> Sometimes, the ticket has a patch and need to be put in a milestone,  
> or
> the title must be changed with the [PATH] prefix, or the status must  
> be
> changed to "Ready for core team".
>
> Sometimes, the ticket has been fixed and just need to be closed after
> the fix has been confirmed.
>
> Last but not least, keep in mind that the Trac instance is used for  
> the
> symfony core, the symfony documentation, and also by all the symfony
> plugins. So, a lot of tickets just do not belong to symfony itself.  
> I'm
> working on separating plugins from the core but I don't think it will
> happen anytime soon (due to some technical difficulties).
>
> If you want to become a triager, please read the dedicated wiki page  
> on
> the subject (http://trac.symfony-project.org/trac/wiki/ 
> TicketWorkflow).
> It's pretty easy, you don't need to know all symfony internals, and  
> your
> help will be greatly appreciated.
>
> Fabien
>
> --
> Fabien Potencier
> Sensio CEO - symfony lead developer
> sensiolabs.com | symfony-project.com | aide-de-camp.org
> Tél: +33 1 40 99 80 80
>
>
> Melchior Anarchion wrote:
>> Hi,
>> if we need to put a message on the mailing list, to see the patch
>> applied it's a bit discouraging, i know symfony is a big project  
>> and it
>> represent a lot of work. the way that only confirmed skilled  
>> programmer
>> can commit to the main symfony branches is a good thing, but when i  
>> see
>> each week  X defect created and Y defect closed and X > Y i think
>> symfony going in the wall.
>>
>> i remember Fabien has show us a nice graph with the ticket life cycle
>> but it don"t see to be applyed. some tickets have more than 2 years  
>> and
>> perhaps nobody know if the bug is still there (just look the oldest  
>> bug )
>>
>>
>>
>> Kris Wallsmith a écrit :
>>> Thank you for your patch. It has been applied to 1.1 and 1.2. Please
>>> keep them coming!
>>>
>>> Kris
>>>
>>> On Oct 14, 7:12 pm, Yuretsz <[EMAIL PROTECTED]> wrote:
>>>
>>>> Ok, I have desire and skills to help Symfony became the best  
>>>> framework ever.
>>>>
>>>> The most easiest way is to fix some bugs in it.
>>>> Ok we have the manual of doing thishttp://trac.symfony- 
>>>> project.org/wiki/HowToContributeToSymfony#Submitt...
>>>>
>>>> To try how the whole thing works I looked into the bug tracker  
>>>> seeking
>>>> the easiest bug. To be sure that the patch is 100% correct.
>>>>
>>>> To test the whole bug fixing process was choosed ticket#4190  
>>>> symfony
>>>> generate:task --use-database option brokenhttp://trac.symfony- 
>>>> project.org/ticket/4190
>>>>
>>>> I've submitted patch for this bug more than 10 days bug the  
>>>> status of
>>>> this ticket not changed at all. No changes in the trunk also.
>>>>
>>>> What I'm doing wrong?
>>>>
>>>> --
>>>> ============================
>>>> Regards...
>>>>
>>>>
>>>
>>
>>
>>>
>>
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to