You can also fix the bug, make a patch (svn diff) and create a new ticket with the patch
Thomas On Mon, Apr 7, 2008 at 5:53 PM, Jay Klehr <[EMAIL PROTECTED]> wrote: > > You don't have enough access to "reopen" a ticket (neither do I). If you > did there would be a "button" for you to change the status of the ticket (it > would actually be in the form of a drop-down). > > Jay > > > > Joe Kelsey wrote: > I seem to be experiencing a very bad communication problem. > > I want to contribute to fixing symfony. The trac system seems to be > the way to do it. > > I think that the patch associated with ticket 3210 is completely and > totally WRONG. I am very sorry if you invested any sort of reputation > in asserting its correctness, but I think I have very valid reasons > for my opinion. > > Now I want to modify 3210 to show that it is not in COMPLETE state. I > cannot find any documentation related to this TRAC system to tell me > how to do it. I rely completely on the buttons provided for me to > press from the web interface, and all I can do is reply and post my > issues there. If you would rather that I post my replies here in this > list I will. > > If you want me to take out a contract with sensio to be able to > interact directly with you, all you have to do is contact me and tell > me the terms. If symfony is really a sensio product that I have to > pay for, please let me know. If it is really and open-source product, > then I will continue to post my bugs and other things here. > > I really think that the overall product is very good. I use it > daily. I don't know what more I need to say. > > Where do I go to find information on using this TRAC thing that you > seem to want to use? Somewhere on the symfony site you have to but > the help files for all of the tools you use if you want others to use > them to help you fix bugs. > > /Joe > > On Apr 5, 12:02 am, Fabien POTENCIER <[EMAIL PROTECTED] > project.com> wrote: > > > The bug IS fixed. > > The fixture file takes class names as main keys, not table names. But > I'm sure you already know that as it's well described in the symfony book. > > If you think there is still a bug, please open a new ticket, describe > the problem, attach a patch that fixes the problem with unit tests that > prove the patch, and prepend the ticket description with [PATCH]. > > The core team read all tickets as they are created. My first reply to > the ticket was exactly 35 minutes after the ticket creation! And the fix > was commited less than 24 hours later. > > Thanks, > 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 > > Joe Kelsey wrote: > > > I have added two comments to ticket #3210 to explain how IT IS NOT > FIXED! > > > TICKET 3210 IS NOT FIXED! > > > How do I mark it so that someone will notice and rework it? I cannot > seem to enter tickets that anyone will willing look at. I have > described several different bugs in the system and nothing seems to > happen. I think that the ticket system is fine, but it seems very > difficult to get anyone to notice that new tickets appear. If you do > not want users to enter tickets, say so. If you want ordinary users > to enter tickets please explain how exactly to do it. > > > /Joe > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en -~----------~----~----~----~------~----~------~--~---
