For now I would only change the <span style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;line-height:18px;text-align:left;background-color:rgb(245,245,245)"><a href="http://seamframework.org">http://seamframework.org</a> URL to be a link.</span><div>
<div style="text-align:left"><br></div><div style="text-align:left"><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="line-height:18px">Maybe making the "Classic Seam 2" Column wider.</span></font></div>
<div style="text-align:left"><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="line-height:18px"><br></span></font></div><div style="text-align:left"><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="line-height:18px">That's my 2 cents.</span></font></div>
<br><div class="gmail_quote">2012/7/5 Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com" target="_blank">pmuir@redhat.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All,<br>
<br>
Please review - <a href="http://www.jboss.org/jdf/stage/migrations/get-started/" target="_blank">http://www.jboss.org/jdf/stage/migrations/get-started/</a><br>
<span class="HOEnZb"><font color="#888888"><br>
Pete<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 28 Jun 2012, at 23:29, Pete Muir wrote:<br>
<br>
> One thing I picked up at Summit was that whilst people really appreciate the migration guides, they also want more advice on when (/whether) they should migrate, and what they should migrate too. We have the story pretty much sorted:<br>
><br>
> * if you have an app that works, and you want to keep running it on Seam 2.2, then great. We'll support that for X more years on EAP. Stay where you are.<br>
> * if you want to stay on Seam 2, but want to take advantage of the new features of Java EE 6, then you can take a look at Seam 2.3, which is currently beta quality. We haven't decided yet whether this will enter the supported product arena.<br>
> * if you want to take advantage of Java EE, you need to do a bit of analysis of your app:<br>
> ** if you have all the features you need in Java EE 6 (and look at TicketMonster, you can achieve a lot!) then migrate to Java EE 6<br>
> ** if you don't, but you can find them in DeltaSpike, and like living on the edge, then you can take the path of adding DeltaSpike to Java EE 6. But we don't have a well trodden path here, with guides for you to follow<br>
> ** otherwise, take a look at the jdf roadmap to see when the features you need will enter jdf, will all the goodness of the stack and guides<br>
><br>
> Comments? I'll get this written up for <a href="http://www.jboss.org/jdf/migrations/get-started/" target="_blank">http://www.jboss.org/jdf/migrations/get-started/</a> next week.<br>
> _______________________________________________<br>
> jdf-dev mailing list<br>
> <a href="mailto:jdf-dev@lists.jboss.org">jdf-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/jdf-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jdf-dev</a><br>
<br>
<br>
_______________________________________________<br>
jdf-dev mailing list<br>
<a href="mailto:jdf-dev@lists.jboss.org">jdf-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jdf-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jdf-dev</a><br>
</div></div></blockquote></div><br></div>