How can we do a next 2.x release?

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

I've been trying to help a user get going with one of the samples
using the latest code but its ended up needing a bunch of change to
the sample pom.xml's to get it to work with the latest snapshot code.
One of the issues is if you checkout a sample like
https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/helloworld/
and try to build it that doesn't work unless you've built trunk
locally. But thats just one of the reasons, its been ages since we did
a trunk release and there are lots of good changes in there. Last time
we talked about this I couldn't find three people who said they'd vote
for a release, If i just cut an RC of what the trunk builds now i
expect there are a lot of broken samples missing doc and and incorrect
readme's so whats the minimum we could do to fix that which would get
three +1s? If i just did a trunk source release + maven module release
but no binary distro would anyone vote for that? Or if i stripped out
all the samples or maybe except for one or two samples which really
worked and had good READMEs would you vote for that? Or what else
would it take?

  ...ant

Re: How can we do a next 2.x release?

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

On Wed, Jul 13, 2011 at 4:43 PM, Luciano Resende <lu...@gmail.com> wrote:
> On Wed, Jul 13, 2011 at 6:48 AM, Mike Edwards
> <mi...@gmail.com> wrote:
>> Folks,
>>
>> I'd like to see us do a full 2.x release - not another Beta.
>>
>> 2.x has been around for a while and it's in pretty good shape.  A full
>> release is called for in my opinion.  If some samples aren't of the right
>> quality, then leave them out for now - they can be added back later once
>> they are in acceptable shape.
>>
>>
>
> I'm OK with 2.x release as long as : there is source and binary
> distributions, and there are few samples that demonstrates different
> ways of running tuscany. if people are in a rush to get something out,
> I'm also fine with a beta3 in a week timeframe, and 2.x within a month
> timeframe.
>
> Thoughts ?
>

Ok a few of us have now said we'll spend a bit of time on release work
over the next days so lets do that and see how it goes. I'll create a
beta3 RC1 next week and we can see how it looks, and use it as a
stepping stone release to 2.0 shortly after, or if it turns out that
it already looks really fine we can just rename the RC to 2.0 and do
the release vote on that. I'd guess we'll inevitably end up wanting a
bit more polish on a 2.0 release so it will take more work which is
why i'd still like to start with a beta3 now so as to get something
out now.

   ...ant

Re: How can we do a next 2.x release?

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

On Wed, Jul 13, 2011 at 6:48 AM, Mike Edwards
<mi...@gmail.com> wrote:
> Folks,
>
> I'd like to see us do a full 2.x release - not another Beta.
>
> 2.x has been around for a while and it's in pretty good shape.  A full
> release is called for in my opinion.  If some samples aren't of the right
> quality, then leave them out for now - they can be added back later once
> they are in acceptable shape.
>
>

I'm OK with 2.x release as long as : there is source and binary
distributions, and there are few samples that demonstrates different
ways of running tuscany. if people are in a rush to get something out,
I'm also fine with a beta3 in a week timeframe, and 2.x within a month
timeframe.

Thoughts ?

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

Re: How can we do a next 2.x release?

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

Folks,

I'd like to see us do a full 2.x release - not another Beta.

2.x has been around for a while and it's in pretty good shape.  A full release is called for in my 
opinion.  If some samples aren't of the right quality, then leave them out for now - they can be 
added back later once they are in acceptable shape.


Yours,  Mike.

On 13/07/2011 09:15, Simon Laws wrote:
> On Wed, Jul 13, 2011 at 4:17 AM, Luciano Resende<lu...@gmail.com>  wrote:
>> On Tue, Jul 12, 2011 at 3:16 PM, ant elder<an...@apache.org>  wrote:
>>> On Tue, Jul 12, 2011 at 10:30 PM, Luciano Resende<lu...@gmail.com>  wrote:
>>>> On Tue, Jul 12, 2011 at 12:54 PM, ant elder<an...@gmail.com>  wrote:
>>>>> I've been trying to help a user get going with one of the samples
>>>>> using the latest code but its ended up needing a bunch of change to
>>>>> the sample pom.xml's to get it to work with the latest snapshot code.
>>>>> One of the issues is if you checkout a sample like
>>>>> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/helloworld/
>>>>> and try to build it that doesn't work unless you've built trunk
>>>>> locally.
>>>>
>>>> So, wouldn't this be a similar issue if you get a released version of
>>>> the helloworld with a released version of tuscany compared to the most
>>>> recent snapshots ?
>>>>
>>>>> But thats just one of the reasons, its been ages since we did
>>>>> a trunk release and there are lots of good changes in there. Last time
>>>>> we talked about this I couldn't find three people who said they'd vote
>>>>> for a release, If i just cut an RC of what the trunk builds now i
>>>>> expect there are a lot of broken samples missing doc and and incorrect
>>>>> readme's so whats the minimum we could do to fix that which would get
>>>>> three +1s? If i just did a trunk source release + maven module release
>>>>> but no binary distro would anyone vote for that? Or if i stripped out
>>>>> all the samples or maybe except for one or two samples which really
>>>>> worked and had good READMEs would you vote for that? Or what else
>>>>> would it take?
>>>>>
>>>>>   ...ant
>>>>>
>>>>
>>>> What would be the "version name" for the release ? I think we should
>>>> do a regular milestone/beta release and I'd be ok if some samples
>>>> might be broken, but I wouldn't like to see source only distros, as
>>>> that would kind require the users to have to build anyway, unless they
>>>> are using maven which it's not really a requirement we have imposed
>>>> into users before.
>>>>
>>>
>>> Ok thats sounding more promising, i don't mind not doing a source only
>>> release i just want _a_ release with the module jars in maven central,
>>> i don't mind what its called 2.0-Beta3 or M6 or something else. So how
>>> about if its called 2.0-Beta3 and based off the current trunk so the
>>> samples and distro are as they are. I'll try and clean up some
>>> helloworld samples but i wont have the time to make all of the samples
>>> perfect.
>>>
>>>    ...ant
>>>
>>
>> What's the timeframe you are looking for ? I could look at some
>> samples and other minor cleanups over the weekend.
>>
>> --
>> Luciano Resende
>> http://people.apache.org/~lresende
>> http://twitter.com/lresende1975
>> http://lresende.blogspot.com/
>>
>
> I can try and take a look through the samples over the next couple of
> days and do some tidying.
>
> Simon
>

Re: How can we do a next 2.x release?

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

On Wed, Jul 13, 2011 at 4:17 AM, Luciano Resende <lu...@gmail.com> wrote:
> On Tue, Jul 12, 2011 at 3:16 PM, ant elder <an...@apache.org> wrote:
>> On Tue, Jul 12, 2011 at 10:30 PM, Luciano Resende <lu...@gmail.com> wrote:
>>> On Tue, Jul 12, 2011 at 12:54 PM, ant elder <an...@gmail.com> wrote:
>>>> I've been trying to help a user get going with one of the samples
>>>> using the latest code but its ended up needing a bunch of change to
>>>> the sample pom.xml's to get it to work with the latest snapshot code.
>>>> One of the issues is if you checkout a sample like
>>>> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/helloworld/
>>>> and try to build it that doesn't work unless you've built trunk
>>>> locally.
>>>
>>> So, wouldn't this be a similar issue if you get a released version of
>>> the helloworld with a released version of tuscany compared to the most
>>> recent snapshots ?
>>>
>>>> But thats just one of the reasons, its been ages since we did
>>>> a trunk release and there are lots of good changes in there. Last time
>>>> we talked about this I couldn't find three people who said they'd vote
>>>> for a release, If i just cut an RC of what the trunk builds now i
>>>> expect there are a lot of broken samples missing doc and and incorrect
>>>> readme's so whats the minimum we could do to fix that which would get
>>>> three +1s? If i just did a trunk source release + maven module release
>>>> but no binary distro would anyone vote for that? Or if i stripped out
>>>> all the samples or maybe except for one or two samples which really
>>>> worked and had good READMEs would you vote for that? Or what else
>>>> would it take?
>>>>
>>>>  ...ant
>>>>
>>>
>>> What would be the "version name" for the release ? I think we should
>>> do a regular milestone/beta release and I'd be ok if some samples
>>> might be broken, but I wouldn't like to see source only distros, as
>>> that would kind require the users to have to build anyway, unless they
>>> are using maven which it's not really a requirement we have imposed
>>> into users before.
>>>
>>
>> Ok thats sounding more promising, i don't mind not doing a source only
>> release i just want _a_ release with the module jars in maven central,
>> i don't mind what its called 2.0-Beta3 or M6 or something else. So how
>> about if its called 2.0-Beta3 and based off the current trunk so the
>> samples and distro are as they are. I'll try and clean up some
>> helloworld samples but i wont have the time to make all of the samples
>> perfect.
>>
>>   ...ant
>>
>
> What's the timeframe you are looking for ? I could look at some
> samples and other minor cleanups over the weekend.
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

I can try and take a look through the samples over the next couple of
days and do some tidying.

Simon

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

Re: How can we do a next 2.x release?

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

On Tue, Jul 12, 2011 at 3:16 PM, ant elder <an...@apache.org> wrote:
> On Tue, Jul 12, 2011 at 10:30 PM, Luciano Resende <lu...@gmail.com> wrote:
>> On Tue, Jul 12, 2011 at 12:54 PM, ant elder <an...@gmail.com> wrote:
>>> I've been trying to help a user get going with one of the samples
>>> using the latest code but its ended up needing a bunch of change to
>>> the sample pom.xml's to get it to work with the latest snapshot code.
>>> One of the issues is if you checkout a sample like
>>> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/helloworld/
>>> and try to build it that doesn't work unless you've built trunk
>>> locally.
>>
>> So, wouldn't this be a similar issue if you get a released version of
>> the helloworld with a released version of tuscany compared to the most
>> recent snapshots ?
>>
>>> But thats just one of the reasons, its been ages since we did
>>> a trunk release and there are lots of good changes in there. Last time
>>> we talked about this I couldn't find three people who said they'd vote
>>> for a release, If i just cut an RC of what the trunk builds now i
>>> expect there are a lot of broken samples missing doc and and incorrect
>>> readme's so whats the minimum we could do to fix that which would get
>>> three +1s? If i just did a trunk source release + maven module release
>>> but no binary distro would anyone vote for that? Or if i stripped out
>>> all the samples or maybe except for one or two samples which really
>>> worked and had good READMEs would you vote for that? Or what else
>>> would it take?
>>>
>>>  ...ant
>>>
>>
>> What would be the "version name" for the release ? I think we should
>> do a regular milestone/beta release and I'd be ok if some samples
>> might be broken, but I wouldn't like to see source only distros, as
>> that would kind require the users to have to build anyway, unless they
>> are using maven which it's not really a requirement we have imposed
>> into users before.
>>
>
> Ok thats sounding more promising, i don't mind not doing a source only
> release i just want _a_ release with the module jars in maven central,
> i don't mind what its called 2.0-Beta3 or M6 or something else. So how
> about if its called 2.0-Beta3 and based off the current trunk so the
> samples and distro are as they are. I'll try and clean up some
> helloworld samples but i wont have the time to make all of the samples
> perfect.
>
>   ...ant
>

What's the timeframe you are looking for ? I could look at some
samples and other minor cleanups over the weekend.

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

Re: How can we do a next 2.x release?

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

On Tue, Jul 12, 2011 at 10:30 PM, Luciano Resende <lu...@gmail.com> wrote:
> On Tue, Jul 12, 2011 at 12:54 PM, ant elder <an...@gmail.com> wrote:
>> I've been trying to help a user get going with one of the samples
>> using the latest code but its ended up needing a bunch of change to
>> the sample pom.xml's to get it to work with the latest snapshot code.
>> One of the issues is if you checkout a sample like
>> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/helloworld/
>> and try to build it that doesn't work unless you've built trunk
>> locally.
>
> So, wouldn't this be a similar issue if you get a released version of
> the helloworld with a released version of tuscany compared to the most
> recent snapshots ?
>
>> But thats just one of the reasons, its been ages since we did
>> a trunk release and there are lots of good changes in there. Last time
>> we talked about this I couldn't find three people who said they'd vote
>> for a release, If i just cut an RC of what the trunk builds now i
>> expect there are a lot of broken samples missing doc and and incorrect
>> readme's so whats the minimum we could do to fix that which would get
>> three +1s? If i just did a trunk source release + maven module release
>> but no binary distro would anyone vote for that? Or if i stripped out
>> all the samples or maybe except for one or two samples which really
>> worked and had good READMEs would you vote for that? Or what else
>> would it take?
>>
>>  ...ant
>>
>
> What would be the "version name" for the release ? I think we should
> do a regular milestone/beta release and I'd be ok if some samples
> might be broken, but I wouldn't like to see source only distros, as
> that would kind require the users to have to build anyway, unless they
> are using maven which it's not really a requirement we have imposed
> into users before.
>

Ok thats sounding more promising, i don't mind not doing a source only
release i just want _a_ release with the module jars in maven central,
i don't mind what its called 2.0-Beta3 or M6 or something else. So how
about if its called 2.0-Beta3 and based off the current trunk so the
samples and distro are as they are. I'll try and clean up some
helloworld samples but i wont have the time to make all of the samples
perfect.

   ...ant

Re: How can we do a next 2.x release?

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

On Tue, Jul 12, 2011 at 12:54 PM, ant elder <an...@gmail.com> wrote:
> I've been trying to help a user get going with one of the samples
> using the latest code but its ended up needing a bunch of change to
> the sample pom.xml's to get it to work with the latest snapshot code.
> One of the issues is if you checkout a sample like
> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/helloworld/
> and try to build it that doesn't work unless you've built trunk
> locally.

So, wouldn't this be a similar issue if you get a released version of
the helloworld with a released version of tuscany compared to the most
recent snapshots ?

> But thats just one of the reasons, its been ages since we did
> a trunk release and there are lots of good changes in there. Last time
> we talked about this I couldn't find three people who said they'd vote
> for a release, If i just cut an RC of what the trunk builds now i
> expect there are a lot of broken samples missing doc and and incorrect
> readme's so whats the minimum we could do to fix that which would get
> three +1s? If i just did a trunk source release + maven module release
> but no binary distro would anyone vote for that? Or if i stripped out
> all the samples or maybe except for one or two samples which really
> worked and had good READMEs would you vote for that? Or what else
> would it take?
>
>  ...ant
>

What would be the "version name" for the release ? I think we should
do a regular milestone/beta release and I'd be ok if some samples
might be broken, but I wouldn't like to see source only distros, as
that would kind require the users to have to build anyway, unless they
are using maven which it's not really a requirement we have imposed
into users before.

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