Hey Arbi,<br><br>Long story short, we&#39;re still working on setting up the infrastructure and providing that information to everyone so they can be on the same page.<br><br>Hopefully we&#39;ll have this under wraps soon,<br>
--Lincoln<br><br><div class="gmail_quote">On Thu, Mar 18, 2010 at 1:36 AM, Arbi Sookazian <span dir="ltr">&lt;<a href="mailto:asookazian@gmail.com">asookazian@gmail.com</a>&gt;</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 all,<br><br>Are there any documented &quot;rules of engagement&quot; or best practices concerning committing patches, bug fixes, etc. for JIRA issues with respect to Seam 3.0, for example?<br><br>Specifically, do the Seam core devs and miscellaneous committers work directly off of trunk for all JIRA issues for a particular release or do they create a separate branch for each JIRA issue which is then reintegrated back into trunk?<br>

<br>If the latter, then what about using Mylyn in Eclipse for task mgmt and context mgmt?  The activation of tasks and tracking of change sets by Mylyn are useful in Eclipse workspaces where there are multiple JIRA issues (or tasks) to work on and isolate context for.<br>

<br>And is a continuous integration server like Hudson or Continuum used as well?  Is a build created by the CI server every time a file or change set is committed to trunk or is it schedule by CRON job?<br><br>thx.<br>
<br>_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>&quot;Keep it Simple&quot;<br>