You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by ant elder <an...@gmail.com> on 2011/03/23 08:49:14 UTC
Next 2.x release
I've made some progress on getting the distributed domain and sca
client going again and would like to do another release to get those
out. If i started the release process next week would that fit in ok
with others plans?
...ant
Re: Next 2.x release
Posted by Luciano Resende <lu...@gmail.com>.
On Sun, Mar 27, 2011 at 10:32 AM, Florian Moga <mo...@gmail.com> wrote:
> In my opinion, the getting-started samples would be enough for a release at
> the moment (they're in pretty good shape, few modifications will be needed).
> I'm still lost in our samples discussion so I've started a wiki page [1] to
> keep track of the requirements for a sample in order to make it to trunk.
> Please update it if I missed something so that we have a complete checklist
> for anyone wanting to work on the samples.
> [1] https://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+Samples+Requirements
>
It would be great if the wiki summarizes the pain points we are trying
to solve. This way we can make sure the solutions really address all
the issues. Otherwise is to vague.
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: Next 2.x release
Posted by ant elder <an...@gmail.com>.
On Wed, Mar 30, 2011 at 5:48 PM, Raymond Feng <en...@gmail.com> wrote:
> IIRC, the "unreleased" folder was created for the in-progress code that is
> not ready for the release. We agreed on the following:
> 1) Developers have freedom to add code into unreleased
> 2) Developers have freedom to move code from unreleased into trunk if they
> think it's ready
> 3) When we propose to retire/move code from trunk into unreleased, we need
> to have consensus.
> I'm pretty keen on 3). I recently found it's pretty changeling to find where
> some code lives now :-(.
The decision to have an unreleased folder was a totally separate
discussion/decision to moving the samples out of trunk. The unreleased
discussion and folder creation happened back in October/November last
year. The decision to move the samples out of trunk to be fixed up and
use an RTC approach to moving them back happened just last month.
Neither of those had anything like a formal vote.
Our users have said its not good our releases are full of samples that
don't work, or which demonstrate Tuscany/SCA incorrectly, or that all
work in different inconsistent ways. We had a long discussion on the
ML about what to do and me and Florian and Mike and Simon L and Simon
N all agreed with trying this new approach to the samples. We spent a
long time trying to find points of consensus, you and Luciano did not
participate in that discussion, and it feels like now you think we're
trying to scam you or something.
We're just trying this new approach, it may work, it may not, it might
only be temporary, its certainly not a rigid set in stone approach and
its completely open to modifications or alternatives - do you or
Luciano have any suggestions?
...ant
Re: Next 2.x release
Posted by Raymond Feng <en...@gmail.com>.
IIRC, the "unreleased" folder was created for the in-progress code that is not ready for the release. We agreed on the following:
1) Developers have freedom to add code into unreleased
2) Developers have freedom to move code from unreleased into trunk if they think it's ready
3) When we propose to retire/move code from trunk into unreleased, we need to have consensus.
I'm pretty keen on 3). I recently found it's pretty changeling to find where some code lives now :-(.
Thanks,
Raymond
________________________________________________________________
Raymond Feng
rfeng@apache.org
Apache Tuscany PMC member and committer: tuscany.apache.org
Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
Personal Web Site: www.enjoyjava.com
________________________________________________________________
On Mar 29, 2011, at 11:51 PM, ant elder wrote:
> On Wed, Mar 30, 2011 at 7:24 AM, Luciano Resende <lu...@gmail.com> wrote:
>> On Tue, Mar 29, 2011 at 3:05 PM, ant elder <an...@apache.org> wrote:
>>> Ok i've now added three getting started samples -
>>> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/
>>>
>>> Is that enough now to get three people to +1 a release? Or if not what
>>> else is needed?
>>>
>>> ...ant
>>>
>>
>> I've added the store app back, and did some minimal test from a
>> distribution which seems to work. It would be good to have that as
>> part of the release as well.
>>
>
> I've moved that to the unreleased folder so it can go through the
> review process that we're using for all samples before adding them to
> trunk. If you want it included then please first start a discussion to
> see if is something we want to include and what needs to be done to
> get it into shape.
>
> ...ant
Re: Next 2.x release
Posted by Raymond Feng <en...@gmail.com>.
For such a process change that will impact how/where we commit code, we definitely need to have a VOTE. Long discussions with many issues mixed are very difficult to follow and conclude.
Thanks,
Raymond
________________________________________________________________
Raymond Feng
rfeng@apache.org
Apache Tuscany PMC member and committer: tuscany.apache.org
Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
Personal Web Site: www.enjoyjava.com
________________________________________________________________
On Mar 30, 2011, at 7:45 AM, ant elder wrote:
> On Wed, Mar 30, 2011 at 3:33 PM, Luciano Resende <lu...@gmail.com> wrote:
>> On Tue, Mar 29, 2011 at 11:51 PM, ant elder <an...@apache.org> wrote:
>>> On Wed, Mar 30, 2011 at 7:24 AM, Luciano Resende <lu...@gmail.com> wrote:
>>>> On Tue, Mar 29, 2011 at 3:05 PM, ant elder <an...@apache.org> wrote:
>>>>> Ok i've now added three getting started samples -
>>>>> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/
>>>>>
>>>>> Is that enough now to get three people to +1 a release? Or if not what
>>>>> else is needed?
>>>>>
>>>>> ...ant
>>>>>
>>>>
>>>> I've added the store app back, and did some minimal test from a
>>>> distribution which seems to work. It would be good to have that as
>>>> part of the release as well.
>>>>
>>>
>>> I've moved that to the unreleased folder so it can go through the
>>> review process that we're using for all samples before adding them to
>>> trunk. If you want it included then please first start a discussion to
>>> see if is something we want to include and what needs to be done to
>>> get it into shape.
>>>
>>> ...ant
>>>
>>
>> So, based on the discussion that we need some samples for a release,
>> one goes and proactively start migrating 'one' sample to trunk, and
>> based on CTR process we use, people are welcome to provide feedback on
>> any commit.... And all he gets is to have the samples moved to
>> unreleased ?
>>
>> BTW, should we also move the getting-started samples to unreleased
>> folder for having a review ? Or do we have a selective review process
>> in Tuscany now ?
>>
>
> Luciano, we have been reviewing these helloworld samples that have
> just been moved from unreleased to trunk/samples, thats largely what
> the long sample discussion thread has been about. This is the email
> that initiated this process -
> http://apache.markmail.org/message/4y77sgdwazyzdq7u
>
> I'm going to try to talk to you on IM to see if it helps get to a
> better common understanding of whats going on.
>
> ...ant
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
On Wed, Mar 30, 2011 at 3:33 PM, Luciano Resende <lu...@gmail.com> wrote:
> On Tue, Mar 29, 2011 at 11:51 PM, ant elder <an...@apache.org> wrote:
>> On Wed, Mar 30, 2011 at 7:24 AM, Luciano Resende <lu...@gmail.com> wrote:
>>> On Tue, Mar 29, 2011 at 3:05 PM, ant elder <an...@apache.org> wrote:
>>>> Ok i've now added three getting started samples -
>>>> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/
>>>>
>>>> Is that enough now to get three people to +1 a release? Or if not what
>>>> else is needed?
>>>>
>>>> ...ant
>>>>
>>>
>>> I've added the store app back, and did some minimal test from a
>>> distribution which seems to work. It would be good to have that as
>>> part of the release as well.
>>>
>>
>> I've moved that to the unreleased folder so it can go through the
>> review process that we're using for all samples before adding them to
>> trunk. If you want it included then please first start a discussion to
>> see if is something we want to include and what needs to be done to
>> get it into shape.
>>
>> ...ant
>>
>
> So, based on the discussion that we need some samples for a release,
> one goes and proactively start migrating 'one' sample to trunk, and
> based on CTR process we use, people are welcome to provide feedback on
> any commit.... And all he gets is to have the samples moved to
> unreleased ?
>
> BTW, should we also move the getting-started samples to unreleased
> folder for having a review ? Or do we have a selective review process
> in Tuscany now ?
>
Luciano, we have been reviewing these helloworld samples that have
just been moved from unreleased to trunk/samples, thats largely what
the long sample discussion thread has been about. This is the email
that initiated this process -
http://apache.markmail.org/message/4y77sgdwazyzdq7u
I'm going to try to talk to you on IM to see if it helps get to a
better common understanding of whats going on.
...ant
Re: Next 2.x release
Posted by Luciano Resende <lu...@gmail.com>.
On Tue, Mar 29, 2011 at 11:51 PM, ant elder <an...@apache.org> wrote:
> On Wed, Mar 30, 2011 at 7:24 AM, Luciano Resende <lu...@gmail.com> wrote:
>> On Tue, Mar 29, 2011 at 3:05 PM, ant elder <an...@apache.org> wrote:
>>> Ok i've now added three getting started samples -
>>> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/
>>>
>>> Is that enough now to get three people to +1 a release? Or if not what
>>> else is needed?
>>>
>>> ...ant
>>>
>>
>> I've added the store app back, and did some minimal test from a
>> distribution which seems to work. It would be good to have that as
>> part of the release as well.
>>
>
> I've moved that to the unreleased folder so it can go through the
> review process that we're using for all samples before adding them to
> trunk. If you want it included then please first start a discussion to
> see if is something we want to include and what needs to be done to
> get it into shape.
>
> ...ant
>
So, based on the discussion that we need some samples for a release,
one goes and proactively start migrating 'one' sample to trunk, and
based on CTR process we use, people are welcome to provide feedback on
any commit.... And all he gets is to have the samples moved to
unreleased ?
BTW, should we also move the getting-started samples to unreleased
folder for having a review ? Or do we have a selective review process
in Tuscany now ?
Anyway... have a good day ...
[1] https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
On Wed, Mar 30, 2011 at 7:24 AM, Luciano Resende <lu...@gmail.com> wrote:
> On Tue, Mar 29, 2011 at 3:05 PM, ant elder <an...@apache.org> wrote:
>> Ok i've now added three getting started samples -
>> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/
>>
>> Is that enough now to get three people to +1 a release? Or if not what
>> else is needed?
>>
>> ...ant
>>
>
> I've added the store app back, and did some minimal test from a
> distribution which seems to work. It would be good to have that as
> part of the release as well.
>
I've moved that to the unreleased folder so it can go through the
review process that we're using for all samples before adding them to
trunk. If you want it included then please first start a discussion to
see if is something we want to include and what needs to be done to
get it into shape.
...ant
Re: Next 2.x release
Posted by Luciano Resende <lu...@gmail.com>.
On Tue, Mar 29, 2011 at 3:05 PM, ant elder <an...@apache.org> wrote:
> Ok i've now added three getting started samples -
> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/
>
> Is that enough now to get three people to +1 a release? Or if not what
> else is needed?
>
> ...ant
>
I've added the store app back, and did some minimal test from a
distribution which seems to work. It would be good to have that as
part of the release as well.
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
Ok i've now added three getting started samples -
https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/
Is that enough now to get three people to +1 a release? Or if not what
else is needed?
...ant
On Tue, Mar 29, 2011 at 8:48 AM, ant elder <an...@apache.org> wrote:
> On Sun, Mar 27, 2011 at 6:32 PM, Florian Moga <mo...@gmail.com> wrote:
>> In my opinion, the getting-started samples would be enough for a release at
>> the moment (they're in pretty good shape, few modifications will be needed).
>
> Ok, and i think a couple of others have expressed that sentiment on
> the discussion thread + me so i think that gives us consensus so i'll
> start doing that, feel free everyone to help polish them up.
>
> ...ant
>
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
I've added a little now to the wiki page, and we can keep updating it
as we think of more things.
...ant
On Tue, Mar 29, 2011 at 2:33 PM, ant elder <an...@apache.org> wrote:
> Yes i shall have a look and make any updates over the next few days.
>
> ...ant
>
> On Tue, Mar 29, 2011 at 8:58 AM, Florian Moga <mo...@gmail.com> wrote:
>> Hi Ant,
>> Can you please have a look on the samples requirement wiki page and update
>> it if you feel so? It will enable other people to help with the samples (me
>> included if I find some time). You've been working on shaping the helloworld
>> sample, there might be some things I didn't notice.
>> Thanks,
>> Florian
>>
>> On Tue, Mar 29, 2011 at 10:48 AM, ant elder <an...@apache.org> wrote:
>>>
>>> On Sun, Mar 27, 2011 at 6:32 PM, Florian Moga <mo...@gmail.com> wrote:
>>> > In my opinion, the getting-started samples would be enough for a release
>>> > at
>>> > the moment (they're in pretty good shape, few modifications will be
>>> > needed).
>>>
>>> Ok, and i think a couple of others have expressed that sentiment on
>>> the discussion thread + me so i think that gives us consensus so i'll
>>> start doing that, feel free everyone to help polish them up.
>>>
>>> ...ant
>>
>>
>
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
Yes i shall have a look and make any updates over the next few days.
...ant
On Tue, Mar 29, 2011 at 8:58 AM, Florian Moga <mo...@gmail.com> wrote:
> Hi Ant,
> Can you please have a look on the samples requirement wiki page and update
> it if you feel so? It will enable other people to help with the samples (me
> included if I find some time). You've been working on shaping the helloworld
> sample, there might be some things I didn't notice.
> Thanks,
> Florian
>
> On Tue, Mar 29, 2011 at 10:48 AM, ant elder <an...@apache.org> wrote:
>>
>> On Sun, Mar 27, 2011 at 6:32 PM, Florian Moga <mo...@gmail.com> wrote:
>> > In my opinion, the getting-started samples would be enough for a release
>> > at
>> > the moment (they're in pretty good shape, few modifications will be
>> > needed).
>>
>> Ok, and i think a couple of others have expressed that sentiment on
>> the discussion thread + me so i think that gives us consensus so i'll
>> start doing that, feel free everyone to help polish them up.
>>
>> ...ant
>
>
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
The issue with that is that users then need Maven to generate the Ant
scripts and the uses who want the Ant scripts probably don't want to
have to be using Maven. To fix that we could include the generated Ant
scripts with the sample but i'm not sure that the way the Maven
generated scripts download the dependencies from the Maven repo was
liked by some in the sample discussion thread. Also the generated
script is three new files which starts to clutter up the maven sample,
i'm not sure how much of an issue this really is, one suggestion in
the sample discussion thread was to have a separate sample showing how
to use Tuscany with Ant. For now i was just leaving what to do with
Ant till later, but if someone else wants to try now sorting it out
that would be fine with me.
...ant
On Tue, Mar 29, 2011 at 9:01 AM, Florian Moga <mo...@gmail.com> wrote:
> Looking at the list, what do you think about adding instructions in the
> README file on how to generate the ant script with maven?
>
>
> On Tue, Mar 29, 2011 at 10:58 AM, Florian Moga <mo...@gmail.com> wrote:
>>
>> Hi Ant,
>> Can you please have a look on the samples requirement wiki page and update
>> it if you feel so? It will enable other people to help with the samples (me
>> included if I find some time). You've been working on shaping the helloworld
>> sample, there might be some things I didn't notice.
>> Thanks,
>> Florian
>>
>> On Tue, Mar 29, 2011 at 10:48 AM, ant elder <an...@apache.org> wrote:
>>>
>>> On Sun, Mar 27, 2011 at 6:32 PM, Florian Moga <mo...@gmail.com> wrote:
>>> > In my opinion, the getting-started samples would be enough for a
>>> > release at
>>> > the moment (they're in pretty good shape, few modifications will be
>>> > needed).
>>>
>>> Ok, and i think a couple of others have expressed that sentiment on
>>> the discussion thread + me so i think that gives us consensus so i'll
>>> start doing that, feel free everyone to help polish them up.
>>>
>>> ...ant
>>
>
>
Re: Next 2.x release
Posted by Florian Moga <mo...@gmail.com>.
Looking at the list, what do you think about adding instructions in the
README file on how to generate the ant script with maven?
On Tue, Mar 29, 2011 at 10:58 AM, Florian Moga <mo...@gmail.com> wrote:
> Hi Ant,
>
> Can you please have a look on the samples requirement wiki page and update
> it if you feel so? It will enable other people to help with the samples (me
> included if I find some time). You've been working on shaping the helloworld
> sample, there might be some things I didn't notice.
>
> Thanks,
>
> Florian
>
>
> On Tue, Mar 29, 2011 at 10:48 AM, ant elder <an...@apache.org> wrote:
>
>> On Sun, Mar 27, 2011 at 6:32 PM, Florian Moga <mo...@gmail.com> wrote:
>> > In my opinion, the getting-started samples would be enough for a release
>> at
>> > the moment (they're in pretty good shape, few modifications will be
>> needed).
>>
>> Ok, and i think a couple of others have expressed that sentiment on
>> the discussion thread + me so i think that gives us consensus so i'll
>> start doing that, feel free everyone to help polish them up.
>>
>> ...ant
>>
>
>
Re: Next 2.x release
Posted by Florian Moga <mo...@gmail.com>.
Hi Ant,
Can you please have a look on the samples requirement wiki page and update
it if you feel so? It will enable other people to help with the samples (me
included if I find some time). You've been working on shaping the helloworld
sample, there might be some things I didn't notice.
Thanks,
Florian
On Tue, Mar 29, 2011 at 10:48 AM, ant elder <an...@apache.org> wrote:
> On Sun, Mar 27, 2011 at 6:32 PM, Florian Moga <mo...@gmail.com> wrote:
> > In my opinion, the getting-started samples would be enough for a release
> at
> > the moment (they're in pretty good shape, few modifications will be
> needed).
>
> Ok, and i think a couple of others have expressed that sentiment on
> the discussion thread + me so i think that gives us consensus so i'll
> start doing that, feel free everyone to help polish them up.
>
> ...ant
>
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
On Sun, Mar 27, 2011 at 6:32 PM, Florian Moga <mo...@gmail.com> wrote:
> In my opinion, the getting-started samples would be enough for a release at
> the moment (they're in pretty good shape, few modifications will be needed).
Ok, and i think a couple of others have expressed that sentiment on
the discussion thread + me so i think that gives us consensus so i'll
start doing that, feel free everyone to help polish them up.
...ant
Re: Next 2.x release
Posted by Florian Moga <mo...@gmail.com>.
In my opinion, the getting-started samples would be enough for a release at
the moment (they're in pretty good shape, few modifications will be needed).
I'm still lost in our samples discussion so I've started a wiki page [1] to
keep track of the requirements for a sample in order to make it to trunk.
Please update it if I missed something so that we have a complete checklist
for anyone wanting to work on the samples.
[1]
https://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+Samples+Requirements
On Sun, Mar 27, 2011 at 10:35 AM, ant elder <an...@gmail.com> wrote:
> On Sat, Mar 26, 2011 at 6:39 PM, ant elder <an...@gmail.com> wrote:
>
> > Would you guys vote +1 on a release like that now?
> >
>
> Or if not will you say what else is needed so that you would +1 a release.
>
> ...ant
>
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
On Sun, Mar 27, 2011 at 5:40 PM, Raymond Feng <en...@gmail.com> wrote:
> If the whole purpose is to have certain level of artifacts versioned in
> maven, can you just create "local" releases instead of official ones? I do
> that all the time using a simple script and publish the jars into a
> "private" maven repo.
No, i think we need more frequent real releases. Its already over a
month since beta2 so i hope we can get another 2.x release out in not
too long.
...ant
Re: Next 2.x release
Posted by ant elder <an...@gmail.com>.
On Sat, Mar 26, 2011 at 6:39 PM, ant elder <an...@gmail.com> wrote:
> Would you guys vote +1 on a release like that now?
>
Or if not will you say what else is needed so that you would +1 a release.
...ant
Re: Next 2.x release
Posted by ant elder <an...@gmail.com>.
The problem with the current samples is that most of them don't work
and there's no consensus yet on exactly what we want, I'm sure you've
all see the eighty odd long email thread about them - subject: "2.0
Beta2 samples (was: [VOTE] Release Tuscany SCA 2.0 Beta2 RC2)".
We could for now just copy back the samples that were in beta2, but
most of them didn't work or are incomplete, and we've had several
comments from devs and users saying its not helpful including samples
with problems. We could include just a few samples but I've trying to
get a basic helloworld sample into a state that there''s some
consensus is ok but no one other than me has ever said they're happy
with any of them.
All i personally want right now is the runtime jars released to the
Maven repository so i can use them without depending on snapshots, so
for that it needs the src distribution and the modules published, i
don't really need a binary distribution or any samples, and I don't
mind if its called 2.0-Beta3 or something else. So i'd quite like to
just release that now and sort out the samples later before 2.0. Would
you guys vote +1 on a release like that now?
...ant
Re: Next 2.x release
Posted by Raymond Feng <en...@gmail.com>.
A release without samples is strange.
Raymond Feng
Sent from my iPhone
On Mar 26, 2011, at 10:00 AM, Luciano Resende <lu...@gmail.com> wrote:
> On Sat, Mar 26, 2011 at 1:39 AM, ant elder <an...@gmail.com> wrote:
>> On Wed, Mar 23, 2011 at 7:49 AM, ant elder <an...@gmail.com> wrote:
>>> I've made some progress on getting the distributed domain and sca
>>> client going again and would like to do another release to get those
>>> out. If i started the release process next week would that fit in ok
>>> with others plans?
>>>
>>> ...ant
>>>
>>
>> Ok no one says they want to hold this till they finish something so
>> I'll plan on doing it. Presently the samples have been moved out of
>> trunk so as it is a build of the binary distribution wont include
>> them. Do you mind about that? If that bothers you enough so that you
>> wouldn't vote +1 to a release please say so now so we can make changes
>> as necessary.
>>
>> ...ant
>>
>
> Does this means no sample at al ? Can't we have at least the store app
> and calculator.
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
Re: Next 2.x release
Posted by Luciano Resende <lu...@gmail.com>.
On Sat, Mar 26, 2011 at 1:39 AM, ant elder <an...@gmail.com> wrote:
> On Wed, Mar 23, 2011 at 7:49 AM, ant elder <an...@gmail.com> wrote:
>> I've made some progress on getting the distributed domain and sca
>> client going again and would like to do another release to get those
>> out. If i started the release process next week would that fit in ok
>> with others plans?
>>
>> ...ant
>>
>
> Ok no one says they want to hold this till they finish something so
> I'll plan on doing it. Presently the samples have been moved out of
> trunk so as it is a build of the binary distribution wont include
> them. Do you mind about that? If that bothers you enough so that you
> wouldn't vote +1 to a release please say so now so we can make changes
> as necessary.
>
> ...ant
>
Does this means no sample at al ? Can't we have at least the store app
and calculator.
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: Next 2.x release
Posted by ant elder <an...@gmail.com>.
On Wed, Mar 23, 2011 at 7:49 AM, ant elder <an...@gmail.com> wrote:
> I've made some progress on getting the distributed domain and sca
> client going again and would like to do another release to get those
> out. If i started the release process next week would that fit in ok
> with others plans?
>
> ...ant
>
Ok no one says they want to hold this till they finish something so
I'll plan on doing it. Presently the samples have been moved out of
trunk so as it is a build of the binary distribution wont include
them. Do you mind about that? If that bothers you enough so that you
wouldn't vote +1 to a release please say so now so we can make changes
as necessary.
...ant
Re: Next 2.x release
Posted by Simon Laws <si...@googlemail.com>.
On Tue, May 17, 2011 at 2:42 PM, ant elder <an...@apache.org> wrote:
>
>
> On Wed, May 4, 2011 at 8:57 AM, ant elder <an...@apache.org> wrote:
>>
>> On Tue, May 3, 2011 at 2:25 PM, Simon Laws <si...@googlemail.com>
>> wrote:
>>
>> >
>> > I'm not going to argue against that I was just repeating what we've
>> > said previously. How about the make this the last beta then get down
>> > to doing the 2.0 release. Our first action should be to list all the
>> > things we think we need to get done in JIRA under the 2.0 category and
>> > then work through them. Our 2.0 category has 18 items in it (2.x
>> > category has 43 items in it) many of while can be closed. So we should
>> > close them down and populate with any others that must be there.
>> >
>>
>> Ok that makes sense. To make this clearer I've moved all the existing
>> open v2 JIRAs to Java-SCA-2.x (there were still a few open ones from
>> previous v2 releases too), lets spend the next week adding what are
>> real issues and tasks that need to happen for 2.0 and put them in
>> Java-SCA-2.0. Then we can see how close we are to doing the 2.0
>> release.
>>
>
> Not many JIRA added to the Java-SCA-2.0 category yet. Is this because we're
> almost done and people are happy to leave things till post 2.0 or do we need
> more time to move and create the JIRAs?
>
> ...ant
>
>
I think it's because we haven't got our fingers out and done it!
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
On Wed, May 4, 2011 at 8:57 AM, ant elder <an...@apache.org> wrote:
> On Tue, May 3, 2011 at 2:25 PM, Simon Laws <si...@googlemail.com>
> wrote:
>
> >
> > I'm not going to argue against that I was just repeating what we've
> > said previously. How about the make this the last beta then get down
> > to doing the 2.0 release. Our first action should be to list all the
> > things we think we need to get done in JIRA under the 2.0 category and
> > then work through them. Our 2.0 category has 18 items in it (2.x
> > category has 43 items in it) many of while can be closed. So we should
> > close them down and populate with any others that must be there.
> >
>
> Ok that makes sense. To make this clearer I've moved all the existing
> open v2 JIRAs to Java-SCA-2.x (there were still a few open ones from
> previous v2 releases too), lets spend the next week adding what are
> real issues and tasks that need to happen for 2.0 and put them in
> Java-SCA-2.0. Then we can see how close we are to doing the 2.0
> release.
>
>
Not many JIRA added to the Java-SCA-2.0 category yet. Is this because we're
almost done and people are happy to leave things till post 2.0 or do we need
more time to move and create the JIRAs?
...ant
RE: Next 2.x release (UNCLASSIFIED)
Posted by "Yang, Gang USA CTR (CH)" <ga...@mail.mil>.
Classification: UNCLASSIFIED
Caveats: NONE
Hi, Simon,
Thanks for looking into this. The significance of JIRA 3852 and 3853 is that it at least allow us get hold of the SOAP message for security processing.
>From the view point of having a general solution, fixing 3852 is preferred since it allows us to integrate with Tuscany instead of the specific WS binding providers (sort of), which can theoretically provide a more generic solution regardless what binding provider is used. I understand my this statement is not entirely true because it depends on how much abstractions Tuscany API provides. I think our earlier discussions touched upon this. But there's a hope. On the contrary, 3853 only provides a way to integrate with Axis2 binding provider specifically.
Thanks again.
Gang
> -----Original Message-----
> From: Simon Laws [mailto:simonslaws@googlemail.com]
> Sent: Monday, May 09, 2011 4:10 AM
> To: dev@tuscany.apache.org
> Subject: Re: Next 2.x release (UNCLASSIFIED)
>
> Hi Gang
>
> I agree that we need to look at this. Haven't go to them yet but I'll
> go through them again and add them to the 2.0 list.
>
> Regards
>
> Simon
>
> On Fri, May 6, 2011 at 7:42 PM, Yang, Gang USA CTR (CH)
> <ga...@mail.mil> wrote:
> > Classification: UNCLASSIFIED
> > Caveats: NONE
> >
> > I created the following JIRAs 3852, 3853, 3854 and 3855 based on
> Simon's summary of several earlier discussions on Policy extension for
> implementing WS security and I verified problems with prototypes (patch
> attached to JIRSs). None of them was included in Java-SCA-2.x. I would
> urge that some of the crucial ones, such as 3852 and/or 3853, be
> considered to be included for the 2.0 release.
> >
> > Our project is currently using 1.6.2, which has PolicyHandler
> support, to implement WS-security. But when we move to 2.0, there would
> be no working mechanism for implementing WS-security.
> >
> > Thanks,
> > Gang
> >
> >> -----Original Message-----
> >> From: Simon Laws [mailto:simonslaws@googlemail.com]
> >> Sent: Wednesday, May 04, 2011 4:08 AM
> >> To: dev@tuscany.apache.org; antelder@apache.org
> >> Subject: Re: Next 2.x release
> >>
> >> On Wed, May 4, 2011 at 8:57 AM, ant elder <an...@apache.org>
> wrote:
> >> > On Tue, May 3, 2011 at 2:25 PM, Simon Laws
> >> <si...@googlemail.com> wrote:
> >> >
> >> >>
> >> >> I'm not going to argue against that I was just repeating what
> we've
> >> >> said previously. How about the make this the last beta then get
> down
> >> >> to doing the 2.0 release. Our first action should be to list all
> the
> >> >> things we think we need to get done in JIRA under the 2.0
> category
> >> and
> >> >> then work through them. Our 2.0 category has 18 items in it (2.x
> >> >> category has 43 items in it) many of while can be closed. So we
> >> should
> >> >> close them down and populate with any others that must be there.
> >> >>
> >> >
> >> > Ok that makes sense. To make this clearer I've moved all the
> existing
> >> > open v2 JIRAs to Java-SCA-2.x (there were still a few open ones
> from
> >> > previous v2 releases too), lets spend the next week adding what
> are
> >> > real issues and tasks that need to happen for 2.0 and put them in
> >> > Java-SCA-2.0. Then we can see how close we are to doing the 2.0
> >> > release.
> >> >
> >> > ...ant
> >> >
> >>
> >> Splendid, thanks Ant. Anyone else have comments/concerns?
> >>
> >> Simon
> >>
> >>
> >> --
> >> Apache Tuscany committer: tuscany.apache.org
> >> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
> >
> > Classification: UNCLASSIFIED
> > Caveats: NONE
> >
> >
> >
>
>
>
> --
> Apache Tuscany committer: tuscany.apache.org
> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Classification: UNCLASSIFIED
Caveats: NONE
Re: Next 2.x release (UNCLASSIFIED)
Posted by Simon Laws <si...@googlemail.com>.
Hi Gang
I agree that we need to look at this. Haven't go to them yet but I'll
go through them again and add them to the 2.0 list.
Regards
Simon
On Fri, May 6, 2011 at 7:42 PM, Yang, Gang USA CTR (CH)
<ga...@mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> I created the following JIRAs 3852, 3853, 3854 and 3855 based on Simon's summary of several earlier discussions on Policy extension for implementing WS security and I verified problems with prototypes (patch attached to JIRSs). None of them was included in Java-SCA-2.x. I would urge that some of the crucial ones, such as 3852 and/or 3853, be considered to be included for the 2.0 release.
>
> Our project is currently using 1.6.2, which has PolicyHandler support, to implement WS-security. But when we move to 2.0, there would be no working mechanism for implementing WS-security.
>
> Thanks,
> Gang
>
>> -----Original Message-----
>> From: Simon Laws [mailto:simonslaws@googlemail.com]
>> Sent: Wednesday, May 04, 2011 4:08 AM
>> To: dev@tuscany.apache.org; antelder@apache.org
>> Subject: Re: Next 2.x release
>>
>> On Wed, May 4, 2011 at 8:57 AM, ant elder <an...@apache.org> wrote:
>> > On Tue, May 3, 2011 at 2:25 PM, Simon Laws
>> <si...@googlemail.com> wrote:
>> >
>> >>
>> >> I'm not going to argue against that I was just repeating what we've
>> >> said previously. How about the make this the last beta then get down
>> >> to doing the 2.0 release. Our first action should be to list all the
>> >> things we think we need to get done in JIRA under the 2.0 category
>> and
>> >> then work through them. Our 2.0 category has 18 items in it (2.x
>> >> category has 43 items in it) many of while can be closed. So we
>> should
>> >> close them down and populate with any others that must be there.
>> >>
>> >
>> > Ok that makes sense. To make this clearer I've moved all the existing
>> > open v2 JIRAs to Java-SCA-2.x (there were still a few open ones from
>> > previous v2 releases too), lets spend the next week adding what are
>> > real issues and tasks that need to happen for 2.0 and put them in
>> > Java-SCA-2.0. Then we can see how close we are to doing the 2.0
>> > release.
>> >
>> > ...ant
>> >
>>
>> Splendid, thanks Ant. Anyone else have comments/concerns?
>>
>> Simon
>>
>>
>> --
>> Apache Tuscany committer: tuscany.apache.org
>> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
RE: Next 2.x release (UNCLASSIFIED)
Posted by "Yang, Gang USA CTR (CH)" <ga...@mail.mil>.
Classification: UNCLASSIFIED
Caveats: NONE
I created the following JIRAs 3852, 3853, 3854 and 3855 based on Simon's summary of several earlier discussions on Policy extension for implementing WS security and I verified problems with prototypes (patch attached to JIRSs). None of them was included in Java-SCA-2.x. I would urge that some of the crucial ones, such as 3852 and/or 3853, be considered to be included for the 2.0 release.
Our project is currently using 1.6.2, which has PolicyHandler support, to implement WS-security. But when we move to 2.0, there would be no working mechanism for implementing WS-security.
Thanks,
Gang
> -----Original Message-----
> From: Simon Laws [mailto:simonslaws@googlemail.com]
> Sent: Wednesday, May 04, 2011 4:08 AM
> To: dev@tuscany.apache.org; antelder@apache.org
> Subject: Re: Next 2.x release
>
> On Wed, May 4, 2011 at 8:57 AM, ant elder <an...@apache.org> wrote:
> > On Tue, May 3, 2011 at 2:25 PM, Simon Laws
> <si...@googlemail.com> wrote:
> >
> >>
> >> I'm not going to argue against that I was just repeating what we've
> >> said previously. How about the make this the last beta then get down
> >> to doing the 2.0 release. Our first action should be to list all the
> >> things we think we need to get done in JIRA under the 2.0 category
> and
> >> then work through them. Our 2.0 category has 18 items in it (2.x
> >> category has 43 items in it) many of while can be closed. So we
> should
> >> close them down and populate with any others that must be there.
> >>
> >
> > Ok that makes sense. To make this clearer I've moved all the existing
> > open v2 JIRAs to Java-SCA-2.x (there were still a few open ones from
> > previous v2 releases too), lets spend the next week adding what are
> > real issues and tasks that need to happen for 2.0 and put them in
> > Java-SCA-2.0. Then we can see how close we are to doing the 2.0
> > release.
> >
> > ...ant
> >
>
> Splendid, thanks Ant. Anyone else have comments/concerns?
>
> Simon
>
>
> --
> Apache Tuscany committer: tuscany.apache.org
> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Classification: UNCLASSIFIED
Caveats: NONE
Re: Next 2.x release
Posted by Simon Laws <si...@googlemail.com>.
On Wed, May 4, 2011 at 8:57 AM, ant elder <an...@apache.org> wrote:
> On Tue, May 3, 2011 at 2:25 PM, Simon Laws <si...@googlemail.com> wrote:
>
>>
>> I'm not going to argue against that I was just repeating what we've
>> said previously. How about the make this the last beta then get down
>> to doing the 2.0 release. Our first action should be to list all the
>> things we think we need to get done in JIRA under the 2.0 category and
>> then work through them. Our 2.0 category has 18 items in it (2.x
>> category has 43 items in it) many of while can be closed. So we should
>> close them down and populate with any others that must be there.
>>
>
> Ok that makes sense. To make this clearer I've moved all the existing
> open v2 JIRAs to Java-SCA-2.x (there were still a few open ones from
> previous v2 releases too), lets spend the next week adding what are
> real issues and tasks that need to happen for 2.0 and put them in
> Java-SCA-2.0. Then we can see how close we are to doing the 2.0
> release.
>
> ...ant
>
Splendid, thanks Ant. Anyone else have comments/concerns?
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
On Tue, May 3, 2011 at 2:25 PM, Simon Laws <si...@googlemail.com> wrote:
>
> I'm not going to argue against that I was just repeating what we've
> said previously. How about the make this the last beta then get down
> to doing the 2.0 release. Our first action should be to list all the
> things we think we need to get done in JIRA under the 2.0 category and
> then work through them. Our 2.0 category has 18 items in it (2.x
> category has 43 items in it) many of while can be closed. So we should
> close them down and populate with any others that must be there.
>
Ok that makes sense. To make this clearer I've moved all the existing
open v2 JIRAs to Java-SCA-2.x (there were still a few open ones from
previous v2 releases too), lets spend the next week adding what are
real issues and tasks that need to happen for 2.0 and put them in
Java-SCA-2.0. Then we can see how close we are to doing the 2.0
release.
...ant
Re: Next 2.x release
Posted by Simon Laws <si...@googlemail.com>.
On Tue, May 3, 2011 at 1:47 PM, ant elder <an...@apache.org> wrote:
> On Tue, May 3, 2011 at 1:04 PM, Simon Laws <si...@googlemail.com> wrote:
>>>> What shall we call this next release? Following on from the last
>>>> release it would be 2.0-Beta3, another option could be 2.0. What else
>>>> do we need to get done before we're ready for a 2.0 release? If its a
>>>> short list of todo's should we just work on getting those done and
>>>> going straight to 2.0 for the next release?
>>>>
>>>
>>> Any comments on the release name?
>>>
>>> I'm back from being on holiday now and it looks like there are enough
>>> others active to get a release vote out so I'd like to have another go
>>> and getting a release out. Unless anyone asks otherwise I'll probably
>>> do a bit of clean up and review this week and cut an RC next week.
>>>
>>> ...ant
>>>
>>
>> I've noticed some discussion on the OASIS list about the optional
>> requirements and associated tests. Maybe Mike would be better placed
>> to comment on any likely implications. I'd say go with 2.0-beta3 until
>> the dust is settled in case we have to change anything.
>>
>
> Ok i guess thats fine for this release just to get it done.
>
> I do think we should revisit the when to do the 2.0 release though. I
> know we've been waiting till OASIS does the 1.1 spec releases but with
> all the politics and time thats taking i think it might be better for
> Tuscany if we do 2.0 sooner and a later 2.x for OASIS.
>
> ...ant
>
I'm not going to argue against that I was just repeating what we've
said previously. How about the make this the last beta then get down
to doing the 2.0 release. Our first action should be to list all the
things we think we need to get done in JIRA under the 2.0 category and
then work through them. Our 2.0 category has 18 items in it (2.x
category has 43 items in it) many of while can be closed. So we should
close them down and populate with any others that must be there.
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: Next 2.x release
Posted by ant elder <an...@apache.org>.
On Tue, May 3, 2011 at 1:04 PM, Simon Laws <si...@googlemail.com> wrote:
>>> What shall we call this next release? Following on from the last
>>> release it would be 2.0-Beta3, another option could be 2.0. What else
>>> do we need to get done before we're ready for a 2.0 release? If its a
>>> short list of todo's should we just work on getting those done and
>>> going straight to 2.0 for the next release?
>>>
>>
>> Any comments on the release name?
>>
>> I'm back from being on holiday now and it looks like there are enough
>> others active to get a release vote out so I'd like to have another go
>> and getting a release out. Unless anyone asks otherwise I'll probably
>> do a bit of clean up and review this week and cut an RC next week.
>>
>> ...ant
>>
>
> I've noticed some discussion on the OASIS list about the optional
> requirements and associated tests. Maybe Mike would be better placed
> to comment on any likely implications. I'd say go with 2.0-beta3 until
> the dust is settled in case we have to change anything.
>
Ok i guess thats fine for this release just to get it done.
I do think we should revisit the when to do the 2.0 release though. I
know we've been waiting till OASIS does the 1.1 spec releases but with
all the politics and time thats taking i think it might be better for
Tuscany if we do 2.0 sooner and a later 2.x for OASIS.
...ant
Re: Next 2.x release
Posted by Simon Laws <si...@googlemail.com>.
>> What shall we call this next release? Following on from the last
>> release it would be 2.0-Beta3, another option could be 2.0. What else
>> do we need to get done before we're ready for a 2.0 release? If its a
>> short list of todo's should we just work on getting those done and
>> going straight to 2.0 for the next release?
>>
>
> Any comments on the release name?
>
> I'm back from being on holiday now and it looks like there are enough
> others active to get a release vote out so I'd like to have another go
> and getting a release out. Unless anyone asks otherwise I'll probably
> do a bit of clean up and review this week and cut an RC next week.
>
> ...ant
>
I've noticed some discussion on the OASIS list about the optional
requirements and associated tests. Maybe Mike would be better placed
to comment on any likely implications. I'd say go with 2.0-beta3 until
the dust is settled in case we have to change anything.
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: Next 2.x release
Posted by ant elder <an...@gmail.com>.
On Mon, Apr 4, 2011 at 3:34 PM, ant elder <an...@gmail.com> wrote:
> On Wed, Mar 23, 2011 at 7:49 AM, ant elder <an...@gmail.com> wrote:
>> I've made some progress on getting the distributed domain and sca
>> client going again and would like to do another release to get those
>> out. If i started the release process next week would that fit in ok
>> with others plans?
>>
>> ...ant
>>
>
> What shall we call this next release? Following on from the last
> release it would be 2.0-Beta3, another option could be 2.0. What else
> do we need to get done before we're ready for a 2.0 release? If its a
> short list of todo's should we just work on getting those done and
> going straight to 2.0 for the next release?
>
Any comments on the release name?
I'm back from being on holiday now and it looks like there are enough
others active to get a release vote out so I'd like to have another go
and getting a release out. Unless anyone asks otherwise I'll probably
do a bit of clean up and review this week and cut an RC next week.
...ant
Re: Next 2.x release
Posted by ant elder <an...@gmail.com>.
On Wed, Mar 23, 2011 at 7:49 AM, ant elder <an...@gmail.com> wrote:
> I've made some progress on getting the distributed domain and sca
> client going again and would like to do another release to get those
> out. If i started the release process next week would that fit in ok
> with others plans?
>
> ...ant
>
What shall we call this next release? Following on from the last
release it would be 2.0-Beta3, another option could be 2.0. What else
do we need to get done before we're ready for a 2.0 release? If its a
short list of todo's should we just work on getting those done and
going straight to 2.0 for the next release?
...ant