Hi, I haven't had any time for Cron for quite a few weeks now and have no idea when I'll next be able to contribute to it. It's currently stable except for one bug which is fixed in git, but it lacks anything but the most basic of features. Eg there's no storing schedules in the database etc. Also there's a pull request from Dave Oxley which I haven't had time to properly go through. I think that one can possibly be prioritised lower as it adds a fairly advanced concept which changes the SPI a little bit, but on the other hand all of Dave's future contributions will likely depend on that so I'm probably causing quite a bottleneck there. Everything else is in JIRA.
It might be necessary for another volunteer, or perhaps someone from JBoss to step in and pick up the slack in order to have something worthwhile to release in 3 week's time. Sorry. Cheers, Pete. On 25/07/2011, at 3:53 AM, George Gastaldi wrote: > Seam reports is alpha1 but quite stable to be a beta > > Em 24/07/2011, às 21:42, Shane Bryzak <[email protected]> escreveu: > >> A minimum of a beta level release is the target, if you're at CR already for >> Seam JMS then that's even better. >> >> On 25/07/11 10:27, John D. Ament wrote: >>> >>> Shane >>> >>> What versions are you expecting for everyone? Seam JMS is at CR and JCR is >>> about to go beta. >>> >>> John >>> >>> On Jul 24, 2011 7:33 PM, "Shane Bryzak" <[email protected]> wrote: >>> > Just a heads up to everyone that we only have 3 weeks remaining until >>> > the beta 1 release for Seam 3.1. It would be appreciated if all module >>> > leads could reply to this with a status update for your module, and >>> > whether you foresee any issues with delivering a beta for your module >>> > within this timeframe. >>> > >>> > I'd also like to remind everyone that we are getting rid of the shaded >>> > (combined) jars, so if you need assistance in doing this for your module >>> > please let me know and I can help out. >>> > >>> > Shane >>> > _______________________________________________ >>> > seam-dev mailing list >>> > [email protected] >>> > https://lists.jboss.org/mailman/listinfo/seam-dev >> >> _______________________________________________ >> seam-dev mailing list >> [email protected] >> https://lists.jboss.org/mailman/listinfo/seam-dev > _______________________________________________ > seam-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
