All of the issues that were unassigned have now either been assigned or slipped to "The future". If I've assigned you an issue and you won't have time to look at it before the release, please slip it accordingly. Pete Muir wrote: > All, > > I would like to have a code freeze for Seam 2.1.0.CR1 Wednesday > 24th September. As usual, all issues marked Critical or Blocker > should be completed before this code freeze takes effect, so if you > have an issue you think must get in, make sure it is marked > Critical or Blocker. Please also review the issues assigned to you. > If they are critical, and you won't get them done in time, please > unassign them, otherwise please adjust their fix version accordingly. > > Christian: 2 exception handling issues > Dan: 3 seam-gen issues, 2 other bugs, 2 feature requests > Jay: 3 interop issues, 1 docs issue > Judy: 3 icefaces issues > Max: 1 JBDS / .exploded builder issue > Mike: 1 Spring issue > Norman: 2 URL rewrite issues > Pete: 2 wicket issues, 1 messages formatting issue, 3 deployment > issues, 1 passivation issue (3 critical issues) > Shane: 4 examples issues, 2 natural conversations issues, 2 other > (2 critical issues) > Unassigned: 26 issues (1 critical) > > Shane has been working though the unassigned issues, working out > whether they are critical or not. Shane, how is this going? Can you > mark any that should block the release as critical, and slip the > rest to "The future". > > Thanks! > > Pete _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev