Please create a JIRA project for the Seam 3 JMS Module: SEAMJMS<div><br></div><div>Thanks.<br><br><div class="gmail_quote">On Wed, Apr 14, 2010 at 7:07 AM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
On 14 Apr 2010, at 12:05, Shane Bryzak wrote:<br>
<br>
> We now have the following SEAM project in JIRA:<br>
><br>
> <a href="https://jira.jboss.org/jira/browse/SEAM" target="_blank">https://jira.jboss.org/jira/browse/SEAM</a><br>
><br>
> The plan is to eventually remove the JBSEAM project,<br>
<br>
</div>Well, we won't remove it, so much as close it to new traffic.<br>
<div><div></div><div class="h5"><br>
> after all of its issues have been addressed in some way or another. As Pete said, all Seam 2 issues should stay put in the JBSEAM project, and Seam 3 and higher issues should now go in SEAM.<br>
><br>
> Shane<br>
><br>
> On 14/04/10 20:02, Pete Muir wrote:<br>
>> People,<br>
>><br>
>> We still need an issue tracker for tracking common Seam tasks:<br>
>><br>
>> * Build infrastructure<br>
>> * Common documentation<br>
>> * Shared examples<br>
>> * Simultaneous release tasks<br>
>> * A dumping ground for "new-users" to put issues which they don't know where they belong (it's then up to us to triage them to the correct place).<br>
>><br>
>> As we've diverged so much from Seam 2, I propose we create a new project in JIRA, SEAM, and keep JBSEAM for Seam 2 issues. This should reduce cross-over confusion between the two codebases' issues. It also has the nice sideeffect of allowing us to get rid of the unneeded JB prefix ;-)<br>
>><br>
>> If anyone disagrees, speak up. Otherwise I'll ask Rodney to do this later today.<br>
>><br>
>> Pete<br>
>><br>
>> On 10 Mar 2010, at 11:57, Pete Muir wrote:<br>
>><br>
>><br>
>>> All,<br>
>>><br>
>>> As we split Seam into modules (and as some like remoting and XML approach a beta release), we need to consider how JIRA should look for Seam 3.<br>
>>><br>
>>> We plan to release modules independently, with a "feature-boxed" lifecycle, releasing modules either as features are added, or critical issues arrive. We also plan a "bundle release" at regular intervals, which takes all the modules, and provides a single stack that are tested to work well together.<br>
>>><br>
>>> Keeping JIRA simple and monolithic has the advantage of being easy to understand and point people at. We can use components to track a module. We would have to prefix the version with the module name, and tracking issues to releases becomes pretty difficult.<br>
>>><br>
>>> Using a JIRA project for each module allows much cleaner tracking of issues to releases.<br>
>>><br>
>>> I favour the latter, but am interested in others opinions.<br>
>>><br>
>>> Pete<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>
>><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>
><br>
<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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Jordan Ganoff<br>
</div>