On Thursday, 19 July 2012 13:49:54 UTC+1, Stuart McCulloch wrote: > > I think it's definitely time to go and start tagging issues that should be > fixed before 3.1, for example: > > http://code.google.com/p/google-guice/issues/detail?id=709 > > is a potential candidate. >
+1 FYI, the current issues tagged as 3.1 candidates are: > > http://code.google.com/p/google-guice/issues/list?q=label%3A3.1 > > once we know what needs to be fixed, we can start planning for 3.1 and > maybe do some RCs :) > This would be great, of course. On the other hand, if people are busy, one approach would be to focus on regressions from the latest release and fixes that could not be done in a subsequent bug-fix release. Best, Ismael -- You received this message because you are subscribed to the Google Groups "google-guice" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-guice/-/3FEfBR5LCKwJ. 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/google-guice?hl=en.
