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 <[email protected]> wrote: > > > On Fri, Oct 1, 2010 at 6:03 PM, Luciano Resende <[email protected]>wrote: > >> On Fri, Oct 1, 2010 at 1:26 AM, Simon Laws <[email protected]> >> wrote: >> > On Fri, Oct 1, 2010 at 9:19 AM, Florian MOGA <[email protected]> >> 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 > > > > > > >
