<div class="gmail_quote">On Fri, Dec 11, 2009 at 6:00 PM, Jim Driscoll <span dir="ltr"><<a href="mailto:Jim.Driscoll@sun.com">Jim.Driscoll@sun.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
<br>
On 12/11/09 2:26 PM, Ed Burns wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
My plan was to merge the branch back into HEAD and do the work there.<br>
</blockquote>
<br></div>
I don't think 2.0 is ready to be the side branch yet. There's still a lot of work to do there.<br>
<br>
Similarly, as Dan notes, some of the changes, like h:inputFile, may possibly be disruptive.<br>
<br>
I'll let Ryan chime in - as lead, I'd prefer it be his call.<br>
<br>
This is also pending a decision about moving the VCS to some more modern system like mercurial or git - both of which are supported on Kenai. But my understanding is that we'd like to hear Oracle's plans before we commit one way or the other, as well as some indication from GF on which direction they're going as well (last I heard, it was mercurial on Kenai). We may want to avoid any big juggling till we have that sorted, and that's liable to be 2-3 months away. <br>
</blockquote></div><br>All of that sounds good.<br><br>I just wonder if we could create a prototype branch on Kenai in the short run that wouldn't affect any users of Mojarra and would let us play while we wait. We could kill it as soon as we do any sort of official migration.<br>
<br>-Dan<br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>