<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
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?<br>
<br>
On 17/02/11 00:51, Ken Finnigan wrote:
<blockquote
cite="mid:AANLkTimj8exbC1d75WtxmmeogoYgjXO=sOemrk_HOtS=@mail.gmail.com"
type="cite">Hi Shane,<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Unless anyone else has a bright spark as to how to proceed, the
above is the plan for i18n.<br>
<br>
Thanks<br>
Ken<br>
<br>
<br>
<div class="gmail_quote">On Tue, Feb 15, 2011 at 4:44 PM, Shane
Bryzak <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Hi Team,<br>
<br>
As you may have noticed, we released Seam 3.0.0.Beta2 over the
weekend.<br>
This was an important milestone and I'd like to thank everyone
for their<br>
hard work in making it happen. The next big release is
3.0.0.CR1, due<br>
at the end of this month. This release will be substantially
more<br>
important as it should closely resemble the final product that
we plan<br>
to release next month. By now, all APIs should be frozen, and
we should<br>
all be working on polishing up our modules, making sure the<br>
documentation and examples are complete, and any major issues
in JIRA<br>
are addressed.<br>
<br>
To ensure that we don't have a last minute rush to finish the
bundled CR<br>
release, I'd like to have all modules reach CR1 by Wednesday
next week<br>
(the 23rd of February) or even earlier if possible. If you
feel your<br>
module is complete enough for a CR release, please let me know
and I'll<br>
perform the release to Maven/Sourceforge for you - remember,
earlier is<br>
better! If you have outstanding issues that can be bumped to
the 3.0.1<br>
release, then please do so (I'll try to go through all the
projects in<br>
JIRA and set up future versions).<br>
<br>
Thanks,<br>
Shane<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/seam-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</blockquote>
</div>
<br>
</blockquote>
<br>
</body>
</html>