> Having commit-ready (tested) patches is a great help. Clearly stating > the problem, making a patch, tests and mentioning which browsers it > has been tested on is very helpful (doing any one of these steps is > appreciated too, of course :) )
Thanks Kangax for the reply - I'll be more diligent in the future about filing bugs. However, given that time seems to be the main constraint to more frequent releases (based on your post) would it be possible to set up some sort of nightly build to allow testers to help test the next release? If there was a 1.6.0.4-NIGHTLY (and possibly a 1.6.1-NIGHTLY) it would be much easier to test against a version with recent patches applied and help highlight what is broken, what is working, provide test cases, etc. Assuming that these nightly builds were relatively well-tested by users it would cut down on the work required of the core team, making more frequent releases (hopefully) an easier thing to do. I would assume the work required to set this up would be minimal (basically, run a nightly script against the appropriate GIT repositories) and would vastly simplify the process for those of us who try to follow the latest developments. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" 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/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
