On 10/19/07, ant elder [EMAIL PROTECTED] wrote:
We've had a Java SCA release every month for a while now so to keep up
that momentum I think it would be good to have an October release as well.
It would probably take too much work to do that from the trunk for October,
so how about a 1.0.1
[
https://issues.apache.org/jira/browse/TUSCANY-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelvin Goodson resolved TUSCANY-1397.
-
Resolution: Fixed
This patch was applied in commit 562586. Please resolve JIRAs when
[
https://issues.apache.org/jira/browse/TUSCANY-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536432
]
Kelvin Goodson commented on TUSCANY-1780:
-
Here's what the generator should be generating I think.
[
https://issues.apache.org/jira/browse/TUSCANY-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536432
]
kgoodson edited comment on TUSCANY-1780 at 10/20/07 6:46 AM:
---
Commented in error
Hi,
Which code base did you use to create the 1.0.1 branch? 1.0 branch or trunk?
If it's from 1.0 branch, we need to control how the post-1.0 commits are
merged over as they may have sequencial dependencies. It might be simpler if
we decide the list of fixes we would like to pull in and then
I answered my own question. :-)
The commit log tells me it was copied from the 1.0 branch. Sorry for being
blind.
Thanks,
Raymond
- Original Message -
From: Raymond Feng [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Saturday, October 20, 2007 9:51 AM
Subject: Re: How about
Since it appears we are going to have a 1.0.1 release, I'd like
to propose fixing TUSCANY-1849 in this release. This would make
1.0.1 non-interoperable with 1.0, but 1.0.1 would be interoperable
with 1.1 and future releases. The alternative is to defer this
fix until 1.1, which would make 1.0.1
