Two notes that might help restore some confidence in the Merb release cycle:
1) Since "Merb 1.1 has been ready for several weeks", would it be possible for someone with access to cleanup Lighthouse so that there are not 75+ open tickets for 1.1? If it's ready to go, then those 75+ tickets should presumably be applied to future releases. Without reassigning or monitoring of the tickets, it's really difficult to understand where each release stands and greatly complicated the patching process for any new would-be contributors since they can't really gage the deployment and patch horizon. 2) Who should new tickets be assigned to by default? Could a "new ticket" user be created or something to that effect? There are lots of tickets that come in that never seem to get any assignment or acknowledgment that they have been seen. Thanks in advance. On Jun 29, 1:35 am, Matt Aimonetti <[email protected]> wrote: > Merb 1.1 has been almost ready for a few weeks now. -- sorry if this is a duplicate, doesn't seem to be posting correctly. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
