HI all, Are there any documented "rules of engagement" or best practices concerning committing patches, bug fixes, etc. for JIRA issues with respect to Seam 3.0, for example? 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?

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. 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?

thx. _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

On Thu, 2010-03-18 at 16:04 +1000, Shane Bryzak wrote: > On 18/03/10 15:36, Arbi Sookazian wrote: > >> HI all, >> >> Are there any documented "rules of engagement" or best practices >> concerning committing patches, bug fixes, etc. for JIRA issues with >> respect to Seam 3.0, for example? >> >> 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? >> > We work off trunk mainly, although for fixes that are backported they > are obviously applied to a branch. > >> 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. >> >> 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? >> > We use Hudson (hudson.jboss.org), I'll let one of the QA guys answer > the build question however I *think* it's triggered by commit. > Basically, the CI is being done by hudson jobs here: http://hudson.jboss.org/hudson/view/Seam/ Currently you can see two hudson jobs: Seam-modules-deploy-remoting and Seam-modules-deploy-xml. In our private instance of hudson we have hudson jobs for all Seam3 modules. The "remoting" job is triggered daily at midnight if there is any change in svn. We can setup this behaviour for all the modules if this is desired behaviour. Shane, WDYT?

Martin >> thx. >> >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev >

Hey Arbi, Long story short, we're still working on setting up the infrastructure and providing that information to everyone so they can be on the same page. Hopefully we'll have this under wraps soon, --Lincoln On Thu, Mar 18, 2010 at 1:36 AM, Arbi Sookazian <asookazian(a)gmail.com&gt;wrote: > HI all, > > Are there any documented "rules of engagement" or best practices > concerning committing patches, bug fixes, etc. for JIRA issues with respect > to Seam 3.0, for example? > > 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? > > 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. > > 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? > > thx. > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

Hey Arbi, Long story short, we're still working on setting up the infrastructure and providing that information to everyone so they can be on the same page. Hopefully we'll have this under wraps soon,

On Thu, Mar 18, 2010 at 11:41 AM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: > On Thu, Mar 18, 2010 at 10:31 AM, Lincoln Baxter, III < > lincolnbaxter(a)gmail.com&gt; wrote: > >> Hey Arbi, >> >> Long story short, we're still working on setting up the infrastructure >> and providing that information to everyone so they can be on the same page. >> >> Hopefully we'll have this under wraps soon, > > > I'll second Lincoln by saying that you have raised great > questions...questions that need to be addressed. And it just so happens we > are working on initiating discussions with the community as I write this. > Now is definitely the time to jump into Seam 3 and share your input and > ideas. I'm talking to Lincoln right now about putting together some wiki > pages that explain and document the process. Stay tuned. > > We'll try not to let us slow us down, but keep in mind we are also a man short for a while as Pete is on vacation this month :) -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://mojavelinux.com http://mojavelinux.com/seaminaction http://www.google.com/profiles/dan.j.allen

So as a matter of svn best practices, I'm wondering if it's best to create branches for each JIRA issue (esp. if they're more complicated enhancements, for example, that involve modifying/refactoring a lot of files and/or adding a lot of new files) or having all devs work right off the trunk? And maybe the answer depends on if it's a minor release (e.g. Seam 2.2) or patch fix release (e.g. Seam 2.2.1) or a large feature release like Seam 3.0....

In this specific case (Seam 3.0), there is no current production support so for now it seems like it may be ok to work directly from svn trunk (minus the broken build problem when bugs are committed). However, I have been involved in private JIRAs via the Redhat/JBoss CSP in the past (with SLAs of course) and that means the core devs will need access to a clean, working trunk for prod maintenance, bug fixes, etc. So I'd imagine in the future there will be a trunk and another future project branch at minimum. It must have been like this in the past? I would imagine Redhat/JBoss would have some kind of SCM standards but I work for a division of Intuit and we don't have current SDLC/SCM standards or best practices that I know of (or that are strictly enforced anyways). Unfortunately, we are "slated" to migrate to Perforce (commercial product with support but Collabnet offers support for SVN as well) in the near future and I'm sure that won't be widely positively accepted. Check this out: http://java.dzone.com/news/vcs-survey Anyways, looking forward to some good stuff from Seam 3. btw, from this link: http://anonsvn.jboss.org/repos/seam/modules/ I don't see a core module. The Seam 2.2.x core will be heavily refactored (or completely re-written/replaced) by Weld 1.0.x I'd imagine. But will it really be completely replaced? I can't imagine so if Seam3 will be backwards compatible with Seam 2.x apps... I'd like to try out Seam 3 eventually with our non-trivial Seam/RF/JPA/JSF app here (which consists of two Maven projects and a couple of common/infrustructural projects that are shared b/n projects here). I'm also wondering how backwards-compatible JSF 2 is. I tried it briefly with my app and experienced some problems (possibly due to misconfiguration?) so reverted back to JSF 1.2 Mojarra for now. It's tough to sell Java EE 6 at enterprise shops that tend to be conservative in terms of adopting technology (e.g. we like to stay 1 to 2 major revisions behind). thx. On Thu, Mar 18, 2010 at 9:00 AM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: On Thu, Mar 18, 2010 at 11:41 AM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: On Thu, Mar 18, 2010 at 10:31 AM, Lincoln Baxter, III <lincolnbaxter(a)gmail.com&gt; wrote: Hey Arbi, Long story short, we're still working on setting up the infrastructure and providing that information to everyone so they can be on the same page. Hopefully we'll have this under wraps soon, I'll second Lincoln by saying that you have raised great questions...questions that need to be addressed. And it just so happens we are working on initiating discussions with the community as I write this. Now is definitely the time to jump into Seam 3 and share your input and ideas. I'm talking to Lincoln right now about putting together some wiki pages that explain and document the process. Stay tuned. We'll try not to let us slow us down, but keep in mind we are also a man short for a while as Pete is on vacation this month :) -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://mojavelinux.com http://mojavelinux.com/seaminaction http://www.google.com/profiles/dan.j.allen _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev