[jbpm-dev] Re: jbpm-3.2.5.SP

[Thomas Diesler]

 > Check JIRA.

I don't even know what issues you are talking about. Let alone whether 
any SOA issues created and resolved during 3.2.2 and 3.2.3 (9 months) 
made it into the the jBPM test suite.

I suggest you give me a defined list of SOA issues that you want me to 
verify. I can then see whether the jBPM testsuite has coverage for that. 
If it does not have coverage then test cases must be created and checked 
in the 3.2.5.SP branch.

svn diff is IMHO no replacement for a successful hudson run.

Mark Little wrote:
> Check JIRA. But do an svn diff between the last SOA-P jBPM branch we 
> accepted and what you are giving us now.
> 
> Mark.
> 
> 
> On 6 Feb 2009, at 11:20, Thomas Diesler wrote:
> 
>> Ok then lets see the list of SOA issues that we talk about and find 
>> the associated test case in the jBPM testsuite that overs the given 
>> issue.
>>
>> Mark Little wrote:
>>> Let's put it this way: we cannot release the current jbpm branch 
>>> until we have confirmation that other issues have not been lost.
>>> Mark.
>>> On 6 Feb 2009, at 10:44, trevor kirby wrote:
>>>> Mark Little wrote:
>>>>> Do we know if any other issues from the branch we were using are 
>>>>> missing in action?
>>>> We have no confirmation either way, so we will have to check, Thomas 
>>>> does your hudson setupgive you any information about  SOA related 
>>>> jiras that it tests against?
>>>>
>>>> Trev
>>>>>
>>>>> Mark.
>>>>>
>>>>>
>>>>> On 6 Feb 2009, at 10:40, trevor kirby wrote:
>>>>>
>>>>>> Mark Little wrote:
>>>>>>> What's the status?
>>>>>> https://jira.jboss.org/jira/browse/JBPM-2017 - according to the 
>>>>>> jira comment -  Corrected HibernateStringInstance.hbm.xml, made 
>>>>>> the correction work for Sybase/jConnect, wrote test case.
>>>>>> There was also an associated late night checkin, thanks Alejandro.
>>>>>>
>>>>>> https://jira.jboss.org/jira/browse/JBPM-2018 - should also be 
>>>>>> fixed by this.
>>>>>>
>>>>>> https://jira.jboss.org/jira/browse/JBPM-2005 - examples - they are 
>>>>>> still missing, but that is not a blocker. Thomas do we have an ETA?
>>>>>>
>>>>>> https://jira.jboss.org/jira/browse/SOA-1157 - fixed by moving to 
>>>>>> 3.2.5
>>>>>>
>>>>>> We are pulling the build and checking.
>>>>>>
>>>>>> Trev
>>>>>>>
>>>>>>> Mark.
>>>>>>>
>>>>>>>
>>>>>>> On 5 Feb 2009, at 19:27, trevor kirby wrote:
>>>>>>>
>>>>>>>> Alejandro Guizar wrote:
>>>>>>>>> I just joined the channel. I kinda prefer email, but I'll meet 
>>>>>>>>> you guys
>>>>>>>>> there.
>>>>>>>>>
>>>>>>>> We are in the UK, so you joined just after we left :-(
>>>>>>>>
>>>>>>>> Trev
>>>>>>>>> -Alejandro
>>>>>>>>>
>>>>>>>>> El jue, 05-02-2009 a las 13:58 +0000, trevor kirby escribió:
>>>>>>>>>
>>>>>>>>>> Alejandro can you hop onto #jbosssoa  please so we can lose 
>>>>>>>>>> some of the time lag in this discussion.
>>>>>>>>>>
>>>>>>>>>> Trev
>>>>>>>>>>
>>>>>>>>>> Julian Coleman wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> are you actually changing stuff at that level?
>>>>>>>>>>>>
>>>>>>>>>>> We don't make any changes here in the SOA platform build
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> A change at that level is not cosmetic and effectively 
>>>>>>>>>>>> invalidates our QA.
>>>>>>>>>>>>
>>>>>>>>>>> Indeed.  So this change will require a re-test.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Are you saying that this issue needs to be reopened?
>>>>>>>>>>>>
>>>>>>>>>>> Yes.  The previous SOA version had a length of 4000, so this 
>>>>>>>>>>> one needs it as
>>>>>>>>>>> well.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Here is the changeset that removed length="4000"
>>>>>>>>>>>> http://fisheye.jboss.org/changelog/JbpmSvn?cs=2440
>>>>>>>>>>>>
>>>>>>>>>>> Thanks for the pointer.  I've tried reversing the removal of 
>>>>>>>>>>> the length 4000
>>>>>>>>>>> parts of that changeset, but the generated sql still has 
>>>>>>>>>>> (e.g.) varchar(255)
>>>>>>>>>>> and nothing with length 4000, so I must be missing something.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Maybe Alejandro can fill in the details why length="4000" 
>>>>>>>>>>>> was removed.
>>>>>>>>>>>>
>>>>>>>>>>> That might be useful.  Somehow, we need it back though ;-)
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> J
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---
>>>>>>> Mark Little
>>>>>>> mlittle at redhat.com
>>>>>>>
>>>>>>> JBoss, a Division of Red Hat
>>>>>>> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 
>>>>>>> Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
>>>>>>> Registered in UK and Wales under Company Registration No. 3798903 
>>>>>>> Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt 
>>>>>>> Parsons (USA) and Brendan Lane (Ireland).
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> ---
>>>>> Mark Little
>>>>> mlittle at redhat.com
>>>>>
>>>>> JBoss, a Division of Red Hat
>>>>> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod 
>>>>> Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
>>>>> Registered in UK and Wales under Company Registration No. 3798903 
>>>>> Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt 
>>>>> Parsons (USA) and Brendan Lane (Ireland).
>>>>>
>>>>>
>>>>>
>>>>
>>> ---
>>> Mark Little
>>> mlittle at redhat.com
>>> JBoss, a Division of Red Hat
>>> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod 
>>> Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
>>> Registered in UK and Wales under Company Registration No. 3798903 
>>> Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt 
>>> Parsons (USA) and Brendan Lane (Ireland).
> 
> ---
> Mark Little
> mlittle at redhat.com
> 
> JBoss, a Division of Red Hat
> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod 
> Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
> Registered in UK and Wales under Company Registration No. 3798903 
> Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt Parsons 
> (USA) and Brendan Lane (Ireland).
> 
> 
>