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 2010/06/30 16:37:04 UTC
Doing another 2.x release in a few weeks?
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
Re: Doing another 2.x release in a few weeks?
Posted by 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?
Posted by 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?
Posted by 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?
Posted by 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?
Posted by 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?
Posted by 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?
Posted by 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?
Posted by 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?
Posted by 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?
Posted by 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?
Posted by 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?
Posted by 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?
Posted by 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
Re: Doing another 2.x release in a few weeks?
Posted by 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?
Posted by Luciano Resende <lu...@gmail.com>.
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 ?
--
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?
Posted by Florian MOGA <mo...@gmail.com>.
Hi Luciano,
If you decide on doing the 2.0-M6 I'd be happy to help in order to
get accustomed with how a release is being done. By that time people will be
working on the distribution structure where i won't interfere (at most
giving feedback/comments on the mailing list) so I'll be available in the
limit of the time i can find. It would definitely be a useful experience for
me.
Florian
On Fri, Oct 1, 2010 at 8:32 PM, ant elder <an...@gmail.com> wrote:
>
>
> On Fri, Oct 1, 2010 at 6:03 PM, Luciano Resende <lu...@gmail.com>wrote:
>
>> On Fri, Oct 1, 2010 at 1:26 AM, Simon Laws <si...@googlemail.com>
>> wrote:
>> > On Fri, Oct 1, 2010 at 9:19 AM, Florian MOGA <mo...@gmail.com>
>> wrote:
>> >> Simon, are you suggesting to cut down a branch prior to doing the build
>> >> structure modifications and make them on the branch? What's the
>> procedure
>> >> you are following when doing a release?
>> >>
>> >
>> > No, I'm suggesting we get trunk into shape and then cut the branch.
>> >
>>
>> Guys, I'm really in need of a new release, and it seems that we are
>> spending too much time on structuring the source/samples instead. Do
>> you guys think we are going to have a release in the next two weeks ?
>> Otherwise I'll try to cut a M5.1 or M6 (based on m5) in the next
>> couple days with the fixes I need.
>>
>>
> If it was me and i _really_ needed a new release by two weeks I'd go with
> the m5 + fixes. Looking at the current trunk state we could easily spend
> most of next week fixing up trunk and then as there have been a lot of
> changes and the release build has the new nexus process that we've never
> actually used before it could well go through a few RCs before we got a vote
> through, and thats more than two weeks gone. If you did an m6 based on m5
> plus fixes you could easily get that done and voted next week.
>
> ...ant
>
>
>
>
>
>
>
Re: Doing another 2.x release in a few weeks?
Posted by ant elder <an...@gmail.com>.
On Fri, Oct 1, 2010 at 6:03 PM, Luciano Resende <lu...@gmail.com>wrote:
> On Fri, Oct 1, 2010 at 1:26 AM, Simon Laws <si...@googlemail.com>
> wrote:
> > On Fri, Oct 1, 2010 at 9:19 AM, Florian MOGA <mo...@gmail.com> wrote:
> >> Simon, are you suggesting to cut down a branch prior to doing the build
> >> structure modifications and make them on the branch? What's the
> procedure
> >> you are following when doing a release?
> >>
> >
> > No, I'm suggesting we get trunk into shape and then cut the branch.
> >
>
> Guys, I'm really in need of a new release, and it seems that we are
> spending too much time on structuring the source/samples instead. Do
> you guys think we are going to have a release in the next two weeks ?
> Otherwise I'll try to cut a M5.1 or M6 (based on m5) in the next
> couple days with the fixes I need.
>
>
If it was me and i _really_ needed a new release by two weeks I'd go with
the m5 + fixes. Looking at the current trunk state we could easily spend
most of next week fixing up trunk and then as there have been a lot of
changes and the release build has the new nexus process that we've never
actually used before it could well go through a few RCs before we got a vote
through, and thats more than two weeks gone. If you did an m6 based on m5
plus fixes you could easily get that done and voted next week.
...ant
Re: Doing another 2.x release in a few weeks?
Posted by Simon Laws <si...@googlemail.com>.
On Fri, Oct 1, 2010 at 6:03 PM, Luciano Resende <lu...@gmail.com> wrote:
> On Fri, Oct 1, 2010 at 1:26 AM, Simon Laws <si...@googlemail.com> wrote:
>> On Fri, Oct 1, 2010 at 9:19 AM, Florian MOGA <mo...@gmail.com> wrote:
>>> Simon, are you suggesting to cut down a branch prior to doing the build
>>> structure modifications and make them on the branch? What's the procedure
>>> you are following when doing a release?
>>>
>>
>> No, I'm suggesting we get trunk into shape and then cut the branch.
>>
>
> Guys, I'm really in need of a new release, and it seems that we are
> spending too much time on structuring the source/samples instead. Do
> you guys think we are going to have a release in the next two weeks ?
> Otherwise I'll try to cut a M5.1 or M6 (based on m5) in the next
> couple days with the fixes I need.
>
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
Hi Luciano
I'd very much like to get the release out ASAP. I think we've done
enough thinking about restructuring to do the beta release. The beta
will give us the chance to stand back and see if we like it or not.
There is still lots to do in terms of fixing sample build
scripts/READMEs/docs etc. but I hope that won't take too long and we
*can* do this within two weeks.
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?
Posted by Luciano Resende <lu...@gmail.com>.
On Fri, Oct 1, 2010 at 1:26 AM, Simon Laws <si...@googlemail.com> wrote:
> On Fri, Oct 1, 2010 at 9:19 AM, Florian MOGA <mo...@gmail.com> wrote:
>> Simon, are you suggesting to cut down a branch prior to doing the build
>> structure modifications and make them on the branch? What's the procedure
>> you are following when doing a release?
>>
>
> No, I'm suggesting we get trunk into shape and then cut the branch.
>
Guys, I'm really in need of a new release, and it seems that we are
spending too much time on structuring the source/samples instead. Do
you guys think we are going to have a release in the next two weeks ?
Otherwise I'll try to cut a M5.1 or M6 (based on m5) in the next
couple days with the fixes I need.
--
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?
Posted by Simon Laws <si...@googlemail.com>.
On Fri, Oct 1, 2010 at 9:19 AM, Florian MOGA <mo...@gmail.com> wrote:
> Simon, are you suggesting to cut down a branch prior to doing the build
> structure modifications and make them on the branch? What's the procedure
> you are following when doing a release?
>
No, I'm suggesting we get trunk into shape and then cut the branch.
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?
Posted by Florian MOGA <mo...@gmail.com>.
Simon, are you suggesting to cut down a branch prior to doing the build
structure modifications and make them on the branch? What's the procedure
you are following when doing a release?
On Thu, Sep 30, 2010 at 12:27 PM, ant elder <an...@gmail.com> wrote:
> I agree with all those suggestions.
>
> ...ant
>
> On Thu, Sep 30, 2010 at 10:10 AM, Florian MOGA <mo...@gmail.com> wrote:
> > Given the fact that in about one week or so we are about to finish
> technical
> > tasks like the jsonp binding, the shell, etc. I think it is a good time
> to
> > do the release but not before we do the distribution cleanup. If we want
> to
> > improve our release process we'll need a clean, simple and organized
> place
> > to work. I got lost half way at the discussions regarding the distro but
> > from what I've understood we will be able to do the core/base + modules
> jars
> > which is a great idea.
> > Also, I'd like to propose a bit of reorganization in the folder
> structure.
> > Some observations:
> >
> > the archetypes and maven folders are confusing. shouldn't archetypes be a
> > subdirectory in the maven folder?
> > compliance-tests and itest could be subdirectories or a "tests" or
> "testing"
> > folder
> > shades and features can be replaced by a single folder containing the new
> > artifacts
> > what about the contrib folder? i find it very confusing in trunk... we
> also
> > have it in sca-java-2.x, in tuscany and a few other places as well
> >
> > Looking at other open source projects, they've got very few top level
> > folders which enables the user to orientate better in the directory
> > structure (see the samples). As seen above, we can achieve that as well
> > quite easy. Also, this would be a good time to do it if you agree with
> the
> > above as improving the samples and distro structure already involve
> making
> > changes in the poms. We'll also have to go through all the samples and
> > modules to change the dependencies with the new artifacts so we'll be
> going
> > through the directory structure at the same time. If we don't do it now,
> it
> > will be a long time since somebody will be up to going through the whole
> > structure and update things. Also, it is a good reason doing it for the
> 2.0
> > release. It will take a bit of time but I think it's well worthed. Having
> > clean directory, samples and distro structure will enable us doing more
> > regular releases.
> >
> > On Thu, Sep 30, 2010 at 10:40 AM, Simon Laws <si...@googlemail.com>
> > wrote:
> >>
> >> On Thu, Sep 30, 2010 at 8:29 AM, ant elder <an...@gmail.com> wrote:
> >> > On Wed, Sep 29, 2010 at 6:27 PM, Simon Laws <
> simonslaws@googlemail.com>
> >> > wrote:
> >> >> How about we start to making progress on the Beta release again...
> >> >>
> >> >> Things are looking ok I believe from an otest point of view.
> >> >> We've had discussion about the samples and that looks to be shaping
> up.
> >> >> We've also had disscussion about the distro structure and there are
> >> >> lots of ideas. I think we need a release to review and to focus the
> >> >> mind.
> >> >>
> >> >
> >> > Big +1 from me, it would be great to get a release done and then get
> >> > into the habit again of much more regular releases.
> >> >
> >> > ...ant
> >> >
> >>
> >> Yep agreed. Needs to be a straightforward process. I think quite a bit
> >> of the pain has been taken out with some of the automation and testing
> >> that's in 2.x now.
> >>
> >> Re. the beta release. I suggest we cut the branch again rather than
> >> trying to use the existing one. There is though quite a bit of tidying
> >> we can do in trunk, e.g. there was more sample name tidying suggested
> >> and we need to tidy the sample poms and build.xml files and make sure
> >> classes and wars etc are excluded. How about we cut the branch
> >> tomorrow or Monday?
> >>
> >> 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?
Posted by ant elder <an...@gmail.com>.
I agree with all those suggestions.
...ant
On Thu, Sep 30, 2010 at 10:10 AM, Florian MOGA <mo...@gmail.com> wrote:
> Given the fact that in about one week or so we are about to finish technical
> tasks like the jsonp binding, the shell, etc. I think it is a good time to
> do the release but not before we do the distribution cleanup. If we want to
> improve our release process we'll need a clean, simple and organized place
> to work. I got lost half way at the discussions regarding the distro but
> from what I've understood we will be able to do the core/base + modules jars
> which is a great idea.
> Also, I'd like to propose a bit of reorganization in the folder structure.
> Some observations:
>
> the archetypes and maven folders are confusing. shouldn't archetypes be a
> subdirectory in the maven folder?
> compliance-tests and itest could be subdirectories or a "tests" or "testing"
> folder
> shades and features can be replaced by a single folder containing the new
> artifacts
> what about the contrib folder? i find it very confusing in trunk... we also
> have it in sca-java-2.x, in tuscany and a few other places as well
>
> Looking at other open source projects, they've got very few top level
> folders which enables the user to orientate better in the directory
> structure (see the samples). As seen above, we can achieve that as well
> quite easy. Also, this would be a good time to do it if you agree with the
> above as improving the samples and distro structure already involve making
> changes in the poms. We'll also have to go through all the samples and
> modules to change the dependencies with the new artifacts so we'll be going
> through the directory structure at the same time. If we don't do it now, it
> will be a long time since somebody will be up to going through the whole
> structure and update things. Also, it is a good reason doing it for the 2.0
> release. It will take a bit of time but I think it's well worthed. Having
> clean directory, samples and distro structure will enable us doing more
> regular releases.
>
> On Thu, Sep 30, 2010 at 10:40 AM, Simon Laws <si...@googlemail.com>
> wrote:
>>
>> On Thu, Sep 30, 2010 at 8:29 AM, ant elder <an...@gmail.com> wrote:
>> > On Wed, Sep 29, 2010 at 6:27 PM, Simon Laws <si...@googlemail.com>
>> > wrote:
>> >> How about we start to making progress on the Beta release again...
>> >>
>> >> Things are looking ok I believe from an otest point of view.
>> >> We've had discussion about the samples and that looks to be shaping up.
>> >> We've also had disscussion about the distro structure and there are
>> >> lots of ideas. I think we need a release to review and to focus the
>> >> mind.
>> >>
>> >
>> > Big +1 from me, it would be great to get a release done and then get
>> > into the habit again of much more regular releases.
>> >
>> > ...ant
>> >
>>
>> Yep agreed. Needs to be a straightforward process. I think quite a bit
>> of the pain has been taken out with some of the automation and testing
>> that's in 2.x now.
>>
>> Re. the beta release. I suggest we cut the branch again rather than
>> trying to use the existing one. There is though quite a bit of tidying
>> we can do in trunk, e.g. there was more sample name tidying suggested
>> and we need to tidy the sample poms and build.xml files and make sure
>> classes and wars etc are excluded. How about we cut the branch
>> tomorrow or Monday?
>>
>> 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?
Posted by Florian MOGA <mo...@gmail.com>.
Given the fact that in about one week or so we are about to finish technical
tasks like the jsonp binding, the shell, etc. I think it is a good time to
do the release but not before we do the distribution cleanup. If we want to
improve our release process we'll need a clean, simple and organized place
to work. I got lost half way at the discussions regarding the distro but
from what I've understood we will be able to do the core/base + modules jars
which is a great idea.
Also, I'd like to propose a bit of reorganization in the folder structure.
Some observations:
- the archetypes and maven folders are confusing. shouldn't archetypes be
a subdirectory in the maven folder?
- compliance-tests and itest could be subdirectories or a "tests" or
"testing" folder
- shades and features can be replaced by a single folder containing the
new artifacts
- what about the contrib folder? i find it very confusing in trunk... we
also have it in sca-java-2.x, in tuscany and a few other places as well
Looking at other open source projects, they've got very few top level
folders which enables the user to orientate better in the directory
structure (see the samples). As seen above, we can achieve that as well
quite easy. Also, this would be a good time to do it if you agree with the
above as improving the samples and distro structure already involve making
changes in the poms. We'll also have to go through all the samples and
modules to change the dependencies with the new artifacts so we'll be going
through the directory structure at the same time. If we don't do it now, it
will be a long time since somebody will be up to going through the whole
structure and update things. Also, it is a good reason doing it for the 2.0
release. It will take a bit of time but I think it's well worthed. Having
clean directory, samples and distro structure will enable us doing more
regular releases.
On Thu, Sep 30, 2010 at 10:40 AM, Simon Laws <si...@googlemail.com>wrote:
> On Thu, Sep 30, 2010 at 8:29 AM, ant elder <an...@gmail.com> wrote:
> > On Wed, Sep 29, 2010 at 6:27 PM, Simon Laws <si...@googlemail.com>
> wrote:
> >> How about we start to making progress on the Beta release again...
> >>
> >> Things are looking ok I believe from an otest point of view.
> >> We've had discussion about the samples and that looks to be shaping up.
> >> We've also had disscussion about the distro structure and there are
> >> lots of ideas. I think we need a release to review and to focus the
> >> mind.
> >>
> >
> > Big +1 from me, it would be great to get a release done and then get
> > into the habit again of much more regular releases.
> >
> > ...ant
> >
>
> Yep agreed. Needs to be a straightforward process. I think quite a bit
> of the pain has been taken out with some of the automation and testing
> that's in 2.x now.
>
> Re. the beta release. I suggest we cut the branch again rather than
> trying to use the existing one. There is though quite a bit of tidying
> we can do in trunk, e.g. there was more sample name tidying suggested
> and we need to tidy the sample poms and build.xml files and make sure
> classes and wars etc are excluded. How about we cut the branch
> tomorrow or Monday?
>
> 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?
Posted by Simon Laws <si...@googlemail.com>.
On Thu, Sep 30, 2010 at 8:29 AM, ant elder <an...@gmail.com> wrote:
> On Wed, Sep 29, 2010 at 6:27 PM, Simon Laws <si...@googlemail.com> wrote:
>> How about we start to making progress on the Beta release again...
>>
>> Things are looking ok I believe from an otest point of view.
>> We've had discussion about the samples and that looks to be shaping up.
>> We've also had disscussion about the distro structure and there are
>> lots of ideas. I think we need a release to review and to focus the
>> mind.
>>
>
> Big +1 from me, it would be great to get a release done and then get
> into the habit again of much more regular releases.
>
> ...ant
>
Yep agreed. Needs to be a straightforward process. I think quite a bit
of the pain has been taken out with some of the automation and testing
that's in 2.x now.
Re. the beta release. I suggest we cut the branch again rather than
trying to use the existing one. There is though quite a bit of tidying
we can do in trunk, e.g. there was more sample name tidying suggested
and we need to tidy the sample poms and build.xml files and make sure
classes and wars etc are excluded. How about we cut the branch
tomorrow or Monday?
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?
Posted by ant elder <an...@gmail.com>.
On Wed, Sep 29, 2010 at 6:27 PM, Simon Laws <si...@googlemail.com> wrote:
> How about we start to making progress on the Beta release again...
>
> Things are looking ok I believe from an otest point of view.
> We've had discussion about the samples and that looks to be shaping up.
> We've also had disscussion about the distro structure and there are
> lots of ideas. I think we need a release to review and to focus the
> mind.
>
Big +1 from me, it would be great to get a release done and then get
into the habit again of much more regular releases.
...ant
Re: Doing another 2.x release in a few weeks?
Posted by Simon Laws <si...@googlemail.com>.
How about we start to making progress on the Beta release again...
Things are looking ok I believe from an otest point of view.
We've had discussion about the samples and that looks to be shaping up.
We've also had disscussion about the distro structure and there are
lots of ideas. I think we need a release to review and to focus the
mind.
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?
Posted by ant elder <an...@apache.org>.
On Mon, Aug 2, 2010 at 11:11 AM, Simon Laws <si...@googlemail.com> wrote:
>>
>> OK lets wait and see how it goes this week. I think it will be easiest
>> for now to create a new branch when we're ready than to continue
>> merging updates to the current release branch, but if anyone is about
>> to do any big changes such as the schema updates which may take a
>> little while to stabalize can they say first so we can take a new
>> release branch.
>>
>> ...ant
>>
>
> Yes, that sounds reasonable.
>
Ok so as you can see i've not yet had time to do anything about the
release, if anyone else wants to start doing it then please do so. If
no one else does then I should have more time to help get it done in a
week or two.
...ant
Re: Doing another 2.x release in a few weeks?
Posted by Simon Laws <si...@googlemail.com>.
>
> OK lets wait and see how it goes this week. I think it will be easiest
> for now to create a new branch when we're ready than to continue
> merging updates to the current release branch, but if anyone is about
> to do any big changes such as the schema updates which may take a
> little while to stabalize can they say first so we can take a new
> release branch.
>
> ...ant
>
Yes, that sounds reasonable.
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?
Posted by ant elder <an...@apache.org>.
On Mon, Aug 2, 2010 at 9:24 AM, Simon Laws <si...@googlemail.com> wrote:
> On Sat, Jul 31, 2010 at 9:28 AM, ant elder <an...@gmail.com> wrote:
>> What shall we do with this release? I've been holding off cutting an
>> RC while all the otests get fixed, a lot of those are done now but the
>> Java CAA and CI ones still have tests to be fixed. Should do a release
>> now as its starting to take a while or hold off for another week or so
>> to see if we can pass either/both of those test suites? (which would
>> give a release passing all the assembly, policy, ws, java caa, and
>> java ci which would be nice so I'd be happy to hold off for now)
>>
>> ...ant
>>
>
> I'd like us to get the tests passing but we need to check how many
> more new tests there are going to be in these areas. We're tracking
> something of a moving target at the moment which will just keep
> pushing the release out. If that's going to continue to be the case we
> should do the release now. If not I'd vote for delaying another week
> or so to get the tests passing.
>
> Another piece of work we do need to do is update to the latest version
> of the OASIS schema. This will also cause some disruption.
>
> Simon
>
OK lets wait and see how it goes this week. I think it will be easiest
for now to create a new branch when we're ready than to continue
merging updates to the current release branch, but if anyone is about
to do any big changes such as the schema updates which may take a
little while to stabalize can they say first so we can take a new
release branch.
...ant
Re: Doing another 2.x release in a few weeks?
Posted by Simon Laws <si...@googlemail.com>.
On Sat, Jul 31, 2010 at 9:28 AM, ant elder <an...@gmail.com> wrote:
> What shall we do with this release? I've been holding off cutting an
> RC while all the otests get fixed, a lot of those are done now but the
> Java CAA and CI ones still have tests to be fixed. Should do a release
> now as its starting to take a while or hold off for another week or so
> to see if we can pass either/both of those test suites? (which would
> give a release passing all the assembly, policy, ws, java caa, and
> java ci which would be nice so I'd be happy to hold off for now)
>
> ...ant
>
I'd like us to get the tests passing but we need to check how many
more new tests there are going to be in these areas. We're tracking
something of a moving target at the moment which will just keep
pushing the release out. If that's going to continue to be the case we
should do the release now. If not I'd vote for delaying another week
or so to get the tests passing.
Another piece of work we do need to do is update to the latest version
of the OASIS schema. This will also cause some disruption.
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?
Posted by ant elder <an...@gmail.com>.
What shall we do with this release? I've been holding off cutting an
RC while all the otests get fixed, a lot of those are done now but the
Java CAA and CI ones still have tests to be fixed. Should do a release
now as its starting to take a while or hold off for another week or so
to see if we can pass either/both of those test suites? (which would
give a release passing all the assembly, policy, ws, java caa, and
java ci which would be nice so I'd be happy to hold off for now)
...ant
Re: Doing another 2.x release in a few weeks?
Posted by Simon Laws <si...@googlemail.com>.
On Wed, Jun 30, 2010 at 5:45 PM, Raymond Feng <en...@gmail.com> wrote:
> +1.
> Let's see how we can make the release process less painful.
> 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 Jun 30, 2010, at 7:37 AM, ant elder 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
>
>
+1 for doing another release.
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?
Posted by Raymond Feng <en...@gmail.com>.
+1.
Let's see how we can make the release process less painful.
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 Jun 30, 2010, at 7:37 AM, ant elder 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