All, This Drools upgrade, and a probable upgrade to jBPM 4 (happening due to these products needed in the JBoss SOA platform 5, based on EAP 5, which in turn includes Seam) mean that we need to make the release Seam 2.2 (which I said would never happen, I know ;-) Due to the concentration on Web Beans / Seam 3 there hasn't been a huge amount of activity recently, however 2.2 will include: * 112 issues closed (please direct your thanks to Norman here - he has been soldiering away!) * improvements to Seam-gen (Glassfish, IDEA etc.) from Dan * big improvements to REST support - Christian and Jozef * Drools and jBPM upgrades So, I suggest that Norman and Marek (can you coordinate with each other) handle the jBPM upgrade (Tom just released alpha2, and plans the GA in the mid summer) - we should wait until there is a beta out I think for Seam 2.2 GA... Tom, any rough guess when this will be? Assuming Tom has a beta, I propose this schedule: Seam 2.2.0 CR1 - Wednesday 22nd April Seam 2.2.0 - Wednesday 13th May Seam 2.2.1 CR1 - Wednesday 17th June Seam 2.2.1 - Wednesday 8th July (hopefully just after the jBPM GA) This will be the first time for time-boxing our releases too, something we are doing for Web Beans, and will do for Seam3. Anne-Louise, could you please comment on how these dates fit with EAP5 component freezes? Will we be able to get 2.2.1 in? Thanks! Begin forwarded message: > From: "Stefano Travelli (JIRA)" <jira-events(a)lists.jboss.org&gt; > Date: 18 March 2009 00:23:22 GMT > To: pete.muir(a)jboss.org > Subject: [JBoss JIRA] Commented: (JBSEAM-4011) Upgrade Drools > framework integration to version 5 > > > [ > https://jira.jboss.org/jira/browse/JBSEAM-4011?page=com.atlassian.jira.pl... > ] > > Stefano Travelli commented on JBSEAM-4011: > ------------------------------------------ > > As far as I know, drools 5 is not a drop in replacement of drools > 4.0.7. Lots of dependencies change (mvel and antlr for instance) and > most of all there are several API changes that make Seam after > changeset #10170 not compatible with Drools 4 forcing a migration to > Drools 5 in the run time environment of existing applications. > > At least, a detailed migration path for existing application is > needed. However, even after accomplished all dependencies, rules in my > application don't compile anymore. > > Actually, in my opinion this upgrade is unfitted for a maintenance > release of Seam. > >> Upgrade Drools framework integration to version 5 >> ------------------------------------------------- >> >> Key: JBSEAM-4011 >> URL: https://jira.jboss.org/jira/browse/JBSEAM-4011 >> Project: Seam >> Issue Type: Feature Request >> Components: Drools >> Reporter: Marek Novotny >> Assignee: Marek Novotny >> Fix For: 2.1.2.CR1 >> >> >> Upgrade Drools framework integration to current development version >> of Drools 5. It is now available 5.0.0.CR1 version. > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the > administrators: https://jira.jboss.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > -- Pete Muir http://www.seamframework.org http://in.relation.to/Bloggers/Pete

Does this mean that we wouldn't have a 2.1.2 with those 112 issues closed and the big improvements to REST support? As a Seam user I hope in a roadmap with a Drools4/jBpm3 Seam 2.1.x branch where bug fixing could continue for a while. stefano 2009/3/18 Tom Baeyens <tbaeyens(a)redhat.com&gt;: > In my original plan, Pageflow was only targetted after July. > > Pete, if one of your people can drive the pageflow migration, then > I can be > there to guide it. That way we can move it forward to april. > > Including jBPM 4 beta as part of your GA might not be a good idea. > jBPM > database schema will change. And that could cause serious upgrade > problems > for SEAM users using jBPM. Also upgrade from jBPM 3 to jBPM 4 will > be > impossible for now. > > regards, tom. > > > > Pete Muir wrote: >> >> All, >> >> This Drools upgrade, and a probable upgrade to jBPM 4 (happening >> due to >> these products needed in the JBoss SOA platform 5, based on EAP 5, >> which in >> turn includes Seam) mean that we need to make the release Seam 2.2 >> (which I >> said would never happen, I know ;-) >> >> Due to the concentration on Web Beans / Seam 3 there hasn't been a >> huge >> amount of activity recently, however 2.2 will include: >> >> * 112 issues closed (please direct your thanks to Norman here - he >> has >> been soldiering away!) >> * improvements to Seam-gen (Glassfish, IDEA etc.) from Dan >> * big improvements to REST support - Christian and Jozef >> * Drools and jBPM upgrades >> >> So, I suggest that Norman and Marek (can you coordinate with each >> other) >> handle the jBPM upgrade (Tom just released alpha2, and plans the >> GA in the >> mid summer) - we should wait until there is a beta out I think for >> Seam 2.2 >> GA... Tom, any rough guess when this will be? >> >> Assuming Tom has a beta, I propose this schedule: >> >> Seam 2.2.0 CR1 - Wednesday 22nd April >> Seam 2.2.0 - Wednesday 13th May >> >> Seam 2.2.1 CR1 - Wednesday 17th June >> Seam 2.2.1 - Wednesday 8th July (hopefully just after the jBPM GA) >> >> This will be the first time for time-boxing our releases too, >> something we >> are doing for Web Beans, and will do for Seam3. >> >> Anne-Louise, could you please comment on how these dates fit with >> EAP5 >> component freezes? Will we be able to get 2.2.1 in? >> >> Thanks! >> >> Begin forwarded message: >> >>> From: "Stefano Travelli (JIRA)" <jira-events(a)lists.jboss.org&gt; >>> Date: 18 March 2009 00:23:22 GMT >>> To: pete.muir(a)jboss.org >>> Subject: [JBoss JIRA] Commented: (JBSEAM-4011) Upgrade Drools >>> framework >>> integration to version 5 >>> >>> >>> [ >>> https://jira.jboss.org/jira/browse/JBSEAM-4011?page=com.atlassian.jira.pl... >>> #action_12457785 >>> ] >>> >>> Stefano Travelli commented on JBSEAM-4011: >>> ------------------------------------------ >>> >>> As far as I know, drools 5 is not a drop in replacement of drools >>> 4.0.7. >>> Lots of dependencies change (mvel and antlr for instance) and >>> most of all >>> there are several API changes that make Seam after changeset >>> #10170 not >>> compatible with Drools 4 forcing a migration to Drools 5 in the >>> run time >>> environment of existing applications. >>> >>> At least, a detailed migration path for existing application is >>> needed. >>> However, even after accomplished all dependencies, rules in my >>> application >>> don't compile anymore. >>> >>> Actually, in my opinion this upgrade is unfitted for a maintenance >>> release of Seam. >>> >>>> Upgrade Drools framework integration to version 5 >>>> ------------------------------------------------- >>>> >>>> Key: JBSEAM-4011 >>>> URL: https://jira.jboss.org/jira/browse/JBSEAM-4011 >>>> Project: Seam >>>> Issue Type: Feature Request >>>> Components: Drools >>>> Reporter: Marek Novotny >>>> Assignee: Marek Novotny >>>> Fix For: 2.1.2.CR1 >>>> >>>> >>>> Upgrade Drools framework integration to current development >>>> version of >>>> Drools 5. It is now available 5.0.0.CR1 version. >>> >>> -- >>> This message is automatically generated by JIRA. >>> - >>> If you think it was sent incorrectly contact one of the >>> administrators: >>> https://jira.jboss.org/jira/secure/Administrators.jspa >>> - >>> For more information on JIRA, see: http://www.atlassian.com/software/jira >>> >>> >> >> -- >> Pete Muir >> http://www.seamframework.org >> http://in.relation.to/Bloggers/Pete >> > > -- > regards, tom. > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev >

Can you tell us what the earliest release we should put in 2.2.0 is? And roughly what date we can target? If we don't have time to do 2.2.0 and 2.2.1, I guess we could do:

On 18 Mar 2009, at 07:51, Tom Baeyens wrote: > In my original plan, Pageflow was only targetted after July. > > Pete, if one of your people can drive the pageflow migration, then I > can be there to guide it. That way we can move it forward to april. Yes, I think we can do that (I was assuming that was the plan anyway). > > > Including jBPM 4 beta as part of your GA might not be a good idea. > jBPM database schema will change. And that could cause serious > upgrade problems for SEAM users using jBPM. Also upgrade from jBPM 3 > to jBPM 4 will be impossible for now. Can you tell us what the earliest release we should put in 2.2.0 is? And roughly what date we can target? If we don't have time to do 2.2.0 and 2.2.1, I guess we could do: Seam 2.2.0.BETA1 - Wednesday 22nd April Seam 2.2.0.CR1 - Wednesday 13th May Seam 2.2.0 - Wednesday 17th June Tom and Anne-Louise, how do these dates fit your respective schedules? > > > regards, tom. > > > > Pete Muir wrote: >> All, >> This Drools upgrade, and a probable upgrade to jBPM 4 (happening due >> to these products needed in the JBoss SOA platform 5, based on EAP 5, >> which in turn includes Seam) mean that we need to make the release >> Seam 2.2 (which I said would never happen, I know ;-) >> Due to the concentration on Web Beans / Seam 3 there hasn't been a >> huge amount of activity recently, however 2.2 will include: >> * 112 issues closed (please direct your thanks to Norman here - he >> has been soldiering away!) >> * improvements to Seam-gen (Glassfish, IDEA etc.) from Dan >> * big improvements to REST support - Christian and Jozef >> * Drools and jBPM upgrades >> So, I suggest that Norman and Marek (can you coordinate with each >> other) handle the jBPM upgrade (Tom just released alpha2, and plans >> the GA in the mid summer) - we should wait until there is a beta out >> I think for Seam 2.2 GA... Tom, any rough guess when this will be? >> Assuming Tom has a beta, I propose this schedule: >> Seam 2.2.0 CR1 - Wednesday 22nd April >> Seam 2.2.0 - Wednesday 13th May >> Seam 2.2.1 CR1 - Wednesday 17th June >> Seam 2.2.1 - Wednesday 8th July (hopefully just after the jBPM GA) >> This will be the first time for time-boxing our releases too, >> something we are doing for Web Beans, and will do for Seam3. >> Anne-Louise, could you please comment on how these dates fit with >> EAP5 component freezes? Will we be able to get 2.2.1 in? >> Thanks! >> Begin forwarded message: >>> From: "Stefano Travelli (JIRA)" <jira-events(a)lists.jboss.org&gt; >>> Date: 18 March 2009 00:23:22 GMT >>> To: pete.muir(a)jboss.org >>> Subject: [JBoss JIRA] Commented: (JBSEAM-4011) Upgrade Drools >>> framework integration to version 5 >>> >>> >>> [ >>> https://jira.jboss.org/jira/browse/JBSEAM-4011?page=com.atlassian.jira.pl... >>> ] >>> >>> Stefano Travelli commented on JBSEAM-4011: >>> ------------------------------------------ >>> >>> As far as I know, drools 5 is not a drop in replacement of drools >>> 4.0.7. Lots of dependencies change (mvel and antlr for instance) and >>> most of all there are several API changes that make Seam after >>> changeset #10170 not compatible with Drools 4 forcing a migration to >>> Drools 5 in the run time environment of existing applications. >>> >>> At least, a detailed migration path for existing application is >>> needed. However, even after accomplished all dependencies, rules in >>> my application don't compile anymore. >>> >>> Actually, in my opinion this upgrade is unfitted for a maintenance >>> release of Seam. >>> >>>> Upgrade Drools framework integration to version 5 >>>> ------------------------------------------------- >>>> >>>> Key: JBSEAM-4011 >>>> URL: https://jira.jboss.org/jira/browse/JBSEAM-4011 >>>> Project: Seam >>>> Issue Type: Feature Request >>>> Components: Drools >>>> Reporter: Marek Novotny >>>> Assignee: Marek Novotny >>>> Fix For: 2.1.2.CR1 >>>> >>>> >>>> Upgrade Drools framework integration to current development version >>>> of Drools 5. It is now available 5.0.0.CR1 version. >>> >>> -- >>> This message is automatically generated by JIRA. >>> - >>> If you think it was sent incorrectly contact one of the >>> administrators: https://jira.jboss.org/jira/secure/Administrators.jspa >>> - >>> For more information on JIRA, see: >>> http://www.atlassian.com/software/jira >>> >>> >> -- >> Pete Muir >> http://www.seamframework.org >> http://in.relation.to/Bloggers/Pete > > -- > regards, tom. > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev -- Pete Muir http://www.seamframework.org http://in.relation.to/Bloggers/Pete

Sorry to leave everyone hanging. Anne Louise is working on how we can best integrate Seam 2 w/ jBPM 4 / Drools 5 into EAP 5. We have a tentative plan, which should be finalised soon. On 18 Mar 2009, at 10:49, Pete Muir wrote: > > On 18 Mar 2009, at 07:51, Tom Baeyens wrote: > >> In my original plan, Pageflow was only targetted after July. >> >> Pete, if one of your people can drive the pageflow migration, then >> I can be there to guide it. That way we can move it forward to >> april. > > Yes, I think we can do that (I was assuming that was the plan > anyway). > >> >> >> Including jBPM 4 beta as part of your GA might not be a good >> idea. jBPM database schema will change. And that could cause >> serious upgrade problems for SEAM users using jBPM. Also upgrade >> from jBPM 3 to jBPM 4 will be impossible for now. > > Can you tell us what the earliest release we should put in 2.2.0 > is? And roughly what date we can target? If we don't have time to > do 2.2.0 and 2.2.1, I guess we could do: > > Seam 2.2.0.BETA1 - Wednesday 22nd April > Seam 2.2.0.CR1 - Wednesday 13th May > Seam 2.2.0 - Wednesday 17th June > > Tom and Anne-Louise, how do these dates fit your respective > schedules? > >> >> >> regards, tom. >> >> >> >> Pete Muir wrote: >>> All, >>> This Drools upgrade, and a probable upgrade to jBPM 4 (happening >>> due to these products needed in the JBoss SOA platform 5, based >>> on EAP 5, which in turn includes Seam) mean that we need to make >>> the release Seam 2.2 (which I said would never happen, I know ;-) >>> Due to the concentration on Web Beans / Seam 3 there hasn't been >>> a huge amount of activity recently, however 2.2 will include: >>> * 112 issues closed (please direct your thanks to Norman here - >>> he has been soldiering away!) >>> * improvements to Seam-gen (Glassfish, IDEA etc.) from Dan >>> * big improvements to REST support - Christian and Jozef >>> * Drools and jBPM upgrades >>> So, I suggest that Norman and Marek (can you coordinate with each >>> other) handle the jBPM upgrade (Tom just released alpha2, and >>> plans the GA in the mid summer) - we should wait until there is a >>> beta out I think for Seam 2.2 GA... Tom, any rough guess when >>> this will be? >>> Assuming Tom has a beta, I propose this schedule: >>> Seam 2.2.0 CR1 - Wednesday 22nd April >>> Seam 2.2.0 - Wednesday 13th May >>> Seam 2.2.1 CR1 - Wednesday 17th June >>> Seam 2.2.1 - Wednesday 8th July (hopefully just after the jBPM GA) >>> This will be the first time for time-boxing our releases too, >>> something we are doing for Web Beans, and will do for Seam3. >>> Anne-Louise, could you please comment on how these dates fit with >>> EAP5 component freezes? Will we be able to get 2.2.1 in? >>> Thanks! >>> Begin forwarded message: >>>> From: "Stefano Travelli (JIRA)" <jira-events(a)lists.jboss.org&gt; >>>> Date: 18 March 2009 00:23:22 GMT >>>> To: pete.muir(a)jboss.org >>>> Subject: [JBoss JIRA] Commented: (JBSEAM-4011) Upgrade Drools >>>> framework integration to version 5 >>>> >>>> >>>> [ https://jira.jboss.org/jira/browse/JBSEAM-4011?page=com.atlassian.jira.pl... >>>> #action_12457785 ] >>>> >>>> Stefano Travelli commented on JBSEAM-4011: >>>> ------------------------------------------ >>>> >>>> As far as I know, drools 5 is not a drop in replacement of >>>> drools 4.0.7. Lots of dependencies change (mvel and antlr for >>>> instance) and most of all there are several API changes that >>>> make Seam after changeset #10170 not compatible with Drools 4 >>>> forcing a migration to Drools 5 in the run time environment of >>>> existing applications. >>>> >>>> At least, a detailed migration path for existing application is >>>> needed. However, even after accomplished all dependencies, rules >>>> in my application don't compile anymore. >>>> >>>> Actually, in my opinion this upgrade is unfitted for a >>>> maintenance release of Seam. >>>> >>>>> Upgrade Drools framework integration to version 5 >>>>> ------------------------------------------------- >>>>> >>>>> Key: JBSEAM-4011 >>>>> URL: https://jira.jboss.org/jira/browse/JBSEAM-4011 >>>>> Project: Seam >>>>> Issue Type: Feature Request >>>>> Components: Drools >>>>> Reporter: Marek Novotny >>>>> Assignee: Marek Novotny >>>>> Fix For: 2.1.2.CR1 >>>>> >>>>> >>>>> Upgrade Drools framework integration to current development >>>>> version of Drools 5. It is now available 5.0.0.CR1 version. >>>> >>>> -- >>>> This message is automatically generated by JIRA. >>>> - >>>> If you think it was sent incorrectly contact one of the >>>> administrators: https://jira.jboss.org/jira/secure/Administrators.jspa >>>> - >>>> For more information on JIRA, see: http://www.atlassian.com/software/jira >>>> >>>> >>> -- >>> Pete Muir >>> http://www.seamframework.org >>> http://in.relation.to/Bloggers/Pete >> >> -- >> regards, tom. >> >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev > > -- > Pete Muir > http://www.seamframework.org > http://in.relation.to/Bloggers/Pete > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev -- Pete Muir http://www.seamframework.org http://in.relation.to/Bloggers/Pete _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

I blogged about release plans: http://in.relation.to/Bloggers/TheStateOfSeam Marek, can you roll back the Drools 5 upgrade in trunk for now? We'll branch after in the release for 2.1/2.2.

Thanks! Pete Muir wrote: > Sorry to leave everyone hanging. Anne Louise is working on how we can > best integrate Seam 2 w/ jBPM 4 / Drools 5 into EAP 5. We have a > tentative plan, which should be finalised soon. > > On 18 Mar 2009, at 10:49, Pete Muir wrote: > >> >> On 18 Mar 2009, at 07:51, Tom Baeyens wrote: >> >>> In my original plan, Pageflow was only targetted after July. >>> >>> Pete, if one of your people can drive the pageflow migration, then I >>> can be there to guide it. That way we can move it forward to april. >> >> Yes, I think we can do that (I was assuming that was the plan anyway). >> >>> >>> >>> Including jBPM 4 beta as part of your GA might not be a good idea. >>> jBPM database schema will change. And that could cause serious >>> upgrade problems for SEAM users using jBPM. Also upgrade from jBPM >>> 3 to jBPM 4 will be impossible for now. >> >> Can you tell us what the earliest release we should put in 2.2.0 is? >> And roughly what date we can target? If we don't have time to do >> 2.2.0 and 2.2.1, I guess we could do: >> >> Seam 2.2.0.BETA1 - Wednesday 22nd April >> Seam 2.2.0.CR1 - Wednesday 13th May >> Seam 2.2.0 - Wednesday 17th June >> >> Tom and Anne-Louise, how do these dates fit your respective schedules? >> >>> >>> >>> regards, tom. >>> >>> >>> >>> Pete Muir wrote: >>>> All, >>>> This Drools upgrade, and a probable upgrade to jBPM 4 (happening >>>> due to these products needed in the JBoss SOA platform 5, based on >>>> EAP 5, which in turn includes Seam) mean that we need to make the >>>> release Seam 2.2 (which I said would never happen, I know ;-) >>>> Due to the concentration on Web Beans / Seam 3 there hasn't been a >>>> huge amount of activity recently, however 2.2 will include: >>>> * 112 issues closed (please direct your thanks to Norman here - he >>>> has been soldiering away!) >>>> * improvements to Seam-gen (Glassfish, IDEA etc.) from Dan >>>> * big improvements to REST support - Christian and Jozef >>>> * Drools and jBPM upgrades >>>> So, I suggest that Norman and Marek (can you coordinate with each >>>> other) handle the jBPM upgrade (Tom just released alpha2, and plans >>>> the GA in the mid summer) - we should wait until there is a beta >>>> out I think for Seam 2.2 GA... Tom, any rough guess when this will be? >>>> Assuming Tom has a beta, I propose this schedule: >>>> Seam 2.2.0 CR1 - Wednesday 22nd April >>>> Seam 2.2.0 - Wednesday 13th May >>>> Seam 2.2.1 CR1 - Wednesday 17th June >>>> Seam 2.2.1 - Wednesday 8th July (hopefully just after the jBPM GA) >>>> This will be the first time for time-boxing our releases too, >>>> something we are doing for Web Beans, and will do for Seam3. >>>> Anne-Louise, could you please comment on how these dates fit with >>>> EAP5 component freezes? Will we be able to get 2.2.1 in? >>>> Thanks! >>>> Begin forwarded message: >>>>> From: "Stefano Travelli (JIRA)" <jira-events(a)lists.jboss.org&gt; >>>>> Date: 18 March 2009 00:23:22 GMT >>>>> To: pete.muir(a)jboss.org >>>>> Subject: [JBoss JIRA] Commented: (JBSEAM-4011) Upgrade Drools >>>>> framework integration to version 5 >>>>> >>>>> >>>>> [ >>>>> https://jira.jboss.org/jira/browse/JBSEAM-4011?page=com.atlassian.jira.pl... >>>>> ] >>>>> >>>>> Stefano Travelli commented on JBSEAM-4011: >>>>> ------------------------------------------ >>>>> >>>>> As far as I know, drools 5 is not a drop in replacement of drools >>>>> 4.0.7. Lots of dependencies change (mvel and antlr for instance) >>>>> and most of all there are several API changes that make Seam after >>>>> changeset #10170 not compatible with Drools 4 forcing a migration >>>>> to Drools 5 in the run time environment of existing applications. >>>>> >>>>> At least, a detailed migration path for existing application is >>>>> needed. However, even after accomplished all dependencies, rules >>>>> in my application don't compile anymore. >>>>> >>>>> Actually, in my opinion this upgrade is unfitted for a maintenance >>>>> release of Seam. >>>>> >>>>>> Upgrade Drools framework integration to version 5 >>>>>> ------------------------------------------------- >>>>>> >>>>>> Key: JBSEAM-4011 >>>>>> URL: https://jira.jboss.org/jira/browse/JBSEAM-4011 >>>>>> Project: Seam >>>>>> Issue Type: Feature Request >>>>>> Components: Drools >>>>>> Reporter: Marek Novotny >>>>>> Assignee: Marek Novotny >>>>>> Fix For: 2.1.2.CR1 >>>>>> >>>>>> >>>>>> Upgrade Drools framework integration to current development >>>>>> version of Drools 5. It is now available 5.0.0.CR1 version. >>>>> >>>>> -- >>>>> This message is automatically generated by JIRA. >>>>> - >>>>> If you think it was sent incorrectly contact one of the >>>>> administrators: >>>>> https://jira.jboss.org/jira/secure/Administrators.jspa >>>>> - >>>>> For more information on JIRA, see: >>>>> http://www.atlassian.com/software/jira >>>>> >>>>> >>>> -- >>>> Pete Muir >>>> http://www.seamframework.org >>>> http://in.relation.to/Bloggers/Pete >>> >>> -- >>> regards, tom. >>> >>> _______________________________________________ >>> seam-dev mailing list >>> seam-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> -- >> Pete Muir >> http://www.seamframework.org >> http://in.relation.to/Bloggers/Pete >> >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev > > -- > Pete Muir > http://www.seamframework.org > http://in.relation.to/Bloggers/Pete > > _______________________________________________ > 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

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknUdoMACgkQU4HO8G8hNxUvtgCghnPEM7R4Onsn+IKnD0GrWmhW jv0AoMx5ccRMiSwa7VOPR7I1XQkTH/I8 =tGc6 -----END PGP SIGNATURE-----

I blogged about release plans: http://in.relation.to/Bloggers/TheStateOfSeam

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan, I did rollback of Drools 5 changes, I have noticed that this influences seam-gen sources. I also reverted seam-gen elements so check these, if all is OK. Dan Allen napsal(a): > Please note that rolling back a dependency like Drools has a ripple effect > into seam-gen. The deployed-jars*.list files must be updated (if the > artifact name changes, as was the case with Drools 5 and MVEL), the IDE > project files must be updated, and the Ivy dependencies file must be > updated. Yes, it sucks, which is why we have seam-gen encore in the > works...but I'm just saying that you have to let me know excactly when you > are changing it so that I can react. > > -Dan > > On Thu, Apr 2, 2009 at 3:56 AM, Pete Muir <pmuir(a)redhat.com&gt; wrote: > >> I blogged about release plans: >> >> http://in.relation.to/Bloggers/TheStateOfSeam >> >> Marek, can you roll back the Drools 5 upgrade in trunk for now? We'll >> branch after in the release for 2.1/2.2. >> >> Thanks! >> >> >> Pete Muir wrote: >> >>> Sorry to leave everyone hanging. Anne Louise is working on how we can best >>> integrate Seam 2 w/ jBPM 4 / Drools 5 into EAP 5. We have a tentative plan, >>> which should be finalised soon. >>> >>> On 18 Mar 2009, at 10:49, Pete Muir wrote: >>> >>> >>>> On 18 Mar 2009, at 07:51, Tom Baeyens wrote: >>>> >>>> In my original plan, Pageflow was only targetted after July. >>>>> Pete, if one of your people can drive the pageflow migration, then I can >>>>> be there to guide it. That way we can move it forward to april. >>>>> >>>> Yes, I think we can do that (I was assuming that was the plan anyway). >>>> >>>> >>>>> Including jBPM 4 beta as part of your GA might not be a good idea. jBPM >>>>> database schema will change. And that could cause serious upgrade problems >>>>> for SEAM users using jBPM. Also upgrade from jBPM 3 to jBPM 4 will be >>>>> impossible for now. >>>>> >>>> Can you tell us what the earliest release we should put in 2.2.0 is? And >>>> roughly what date we can target? If we don't have time to do 2.2.0 and >>>> 2.2.1, I guess we could do: >>>> >>>> Seam 2.2.0.BETA1 - Wednesday 22nd April >>>> Seam 2.2.0.CR1 - Wednesday 13th May >>>> Seam 2.2.0 - Wednesday 17th June >>>> >>>> Tom and Anne-Louise, how do these dates fit your respective schedules? >>>> >>>> >>>>> regards, tom. >>>>> >>>>> >>>>> >>>>> Pete Muir wrote: >>>>> >>>>>> All, >>>>>> This Drools upgrade, and a probable upgrade to jBPM 4 (happening due to >>>>>> these products needed in the JBoss SOA platform 5, based on EAP 5, which in >>>>>> turn includes Seam) mean that we need to make the release Seam 2.2 (which I >>>>>> said would never happen, I know ;-) >>>>>> Due to the concentration on Web Beans / Seam 3 there hasn't been a huge >>>>>> amount of activity recently, however 2.2 will include: >>>>>> * 112 issues closed (please direct your thanks to Norman here - he has >>>>>> been soldiering away!) >>>>>> * improvements to Seam-gen (Glassfish, IDEA etc.) from Dan >>>>>> * big improvements to REST support - Christian and Jozef >>>>>> * Drools and jBPM upgrades >>>>>> So, I suggest that Norman and Marek (can you coordinate with each >>>>>> other) handle the jBPM upgrade (Tom just released alpha2, and plans the GA >>>>>> in the mid summer) - we should wait until there is a beta out I think for >>>>>> Seam 2.2 GA... Tom, any rough guess when this will be? >>>>>> Assuming Tom has a beta, I propose this schedule: >>>>>> Seam 2.2.0 CR1 - Wednesday 22nd April >>>>>> Seam 2.2.0 - Wednesday 13th May >>>>>> Seam 2.2.1 CR1 - Wednesday 17th June >>>>>> Seam 2.2.1 - Wednesday 8th July (hopefully just after the jBPM GA) >>>>>> This will be the first time for time-boxing our releases too, something >>>>>> we are doing for Web Beans, and will do for Seam3. >>>>>> Anne-Louise, could you please comment on how these dates fit with EAP5 >>>>>> component freezes? Will we be able to get 2.2.1 in? >>>>>> Thanks! >>>>>> Begin forwarded message: >>>>>> >>>>>>> From: "Stefano Travelli (JIRA)" <jira-events(a)lists.jboss.org&gt; >>>>>>> Date: 18 March 2009 00:23:22 GMT >>>>>>> To: pete.muir(a)jboss.org >>>>>>> Subject: [JBoss JIRA] Commented: (JBSEAM-4011) Upgrade Drools >>>>>>> framework integration to version 5 >>>>>>> >>>>>>> >>>>>>> [ >>>>>>> https://jira.jboss.org/jira/browse/JBSEAM-4011?page=com.atlassian.jira.pl... ] >>>>>>> >>>>>>> Stefano Travelli commented on JBSEAM-4011: >>>>>>> ------------------------------------------ >>>>>>> >>>>>>> As far as I know, drools 5 is not a drop in replacement of drools >>>>>>> 4.0.7. Lots of dependencies change (mvel and antlr for instance) and most of >>>>>>> all there are several API changes that make Seam after changeset #10170 not >>>>>>> compatible with Drools 4 forcing a migration to Drools 5 in the run time >>>>>>> environment of existing applications. >>>>>>> >>>>>>> At least, a detailed migration path for existing application is >>>>>>> needed. However, even after accomplished all dependencies, rules in my >>>>>>> application don't compile anymore. >>>>>>> >>>>>>> Actually, in my opinion this upgrade is unfitted for a maintenance >>>>>>> release of Seam. >>>>>>> >>>>>>> Upgrade Drools framework integration to version 5 >>>>>>>> ------------------------------------------------- >>>>>>>> >>>>>>>> Key: JBSEAM-4011 >>>>>>>> URL: https://jira.jboss.org/jira/browse/JBSEAM-4011 >>>>>>>> Project: Seam >>>>>>>> Issue Type: Feature Request >>>>>>>> Components: Drools >>>>>>>> Reporter: Marek Novotny >>>>>>>> Assignee: Marek Novotny >>>>>>>> Fix For: 2.1.2.CR1 >>>>>>>> >>>>>>>> >>>>>>>> Upgrade Drools framework integration to current development version >>>>>>>> of Drools 5. It is now available 5.0.0.CR1 version. >>>>>>>> >>>>>>> -- >>>>>>> This message is automatically generated by JIRA. >>>>>>> - >>>>>>> If you think it was sent incorrectly contact one of the >>>>>>> administrators: >>>>>>> https://jira.jboss.org/jira/secure/Administrators.jspa >>>>>>> - >>>>>>> For more information on JIRA, see: >>>>>>> http://www.atlassian.com/software/jira >>>>>>> >>>>>>> >>>>>>> -- >>>>>> Pete Muir >>>>>> http://www.seamframework.org >>>>>> http://in.relation.to/Bloggers/Pete >>>>>> >>>>> -- >>>>> regards, tom. >>>>> >>>>> _______________________________________________ >>>>> seam-dev mailing list >>>>> seam-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>> >>>> -- >>>> Pete Muir >>>> http://www.seamframework.org >>>> http://in.relation.to/Bloggers/Pete >>>> >>>> _______________________________________________ >>>> seam-dev mailing list >>>> seam-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>> >>> -- >>> Pete Muir >>> http://www.seamframework.org >>> http://in.relation.to/Bloggers/Pete >>> >>> _______________________________________________ >>> 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 >> > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev - -- Marek Novotny - -- JBoss Seam Product Lead Red Hat Czech s.r.o. Purkynova 99 612 45 Brno Email: mnovotny(a)redhat.com Office phone: +420 532 294 287, ext. 82-62 087 mobile: +420 608 509 230 - ------------------------------------------------------ Looking to carve out IT costs? www.europe.redhat.com/promo/carveoutcosts/

On Apr 2, 2009, at 20:20, Dan Allen wrote: On Thu, Apr 2, 2009 at 3:56 AM, Pete Muir <pmuir(a)redhat.com&gt; wrote: > I blogged about release plans: > > http://in.relation.to/Bloggers/TheStateOfSeam And I tweeted. http://twitter.com/jbosseam it's http://twitter.com/jbossseam or http://twitter.com/JBossSeam