With Seam 3.0.0 on the horizon, it&#39;s time to get serious about putting together the Seam 2 to Seam 3 migration guide. The purpose of this thread is to capture requirements for this guide.<div><br></div><div>For a migration guide to be useful, it must be rooted in practical procedures rather than theoretical correlations. Therefore, before drafting a single paragraph, it’s important to capture the requirements for migration from the user community. We&#39;ll then seek to answer those questions in the guide. Once we have addressed those questions, we can fill-in the guide with more generalized mappings for completeness.</div>

<div><br></div><div>So I ask, &quot;what&#39;s your vision of an ideal migration guide?&quot;</div><div><br></div><div>We don&#39;t have to answer the questions in this guide, though if you feel compelled to answer a question, feel free to do so. Let&#39;s just try to stay focused on identifying your concerns and questions, then we can discuss the answers while reviewing the guide drafts.</div>

<div><br></div><div>Fire the requirements away. If you&#39;ve already written requirements somewhere on the web, you can just link to them.</div><div><br></div><div>-Dan<br><meta http-equiv="content-type" content="text/html; charset=utf-8"><br>

-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>

<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>
</div>