There's some minor cleanup and housekeeping that needs to be done, which I should be able to do over the weekend. Would aim for a CR1 early next week.
On Wed, Feb 16, 2011 at 4:01 PM, Shane Bryzak <[email protected]> wrote: > That's fine Ken, I'd rather delay the feature and spend the time required > to get it right than try to rush something out for the release. Besides > that, is there any other outstanding work you'd like to get done to the > international module, or can we go ahead and release CR1 now? > > > On 17/02/11 00:51, Ken Finnigan wrote: > > Hi Shane, > > For the i18n module I don't expect us to be in a position to support type > safe messages for CR1, as I don't expect us to have the annotation processor > we need in a state that we can use until next week at the earliest, and even > then it would only be a snapshot version. > > My plan, unless anyone else has a bright spark, is to have a fast follower > release of i18n for either 3.1 or 4.0 (depending on how much we break the > API and everyone's thoughts) that includes the type safe message annotations > within a couple of months of Seam 3.0.0.CR1, and for the release next week I > simply clean up the existing API to get it closer to what will be in place > once type safe messaging is available. > > I really wanted to be able to get type safe messaging into the first > version of Seam 3, but I honestly don't see that happening for next week. > > Unless anyone else has a bright spark as to how to proceed, the above is > the plan for i18n. > > Thanks > Ken > > > On Tue, Feb 15, 2011 at 4:44 PM, Shane Bryzak <[email protected]> wrote: > >> Hi Team, >> >> As you may have noticed, we released Seam 3.0.0.Beta2 over the weekend. >> This was an important milestone and I'd like to thank everyone for their >> hard work in making it happen. The next big release is 3.0.0.CR1, due >> at the end of this month. This release will be substantially more >> important as it should closely resemble the final product that we plan >> to release next month. By now, all APIs should be frozen, and we should >> all be working on polishing up our modules, making sure the >> documentation and examples are complete, and any major issues in JIRA >> are addressed. >> >> To ensure that we don't have a last minute rush to finish the bundled CR >> release, I'd like to have all modules reach CR1 by Wednesday next week >> (the 23rd of February) or even earlier if possible. If you feel your >> module is complete enough for a CR release, please let me know and I'll >> perform the release to Maven/Sourceforge for you - remember, earlier is >> better! If you have outstanding issues that can be bumped to the 3.0.1 >> release, then please do so (I'll try to go through all the projects in >> JIRA and set up future versions). >> >> Thanks, >> 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
