On Wed, May 19, 2010 at 11:09 AM, ant elder <[email protected]> wrote: > On Wed, May 19, 2010 at 10:58 AM, Simon Laws <[email protected]> > wrote: >> On Fri, May 7, 2010 at 10:57 AM, Simon Laws <[email protected]> >> wrote: >>> On Wed, May 5, 2010 at 7:27 AM, ant elder <[email protected]> wrote: >>>> On Tue, May 4, 2010 at 7:24 PM, Luciano Resende <[email protected]> >>>> wrote: >>>>> We have made a lot of progress since our last Tuscany M4 release, and >>>>> although we have talked about it in the past, we haven't actually got >>>>> to it. >>>>> >>>>> I want to start working on the M5 release, and was planning to cut a >>>>> release branch around this weekend, or early next week. >>>>> >>>>> Thoughts ? >>>>> >>>>> -- >>>>> Luciano Resende >>>>> http://people.apache.org/~lresende >>>>> http://twitter.com/lresende1975 >>>>> http://lresende.blogspot.com/ >>>>> >>>> >>>> Its been way to long since the last release so yes lets get on with >>>> this one. Taking a branch this weekend seems rushed to me though as >>>> there's still a lot that needs doing, why not try some of the cleanup >>>> in trunk first to see what the state is and what needs doing before >>>> deciding when to take a release branch? >>>> >>>> ...ant >>>> >>> >>> Having spent some time reminding myself where we're at with the distr >>> structure (samples etc.) I'd like us to hold off taking the branch a >>> little bit longer. As we're well long the milestone road now there are >>> some things I think we need to finally make decisions on, launchers, >>> samples structures etc. and a few more days spent getting the trunk >>> set up based on this before we branch will, I think, focus our minds >>> and remove an awful lot of wasted effort spent copying stuff backwards >>> and forwards. >>> >>> Simon >>> >>> -- >>> Apache Tuscany committer: tuscany.apache.org >>> Co-author of a book about Tuscany and SCA: tuscanyinaction.com >>> >> >> I've got to a point where I've made changes to the non-osgi calculator >> based samples to separate the contributions from the mechanisms by >> which the contributions are started. With various other distractions >> it's taken a *long* time to get that done. So rather than addressing >> the rest of the samples now, I propose that we use this as an example >> approach we can include in M5 and then do more work on it after the >> release. >> >> There are still things I need to do today, such as fixing up the >> README files and making sure the output jar names are consistent etc. >> so I'll still be making sample related changes during the day. >> >> There are issues that have been raised during this process, for example, >> >> 1 - the nature of the runtime jars that the samples refer to >> this is a wider discussion which I think should wait until after M5. >> 2 - the use of extension specific directories to collect samples >> together (see samples/binding-rmi for an example). >> we could just create the directories and fix this >> 3 - how command line launching will work assuming we want to support it. >> I tried the .bat file we have and that didn't work with the build >> as it is but I haven't looked at why. I'm tempted to exclude this >> option for calculator samples for M5. >> > > I think doing (2) would be good as it will make things clearer and > less cluttered, so I'm happy to go make the changes. > > Whats the problem you see with .bat script, i've just tried it and it > seemed to work ok. > > ...ant >
-- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
