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

[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?

[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?

[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?

[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?

[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?

[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