Thank you all that participated on the chat, this was very productive time.
Below is the IRC log:
* rfeng ([EMAIL PROTECTED]) has
joined #tuscany
lresende slaws, yt ?
* halehM ([EMAIL PROTECTED]) has joined #Tuscany
slaws hi
lresende slaws, i have a question for you, but i guess we should
start the 1.2 discussion first...
slaws ok
lresende Hi everyone, thanks for joining
lresende First, I'd like to check with you guys how are things going
related to the 1.2 release, and if you guys have outstanding work in
progress now...
lresende this might influence when I cut the release branch
slaws the part I have a question on is the workspace piece that
sebastien has been working on
rfeng hi
lresende slaws, well, i guess he is not here at the moment, but
what's your question ?
* ant_ ([EMAIL PROTECTED]) has
joined #tuscany
slaws do we convert samples to use workspace?
lresende so, i guess I saw some changes to convert
calculator-distributed to use it, right ?
slaws calculator-distributed runs on my PC (but not on continuum for
some reason) but there are others that could usefully be converted to
give a more consistent picture
rfeng how much is the effort to convert?
lresende I'm not sure we need/want to convert all other samples to
it, it probably would make them more complex... no ?
lresende btw, it does not run on my machine, so I guess it's a linux issue
ant_ ...and it seems very last minute to be considering it for this release
* nash ([EMAIL PROTECTED]/ibm/x-da5c9ffb7b6b2b88) has joined #tuscany
lresende yes, I think that, if we have one sample
(calculator-distributed) working with workspace is enough...
considering time
nash hi, sorry to join late.. setup problems
rfeng i can run it on windows
lresende hi nash, we just started, discussing if people have any
outstanding in progress work for 1.2
nash not much from me :-(
lresende rfeng, i can't run calculator-distributed in red hat, and
continuum is using ubuntu
nash a bit of progress with 2033 today, but doubt that it will make 1.2
slaws Ok - am just compiling on linux but taking a while
slaws on the previous point - ok by me - i'll add some words to the
release note pointing out this is experimental and things are in flux
lresende slaws, great
lresende any other in progress items for 1.2 ?
slaws other than that I'm doing JIRA
lresende I have one jira related to multiple contribution and one or
two jira related to ant scripts that I need to work on, but that
probably can be done in paralel with the branch
rfeng I'm working with Venkat on some policy stuff, but not sure how
much we can finish for 1.2
slaws i saw a few sample related JIRA - can we clear those before we
take the branch
slaws let me see...
halehM is it worth to go through the 1.2 Jira list?
lresende yes, we can look at jiras in a sec, let me just ask rfeng
about his last message
lresende rfeng, so, for the policy stuff, can that be done on the
branch, or do you want me to hold the branch for couple more days ?
rfeng it probably has to be incremental.
lresende I guess I/we can continue with some work in trunk, and take
the branch on Monday morning if that helps
rfeng maybe it's too late for 1.2
lresende rfeng, ok then
lresende ok, so if no other issues, we can then look at JIRAs for
1.2 as suggested by halehM ?
nash would it make sense to start wth the ciritical ones?
lresende here is the link :
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=12310210fixfor=12312967
* Venkat ([EMAIL PROTECTED]) has joined #tuscany
nash is this just for JIRAs targeted at 1.2?
lresende nash, so, discuss JIRAs by priority ?
nash we can do it in either order
lresende yes, these are just the 1.2 ? do we want to look at the
whole set of jiras ?
nash at least the critical ones
nash i'm fine to start with the 1.2 list
lresende ok, so let's start with 1.2 and we look at the critical
ones from the java-sca-next right after
lresende TUSCANY-2050
lresende this is still unassigned, but looks like rfeng requested wsdl/xsds
lresende no updates from user yet i guess
lresende TUSCANY-1997 is marked in progress by jsdelfino
nash there is a comment suggesting it may be a problem in ws-commons
nash sorry that was on 2050. slow
rfeng let me check 2050
nash maybe we need to move forward to a new release of ws-commons
rfeng we probably have to move it as part of axis2 1.4
lresende so, probably not for sca 1.2, right ?
nash it's shame that we can't just move ws-commons on its own
nash don't the ws-common folks bother with upward compatibiity?
rfeng it will be messy with the maven transitive dependencies
rfeng for 2050, the reporter doesn't provide his test case
nash ok i understand
nash i will try to recreate 2050
lresende ok
nash the description looks pretty clear
lresende TUSCANY-2081,TUSCANY-2067,TUSCANY-2083 are classloader/osgi
related... looks like Rajini working on it...
lresende TUSCANY-2068 is also osgi related, but looks like ant is
