Re: Doing another 2.x release in a few weeks?

[Mike Edwards <mi...@gmail.com>]

Luciano Resende wrote:
> On Wed, Jun 30, 2010 at 7:37 AM, ant elder <an...@gmail.com> wrote:
>> Its three weeks since the M5 release now and it would be good to try
>> to do more frequent releases so how about aiming for another release
>> in a few weeks time? Don't need to do anything about it yet, just if
>> you have things you're working on for the next release keep this time
>> frame in mind - so that would be done in two weeks leaving the last
>> week to sort out the release and voting. Does that suite everyone?
>>
>> Â  ...ant
>>
> 
> To my surprise, I still hear from people that are using Tuscany that
> they haven't look too serious in the 2.x yet, because it's a milestone
> release. Any reason not to call this our 2.0 release ?
> 
> 
Folks,

+1 to another release - and I agree with Luciano, time to encourage folk to use 2.x so I'm in favour 
of making this a full release.  We're getting close on OASIS compliance and the functionality is 
looking good.


Yours,  Mike.

Re: Doing another 2.x release in a few weeks?

[ant elder <an...@apache.org>]

On Fri, Jul 23, 2010 at 10:11 AM, kelvin goodson
<ke...@apache.org> wrote:
> Comments so far are below.  Is it worth being on IRC while we check
> these things over so we can avoid duplication of effort?  We can
> always post summaries on the list at intervals.
>

Good idea, i'm there now.

   ...ant

Re: Doing another 2.x release in a few weeks?

[kelvin goodson <ke...@apache.org>]

Comments so far are below.  Is it worth being on IRC while we check
these things over so we can avoid duplication of effort?  We can
always post summaries on the list at intervals.


o With all o.a.t.s artifacts blatted from my local repo and the
staging repo set to be the mirror for all things I can successfully
build and run the samples from an extraction of the source distro.

o README...
This caveat was introduced in M5,
"Please note that milestone releases may support experimental
features and APIs that may not exist in future releases."
.. what do we want to do with it now?

continuing to look it over ..
Kelvin.

On Fri, Jul 23, 2010 at 9:29 AM, kelvin goodson
<ke...@apache.org> wrote:
> OK,  thanks ant, I'll give the tyres a kick
>
> On Fri, Jul 23, 2010 at 9:26 AM, ant elder <an...@apache.org> wrote:
>> Yes i'll update the doc but i'd like to get it working well first, and
>> its still not quite there. One issue is that the distributions are
>> left inside the maven staging repo so when that gets deployed the
>> distributions would end up in the real maven central repo which
>> probably isn't what we want. Another is that currently the one command
>> doesn't build things like the samples and itests (so that the
>> artifacts don't get uploaded) but that means on a fresh checkout/build
>> the distribution doesn't include the prebuilt sample artifacts. If
>> anyone has suggestions for better ways to fix either of those, and
>> also to do more reviews of these staged artifacts to see if there are
>> other issues that need to be fixed.
>>
>>   ...ant
>>
>> On Fri, Jul 23, 2010 at 9:16 AM, kelvin goodson
>> <ke...@apache.org> wrote:
>>> just confirming the first link worked fine with my apache id and p/w
>>> and the 2nd was also fine and did not require a authentication.  Will
>>> you be OK to update the "Making Releases" doc? [1]  It will be very
>>> interesting to see how much of the process get's condensed down to a
>>> single command?
>>>
>>> Kelvin.
>>>
>>> [1] https://cwiki.apache.org/confluence/display/TUSCANYxDOCx2x/Making+Releases
>>>
>>> On Thu, Jul 22, 2010 at 7:32 PM, ant elder <an...@apache.org> wrote:
>>>> On Thu, Jul 22, 2010 at 5:15 PM, Luciano Resende <lu...@gmail.com> wrote:
>>>>> On Thu, Jul 22, 2010 at 7:37 AM, ant elder <an...@apache.org> wrote:
>>>>>> I should work with everyones exsiting apache userids, let me know if
>>>>>> it doesn't. It would also be good to find a way so you don't need to
>>>>>> logon to look at the staged releases,
>>>>>
>>>>> Yes, this would invite the community to take a look at the release
>>>>> before it's really released. In the past the community had helped a
>>>>> lot on reviewing and finding issues on RC.
>>>>>
>>>>>> i've no idea if thats possible
>>>>>> or not with Nexus.
>>>>>>
>>>>>
>>>>> I tried to use just the HTTP url, but that gets redirected to HTTPS
>>>>> and request password. We need to check with Infra.
>>>>>
>>>>
>>>> After fiddling about in Nexus this one works now -
>>>> http://repository.apache.org/content/repositories/orgapachetuscany-027/
>>>>
>>>>   ...ant
>>>>
>>>
>>
>

Re: Doing another 2.x release in a few weeks?

[kelvin goodson <ke...@apache.org>]

OK,  thanks ant, I'll give the tyres a kick

On Fri, Jul 23, 2010 at 9:26 AM, ant elder <an...@apache.org> wrote:
> Yes i'll update the doc but i'd like to get it working well first, and
> its still not quite there. One issue is that the distributions are
> left inside the maven staging repo so when that gets deployed the
> distributions would end up in the real maven central repo which
> probably isn't what we want. Another is that currently the one command
> doesn't build things like the samples and itests (so that the
> artifacts don't get uploaded) but that means on a fresh checkout/build
> the distribution doesn't include the prebuilt sample artifacts. If
> anyone has suggestions for better ways to fix either of those, and
> also to do more reviews of these staged artifacts to see if there are
> other issues that need to be fixed.
>
>   ...ant
>
> On Fri, Jul 23, 2010 at 9:16 AM, kelvin goodson
> <ke...@apache.org> wrote:
>> just confirming the first link worked fine with my apache id and p/w
>> and the 2nd was also fine and did not require a authentication.  Will
>> you be OK to update the "Making Releases" doc? [1]  It will be very
>> interesting to see how much of the process get's condensed down to a
>> single command?
>>
>> Kelvin.
>>
>> [1] https://cwiki.apache.org/confluence/display/TUSCANYxDOCx2x/Making+Releases
>>
>> On Thu, Jul 22, 2010 at 7:32 PM, ant elder <an...@apache.org> wrote:
>>> On Thu, Jul 22, 2010 at 5:15 PM, Luciano Resende <lu...@gmail.com> wrote:
>>>> On Thu, Jul 22, 2010 at 7:37 AM, ant elder <an...@apache.org> wrote:
>>>>> I should work with everyones exsiting apache userids, let me know if
>>>>> it doesn't. It would also be good to find a way so you don't need to
>>>>> logon to look at the staged releases,
>>>>
>>>> Yes, this would invite the community to take a look at the release
>>>> before it's really released. In the past the community had helped a
>>>> lot on reviewing and finding issues on RC.
>>>>
>>>>> i've no idea if thats possible
>>>>> or not with Nexus.
>>>>>
>>>>
>>>> I tried to use just the HTTP url, but that gets redirected to HTTPS
>>>> and request password. We need to check with Infra.
>>>>
>>>
>>> After fiddling about in Nexus this one works now -
>>> http://repository.apache.org/content/repositories/orgapachetuscany-027/
>>>
>>>   ...ant
>>>
>>
>

Re: Doing another 2.x release in a few weeks?

[ant elder <an...@apache.org>]

Yes i'll update the doc but i'd like to get it working well first, and
its still not quite there. One issue is that the distributions are
left inside the maven staging repo so when that gets deployed the
distributions would end up in the real maven central repo which
probably isn't what we want. Another is that currently the one command
doesn't build things like the samples and itests (so that the
artifacts don't get uploaded) but that means on a fresh checkout/build
the distribution doesn't include the prebuilt sample artifacts. If
anyone has suggestions for better ways to fix either of those, and
also to do more reviews of these staged artifacts to see if there are
other issues that need to be fixed.

   ...ant

On Fri, Jul 23, 2010 at 9:16 AM, kelvin goodson
<ke...@apache.org> wrote:
> just confirming the first link worked fine with my apache id and p/w
> and the 2nd was also fine and did not require a authentication.  Will
> you be OK to update the "Making Releases" doc? [1]  It will be very
> interesting to see how much of the process get's condensed down to a
> single command?
>
> Kelvin.
>
> [1] https://cwiki.apache.org/confluence/display/TUSCANYxDOCx2x/Making+Releases
>
> On Thu, Jul 22, 2010 at 7:32 PM, ant elder <an...@apache.org> wrote:
>> On Thu, Jul 22, 2010 at 5:15 PM, Luciano Resende <lu...@gmail.com> wrote:
>>> On Thu, Jul 22, 2010 at 7:37 AM, ant elder <an...@apache.org> wrote:
>>>> I should work with everyones exsiting apache userids, let me know if
>>>> it doesn't. It would also be good to find a way so you don't need to
>>>> logon to look at the staged releases,
>>>
>>> Yes, this would invite the community to take a look at the release
>>> before it's really released. In the past the community had helped a
>>> lot on reviewing and finding issues on RC.
>>>
>>>> i've no idea if thats possible
>>>> or not with Nexus.
>>>>
>>>
>>> I tried to use just the HTTP url, but that gets redirected to HTTPS
>>> and request password. We need to check with Infra.
>>>
>>
>> After fiddling about in Nexus this one works now -
>> http://repository.apache.org/content/repositories/orgapachetuscany-027/
>>
>>   ...ant
>>
>

Re: Doing another 2.x release in a few weeks?

[kelvin goodson <ke...@apache.org>]

just confirming the first link worked fine with my apache id and p/w
and the 2nd was also fine and did not require a authentication.  Will
you be OK to update the "Making Releases" doc? [1]  It will be very
interesting to see how much of the process get's condensed down to a
single command?

Kelvin.

[1] https://cwiki.apache.org/confluence/display/TUSCANYxDOCx2x/Making+Releases

On Thu, Jul 22, 2010 at 7:32 PM, ant elder <an...@apache.org> wrote:
> On Thu, Jul 22, 2010 at 5:15 PM, Luciano Resende <lu...@gmail.com> wrote:
>> On Thu, Jul 22, 2010 at 7:37 AM, ant elder <an...@apache.org> wrote:
>>> I should work with everyones exsiting apache userids, let me know if
>>> it doesn't. It would also be good to find a way so you don't need to
>>> logon to look at the staged releases,
>>
>> Yes, this would invite the community to take a look at the release
>> before it's really released. In the past the community had helped a
>> lot on reviewing and finding issues on RC.
>>
>>> i've no idea if thats possible
>>> or not with Nexus.
>>>
>>
>> I tried to use just the HTTP url, but that gets redirected to HTTPS
>> and request password. We need to check with Infra.
>>
>
> After fiddling about in Nexus this one works now -
> http://repository.apache.org/content/repositories/orgapachetuscany-027/
>
>   ...ant
>

Re: Doing another 2.x release in a few weeks?

[ant elder <an...@apache.org>]

On Thu, Jul 22, 2010 at 5:15 PM, Luciano Resende <lu...@gmail.com> wrote:
> On Thu, Jul 22, 2010 at 7:37 AM, ant elder <an...@apache.org> wrote:
>> I should work with everyones exsiting apache userids, let me know if
>> it doesn't. It would also be good to find a way so you don't need to
>> logon to look at the staged releases,
>
> Yes, this would invite the community to take a look at the release
> before it's really released. In the past the community had helped a
> lot on reviewing and finding issues on RC.
>
>> i've no idea if thats possible
>> or not with Nexus.
>>
>
> I tried to use just the HTTP url, but that gets redirected to HTTPS
> and request password. We need to check with Infra.
>

After fiddling about in Nexus this one works now -
http://repository.apache.org/content/repositories/orgapachetuscany-027/

   ...ant

Re: Doing another 2.x release in a few weeks?

[Luciano Resende <lu...@gmail.com>]

On Thu, Jul 22, 2010 at 7:37 AM, ant elder <an...@apache.org> wrote:
> I should work with everyones exsiting apache userids, let me know if
> it doesn't. It would also be good to find a way so you don't need to
> logon to look at the staged releases,

Yes, this would invite the community to take a look at the release
before it's really released. In the past the community had helped a
lot on reviewing and finding issues on RC.

> i've no idea if thats possible
> or not with Nexus.
>

I tried to use just the HTTP url, but that gets redirected to HTTPS
and request password. We need to check with Infra.

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Doing another 2.x release in a few weeks?

[ant elder <an...@apache.org>]

I should work with everyones exsiting apache userids, let me know if
it doesn't. It would also be good to find a way so you don't need to
logon to look at the staged releases, i've no idea if thats possible
or not with Nexus.

   ...ant

On Thu, Jul 22, 2010 at 3:24 PM, kelvin goodson
<ke...@apache.org> wrote:
> This sounds like a real advance.  I followed the link but was asked
> for a nexus login id and password.  What's the story there?  Do we all
> need to apply for one of these?
>
> Kelvin.
>
> On Thu, Jul 22, 2010 at 2:32 PM, ant elder <an...@apache.org> wrote:
>> On Mon, Jul 19, 2010 at 11:57 AM, ant elder <an...@apache.org> wrote:
>>> On Fri, Jul 16, 2010 at 10:49 AM, Simon Laws <si...@googlemail.com> wrote:
>>>> On Thu, Jul 1, 2010 at 3:24 PM, ant elder <an...@gmail.com> wrote:
>>>>> On Thu, Jul 1, 2010 at 2:08 PM, Mike Edwards
>>>>> <mi...@gmail.com> wrote:
>>>>>> Luciano Resende wrote:
>>>>>>>
>>>>>>> On Wed, Jun 30, 2010 at 7:37 AM, ant elder <an...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Its three weeks since the M5 release now and it would be good to try
>>>>>>>> to do more frequent releases so how about aiming for another release
>>>>>>>> in a few weeks time? Don't need to do anything about it yet, just if
>>>>>>>> you have things you're working on for the next release keep this time
>>>>>>>> frame in mind - so that would be done in two weeks leaving the last
>>>>>>>> week to sort out the release and voting. Does that suite everyone?
>>>>>>>>
>>>>>>>> Â  ...ant
>>>>>>>>
>>>>>>>
>>>>>>> To my surprise, I still hear from people that are using Tuscany that
>>>>>>> they haven't look too serious in the 2.x yet, because it's a milestone
>>>>>>> release. Any reason not to call this our 2.0 release ?
>>>>>>>
>>>>>>>
>>>>>> Folks,
>>>>>>
>>>>>> +1 to another release - and I agree with Luciano, time to encourage folk to
>>>>>> use 2.x so I'm in favour of making this a full release.  We're getting close
>>>>>> on OASIS compliance and the functionality is looking good.
>>>>>>
>>>>>
>>>>> I agree calling these "milestone" releases puts people of using it.
>>>>> How about though we call this next release something else (beta?) and
>>>>> do the one after that as 2.0? That would give a little more time to
>>>>> polish things so when people do try it they get a good experience.
>>>>> There is still quite a lot that could do with tidying - the samples,
>>>>> website, etc, - and I'm not sure we'd get much of that done in just
>>>>> the next three weeks along with all the other work that is currently
>>>>> being done.
>>>>>
>>>>>   ...ant
>>>>>
>>>>
>>>> +1 for next release being a beta. Once we catch up with recent changes
>>>> in the JCA otests and complete the last few tests elsewhere we'll be
>>>> looking good, given the current state of the OASIS tests, in
>>>> demonstrating the full set of "core" function which I believe includes
>>>> Assembly, JCA, JCI, Policy, WS. I put "core" as this is the minimum
>>>> set of function required to actually run the otests.
>>>>
>>>> The otests may still change of course but it seems right to be going
>>>> for a beta so that we can then work on polishing the runtime, docs
>>>> etc. while people take a look at the beta and report back.
>>>>
>>>
>>> That sounds ok to me.
>>>
>>> Going by the timing suggested earlier in this thread we should be
>>> doing the release about now, so I'd like to do that as soon as we've
>>> sorted out all the current build and otest failures, which should mean
>>> an RC sometime this week if that fits in with everyone. I've created a
>>> Java-SCA-2.0-Beta1 JIRA category for the release so use that for jiras
>>> for things wanted in the release.
>>>
>>>   ...ant
>>>
>>
>> Ok i've taken a branch and tag and run a release using the nexus and
>> the new release process. So far so simple and with one mvn command it
>> did everything including all the signing and uploads (though it did
>> take a few hours). Still working out how all this new stuff works but
>> whats there is available at
>> https://repository.apache.org/index.html#stagingRepositories. All the
>> distributions and everything are all in the staging repo, would be
>> easier to find a way to separate them out but i'm not sure how to do
>> that yet. I'm reviewing it now, if anyone else wants to please do post
>> any comments.
>>
>>   ...ant
>>
>

Re: Doing another 2.x release in a few weeks?

[kelvin goodson <ke...@apache.org>]

This sounds like a real advance.  I followed the link but was asked
for a nexus login id and password.  What's the story there?  Do we all
need to apply for one of these?

Kelvin.

On Thu, Jul 22, 2010 at 2:32 PM, ant elder <an...@apache.org> wrote:
> On Mon, Jul 19, 2010 at 11:57 AM, ant elder <an...@apache.org> wrote:
>> On Fri, Jul 16, 2010 at 10:49 AM, Simon Laws <si...@googlemail.com> wrote:
>>> On Thu, Jul 1, 2010 at 3:24 PM, ant elder <an...@gmail.com> wrote:
>>>> On Thu, Jul 1, 2010 at 2:08 PM, Mike Edwards
>>>> <mi...@gmail.com> wrote:
>>>>> Luciano Resende wrote:
>>>>>>
>>>>>> On Wed, Jun 30, 2010 at 7:37 AM, ant elder <an...@gmail.com> wrote:
>>>>>>>
>>>>>>> Its three weeks since the M5 release now and it would be good to try
>>>>>>> to do more frequent releases so how about aiming for another release
>>>>>>> in a few weeks time? Don't need to do anything about it yet, just if
>>>>>>> you have things you're working on for the next release keep this time
>>>>>>> frame in mind - so that would be done in two weeks leaving the last
>>>>>>> week to sort out the release and voting. Does that suite everyone?
>>>>>>>
>>>>>>> Â  ...ant
>>>>>>>
>>>>>>
>>>>>> To my surprise, I still hear from people that are using Tuscany that
>>>>>> they haven't look too serious in the 2.x yet, because it's a milestone
>>>>>> release. Any reason not to call this our 2.0 release ?
>>>>>>
>>>>>>
>>>>> Folks,
>>>>>
>>>>> +1 to another release - and I agree with Luciano, time to encourage folk to
>>>>> use 2.x so I'm in favour of making this a full release.  We're getting close
>>>>> on OASIS compliance and the functionality is looking good.
>>>>>
>>>>
>>>> I agree calling these "milestone" releases puts people of using it.
>>>> How about though we call this next release something else (beta?) and
>>>> do the one after that as 2.0? That would give a little more time to
>>>> polish things so when people do try it they get a good experience.
>>>> There is still quite a lot that could do with tidying - the samples,
>>>> website, etc, - and I'm not sure we'd get much of that done in just
>>>> the next three weeks along with all the other work that is currently
>>>> being done.
>>>>
>>>>   ...ant
>>>>
>>>
>>> +1 for next release being a beta. Once we catch up with recent changes
>>> in the JCA otests and complete the last few tests elsewhere we'll be
>>> looking good, given the current state of the OASIS tests, in
>>> demonstrating the full set of "core" function which I believe includes
>>> Assembly, JCA, JCI, Policy, WS. I put "core" as this is the minimum
>>> set of function required to actually run the otests.
>>>
>>> The otests may still change of course but it seems right to be going
>>> for a beta so that we can then work on polishing the runtime, docs
>>> etc. while people take a look at the beta and report back.
>>>
>>
>> That sounds ok to me.
>>
>> Going by the timing suggested earlier in this thread we should be
>> doing the release about now, so I'd like to do that as soon as we've
>> sorted out all the current build and otest failures, which should mean
>> an RC sometime this week if that fits in with everyone. I've created a
>> Java-SCA-2.0-Beta1 JIRA category for the release so use that for jiras
>> for things wanted in the release.
>>
>>   ...ant
>>
>
> Ok i've taken a branch and tag and run a release using the nexus and
> the new release process. So far so simple and with one mvn command it
> did everything including all the signing and uploads (though it did
> take a few hours). Still working out how all this new stuff works but
> whats there is available at
> https://repository.apache.org/index.html#stagingRepositories. All the
> distributions and everything are all in the staging repo, would be
> easier to find a way to separate them out but i'm not sure how to do
> that yet. I'm reviewing it now, if anyone else wants to please do post
> any comments.
>
>   ...ant
>

Re: Doing another 2.x release in a few weeks?

[ant elder <an...@apache.org>]

On Mon, Jul 19, 2010 at 11:57 AM, ant elder <an...@apache.org> wrote:
> On Fri, Jul 16, 2010 at 10:49 AM, Simon Laws <si...@googlemail.com> wrote:
>> On Thu, Jul 1, 2010 at 3:24 PM, ant elder <an...@gmail.com> wrote:
>>> On Thu, Jul 1, 2010 at 2:08 PM, Mike Edwards
>>> <mi...@gmail.com> wrote:
>>>> Luciano Resende wrote:
>>>>>
>>>>> On Wed, Jun 30, 2010 at 7:37 AM, ant elder <an...@gmail.com> wrote:
>>>>>>
>>>>>> Its three weeks since the M5 release now and it would be good to try
>>>>>> to do more frequent releases so how about aiming for another release
>>>>>> in a few weeks time? Don't need to do anything about it yet, just if
>>>>>> you have things you're working on for the next release keep this time
>>>>>> frame in mind - so that would be done in two weeks leaving the last
>>>>>> week to sort out the release and voting. Does that suite everyone?
>>>>>>
>>>>>> Â  ...ant
>>>>>>
>>>>>
>>>>> To my surprise, I still hear from people that are using Tuscany that
>>>>> they haven't look too serious in the 2.x yet, because it's a milestone
>>>>> release. Any reason not to call this our 2.0 release ?
>>>>>
>>>>>
>>>> Folks,
>>>>
>>>> +1 to another release - and I agree with Luciano, time to encourage folk to
>>>> use 2.x so I'm in favour of making this a full release.  We're getting close
>>>> on OASIS compliance and the functionality is looking good.
>>>>
>>>
>>> I agree calling these "milestone" releases puts people of using it.
>>> How about though we call this next release something else (beta?) and
>>> do the one after that as 2.0? That would give a little more time to
>>> polish things so when people do try it they get a good experience.
>>> There is still quite a lot that could do with tidying - the samples,
>>> website, etc, - and I'm not sure we'd get much of that done in just
>>> the next three weeks along with all the other work that is currently
>>> being done.
>>>
>>>   ...ant
>>>
>>
>> +1 for next release being a beta. Once we catch up with recent changes
>> in the JCA otests and complete the last few tests elsewhere we'll be
>> looking good, given the current state of the OASIS tests, in
>> demonstrating the full set of "core" function which I believe includes
>> Assembly, JCA, JCI, Policy, WS. I put "core" as this is the minimum
>> set of function required to actually run the otests.
>>
>> The otests may still change of course but it seems right to be going
>> for a beta so that we can then work on polishing the runtime, docs
>> etc. while people take a look at the beta and report back.
>>
>
> That sounds ok to me.
>
> Going by the timing suggested earlier in this thread we should be
> doing the release about now, so I'd like to do that as soon as we've
> sorted out all the current build and otest failures, which should mean
> an RC sometime this week if that fits in with everyone. I've created a
> Java-SCA-2.0-Beta1 JIRA category for the release so use that for jiras
> for things wanted in the release.
>
>   ...ant
>

Ok i've taken a branch and tag and run a release using the nexus and
the new release process. So far so simple and with one mvn command it
did everything including all the signing and uploads (though it did
take a few hours). Still working out how all this new stuff works but
whats there is available at
https://repository.apache.org/index.html#stagingRepositories. All the
distributions and everything are all in the staging repo, would be
easier to find a way to separate them out but i'm not sure how to do
that yet. I'm reviewing it now, if anyone else wants to please do post
any comments.

   ...ant

Re: Doing another 2.x release in a few weeks?

[ant elder <an...@apache.org>]

On Fri, Jul 16, 2010 at 10:49 AM, Simon Laws <si...@googlemail.com> wrote:
> On Thu, Jul 1, 2010 at 3:24 PM, ant elder <an...@gmail.com> wrote:
>> On Thu, Jul 1, 2010 at 2:08 PM, Mike Edwards
>> <mi...@gmail.com> wrote:
>>> Luciano Resende wrote:
>>>>
>>>> On Wed, Jun 30, 2010 at 7:37 AM, ant elder <an...@gmail.com> wrote:
>>>>>
>>>>> Its three weeks since the M5 release now and it would be good to try
>>>>> to do more frequent releases so how about aiming for another release
>>>>> in a few weeks time? Don't need to do anything about it yet, just if
>>>>> you have things you're working on for the next release keep this time
>>>>> frame in mind - so that would be done in two weeks leaving the last
>>>>> week to sort out the release and voting. Does that suite everyone?
>>>>>
>>>>> Â  ...ant
>>>>>
>>>>
>>>> To my surprise, I still hear from people that are using Tuscany that
>>>> they haven't look too serious in the 2.x yet, because it's a milestone
>>>> release. Any reason not to call this our 2.0 release ?
>>>>
>>>>
>>> Folks,
>>>
>>> +1 to another release - and I agree with Luciano, time to encourage folk to
>>> use 2.x so I'm in favour of making this a full release.  We're getting close
>>> on OASIS compliance and the functionality is looking good.
>>>
>>
>> I agree calling these "milestone" releases puts people of using it.
>> How about though we call this next release something else (beta?) and
>> do the one after that as 2.0? That would give a little more time to
>> polish things so when people do try it they get a good experience.
>> There is still quite a lot that could do with tidying - the samples,
>> website, etc, - and I'm not sure we'd get much of that done in just
>> the next three weeks along with all the other work that is currently
>> being done.
>>
>>   ...ant
>>
>
> +1 for next release being a beta. Once we catch up with recent changes
> in the JCA otests and complete the last few tests elsewhere we'll be
> looking good, given the current state of the OASIS tests, in
> demonstrating the full set of "core" function which I believe includes
> Assembly, JCA, JCI, Policy, WS. I put "core" as this is the minimum
> set of function required to actually run the otests.
>
> The otests may still change of course but it seems right to be going
> for a beta so that we can then work on polishing the runtime, docs
> etc. while people take a look at the beta and report back.
>

That sounds ok to me.

Going by the timing suggested earlier in this thread we should be
doing the release about now, so I'd like to do that as soon as we've
sorted out all the current build and otest failures, which should mean
an RC sometime this week if that fits in with everyone. I've created a
Java-SCA-2.0-Beta1 JIRA category for the release so use that for jiras
for things wanted in the release.

   ...ant

Re: Doing another 2.x release in a few weeks?

[Simon Laws <si...@googlemail.com>]

On Thu, Jul 1, 2010 at 3:24 PM, ant elder <an...@gmail.com> wrote:
> On Thu, Jul 1, 2010 at 2:08 PM, Mike Edwards
> <mi...@gmail.com> wrote:
>> Luciano Resende wrote:
>>>
>>> On Wed, Jun 30, 2010 at 7:37 AM, ant elder <an...@gmail.com> wrote:
>>>>
>>>> Its three weeks since the M5 release now and it would be good to try
>>>> to do more frequent releases so how about aiming for another release
>>>> in a few weeks time? Don't need to do anything about it yet, just if
>>>> you have things you're working on for the next release keep this time
>>>> frame in mind - so that would be done in two weeks leaving the last
>>>> week to sort out the release and voting. Does that suite everyone?
>>>>
>>>> Â  ...ant
>>>>
>>>
>>> To my surprise, I still hear from people that are using Tuscany that
>>> they haven't look too serious in the 2.x yet, because it's a milestone
>>> release. Any reason not to call this our 2.0 release ?
>>>
>>>
>> Folks,
>>
>> +1 to another release - and I agree with Luciano, time to encourage folk to
>> use 2.x so I'm in favour of making this a full release.  We're getting close
>> on OASIS compliance and the functionality is looking good.
>>
>
> I agree calling these "milestone" releases puts people of using it.
> How about though we call this next release something else (beta?) and
> do the one after that as 2.0? That would give a little more time to
> polish things so when people do try it they get a good experience.
> There is still quite a lot that could do with tidying - the samples,
> website, etc, - and I'm not sure we'd get much of that done in just
> the next three weeks along with all the other work that is currently
> being done.
>
>   ...ant
>

+1 for next release being a beta. Once we catch up with recent changes
in the JCA otests and complete the last few tests elsewhere we'll be
looking good, given the current state of the OASIS tests, in
demonstrating the full set of "core" function which I believe includes
Assembly, JCA, JCI, Policy, WS. I put "core" as this is the minimum
set of function required to actually run the otests.

The otests may still change of course but it seems right to be going
for a beta so that we can then work on polishing the runtime, docs
etc. while people take a look at the beta and report back.

Simon

-- 
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com

Re: Doing another 2.x release in a few weeks?

[ant elder <an...@gmail.com>]

On Thu, Jul 1, 2010 at 2:08 PM, Mike Edwards
<mi...@gmail.com> wrote:
> Luciano Resende wrote:
>>
>> On Wed, Jun 30, 2010 at 7:37 AM, ant elder <an...@gmail.com> wrote:
>>>
>>> Its three weeks since the M5 release now and it would be good to try
>>> to do more frequent releases so how about aiming for another release
>>> in a few weeks time? Don't need to do anything about it yet, just if
>>> you have things you're working on for the next release keep this time
>>> frame in mind - so that would be done in two weeks leaving the last
>>> week to sort out the release and voting. Does that suite everyone?
>>>
>>> Â  ...ant
>>>
>>
>> To my surprise, I still hear from people that are using Tuscany that
>> they haven't look too serious in the 2.x yet, because it's a milestone
>> release. Any reason not to call this our 2.0 release ?
>>
>>
> Folks,
>
> +1 to another release - and I agree with Luciano, time to encourage folk to
> use 2.x so I'm in favour of making this a full release.  We're getting close
> on OASIS compliance and the functionality is looking good.
>

I agree calling these "milestone" releases puts people of using it.
How about though we call this next release something else (beta?) and
do the one after that as 2.0? That would give a little more time to
polish things so when people do try it they get a good experience.
There is still quite a lot that could do with tidying - the samples,
website, etc, - and I'm not sure we'd get much of that done in just
the next three weeks along with all the other work that is currently
being done.

   ...ant