Hi Navin, Afaik you would need committer rights to be able to contribute anything much to the M2 release I'm afraid.
Regards, Marnie On 4/11/07, Kamath, Navin <[EMAIL PROTECTED]> wrote:
Hi Rajith, IONA would like to help out in the M2 release process. But it will probably be Tej (already a committer) or myself (not yet a committer :) who will be doing it. Is there a JIRA task for this issue so that I can know what is being exactly for here? Regards, Navin -----Original Message----- From: Rajith Attapattu [mailto:[EMAIL PROTECTED] Sent: 11 April 2007 14:01 To: [EMAIL PROTECTED] Subject: Re: [RESULT] Qpid M2 Release Thanks Martin and Rupert for the comments. Steve V is no longer with iona or the project, so somebody needs to step up here and help. Dan Kulp can you help sorting out the maven issues ? Regards, Rajith On 4/11/07, Rupert Smith <[EMAIL PROTECTED]> wrote: > > That merge list is getting long again. I tried to merge some changes I > made > that are nearer the end of it, but got conflicts so just abandoned the > merge > for the moment. Its definitely better if the list can be worked through in > order from earlier to later changes... > > On 11/04/07, Martin Ritchie <[EMAIL PROTECTED]> wrote: > > > > My understanding of the branching was that we created M2 so that the > > new AMQP features could be moved to trunk and the _relatively_ stable > > 0.8 implementation could be wound up for release before we spend a > > good few months getting the next implementation ready. > > > > A good starting point would be with the set of of open bugs and > > categorising them as M2 or M3 or later. > > > > I shall certainly do that with what I have open. > > > > The work that was done before on the legal notices won't work as we no > > longer have that information in our repository. However one of the > > driving forces behind the move to maven IIRC was to make this sort of > > thing easier. Unfortunately I haven't heard from Steve V. in a while > > as he would be the man with the answer, but maven must have a plug in > > that can generate an Apache legal notice document based on the project > > dependencies. > > > > The java trunk vs M2 difference is that I'm working mainly on M2 > > finishing off the various outstanding issues I have and > > "theoretically" merging them to trunk as I go. Unfortunately, I've not > > had time to do the merging which really needs done before trunk runs > > off with too many new changes that prevents the merge. > > > > On 10/04/07, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > > > Martin, > > > > > > I can help as much as I can and I hope that some of the work that we > put > > in > > > to the last release want have to be repeated. > > > For example the legal notices, licenses etc. > > > > > > If there are any new dependencies that we have added please let us > know. > > I > > > will create a wiki page to track M2 progress. > > > I cut the M2 branch based on request by JPM. However I am (or the > > community) > > > is not sure what is happening where. > > > > > > What is going on in the java trunk vs the M2 branch ? are > > > changes/improvements in the M2 being merged back to trunk? > > > When is the plan for M2 release? > > > > > > So lets start there and capture the items that going in to this > > release. > > > > > > Regards, > > > > > > Rajith > > > > > > > > > On 4/10/07, Martin Ritchie <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi, Rajith, > > > > > > > > Let me say thanks aswell for stepping forward but just to let you > know > > > > being the release manager is more than just cutting an a few RCs. > > > > > > > > The incubator has a guide which is not yet complete but a good > > starting > > > > read: > > > > http://incubator.apache.org/guides/releasemanagement.html > > > > > > > > In addition to this though I would say that the M2 branch has to > much > > > > development on it to release just now. I would suggest that we need > to > > > > set a cut off point for development. Of course having marked what > > > > defects are to be included in M2. Then re-branch for RC cutting and > > > > merging any resulting defects. > > > > > > > > Regards > > > > > > > > Martin > > > > > > > > On 10/04/07, Marnie McCormack <[EMAIL PROTECTED]> > wrote: > > > > > Hi Rajith, > > > > > > > > > > Thanks ! > > > > > > > > > > I think we need to create a list of tasks for M2, as we did for > M1. > > I > > > > > suspect there's a lot of cleaning up to be done before we can > create > > RCs > > > > ? > > > > > > > > > > We also need licenses etc all updated. A quick checlist for user > > docs on > > > > the > > > > > non-Java side is probably worthwhile (as this is their first > > release) > > > > ... > > > > > > > > > > Bye for now, > > > > > Marnie > > > > > > > > > > > > > > > On 4/10/07, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > Hey Marnie, > > > > > > > > > > > > I will help as stated and I have already created a M2 branch. > > > > > > I am waiting for folks to give the green light to cut the RC's > > > > > > > > > > > > Rajith > > > > > > > > > > > > On 4/10/07, Marnie McCormack <[EMAIL PROTECTED]> > > wrote: > > > > > > > > > > > > > > All, > > > > > > > > > > > > > > Does anyone want to volunteer to manage the M2 release ? > > > > > > > > > > > > > > I'm afraid that I cannot, for personal/biological reasons. > > > > > > > > > > > > > > I think M2 is pretty important for Apache Qpid in terms of > > progress, > > > > and > > > > > > > making a reasonably robust project available to download/use. > > > > > > > > > > > > > > Now easy on the stampede ...... :-) > > > > > > > > > > > > > > Thanks & Regards, > > > > > > > Marnie > > > > > > > > > > > > > > > > > > > > > On 3/15/07, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > Marnie, > > > > > > > > > > > > > > > > Hey np, I will take care of it. > > > > > > > > > > > > > > > > take it easy, > > > > > > > > > > > > > > > > Rajith > > > > > > > > > > > > > > > > On 3/15/07, Marnie McCormack < > [EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > > > > > > > > > > Hi Rajith, > > > > > > > > > > > > > > > > > > I'm happy for you to cut the branch (across all included > > > > > > technologies) > > > > > > > - > > > > > > > > > thanks. > > > > > > > > > > > > > > > > > > On the release management front, I'm afraid I'll have to > opt > > out > > > > as > > > > > > > I'm > > > > > > > > > heavily loaded at the moment. I'm also heavily pregnant so > > > > working > > > > > > to > > > > > > > a > > > > > > > > > tight schedule to get everything I need to do done before > > riding > > > > off > > > > > > > > into > > > > > > > > > the sunset :-) > > > > > > > > > > > > > > > > > > I'll still be around whilst I'm on maternity leave, but a > > little > > > > > > less > > > > > > > > > available ! > > > > > > > > > > > > > > > > > > Bfn, > > > > > > > > > Marnie > > > > > > > > > > > > > > > > > > On 3/15/07, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > > Marnie, > > > > > > > > > > > > > > > > > > > > If all parties are happy I can cut a branch for the > > release in > > > > the > > > > > > > > next > > > > > > > > > > hour. > > > > > > > > > > Marnie would u like to be the release manager for this > > release > > > > ? > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > > > > > > > > > Rajith > > > > > > > > > > > > > > > > > > > > On 3/15/07, Marnie McCormack < > > [EMAIL PROTECTED]> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > Ah. Good news and bad, imho. Happy to include Ruby but > a > > > > little > > > > > > > > > > concerned > > > > > > > > > > > that it's not going to be release-able for reasons > other > > > > than > > > > > > the > > > > > > > > code > > > > > > > > > > :-) > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > Marnie > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 3/15/07, Carl Trieloff <[EMAIL PROTECTED]> > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Marnie, > > > > > > > > > > > > > > > > > > > > > > > > 3 +1's means that the vote carries, and as we have > no > > -1's > > > > or > > > > > > > 0's > > > > > > > > > all > > > > > > > > > > > > the components in the vote > > > > > > > > > > > > should be included in M2. i.e. Ruby carried also so > it > > > > must be > > > > > > > > > > included. > > > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > Carl. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Marnie McCormack wrote: > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks for your votes and input on the M2 Release > > vote > > > > > > thread. > > > > > > > > > > > > > > > > > > > > > > > > > > I have now tallied up the votes cast, and they > look > > like > > > > > > this: > > > > > > > > > > > > > > > > > > > > > > > > > > [ +8 ] M2 Release inc Java, C++, .NET > > > > > > > > > > > > > [ +6 ] Python client (plus 2 abstentions) > > > > > > > > > > > > > [ +3 ] Ruby client (plus 5 abstentions) > > > > > > > > > > > > > > > > > > > > > > > > > > My reading of the discussions thus far is that the > > > > python is > > > > > > > > > fairly > > > > > > > > > > > well > > > > > > > > > > > > > used and thus maintained. The Ruby seems a bit > > behind > > > > this > > > > > > in > > > > > > > > > status > > > > > > > > > > > and > > > > > > > > > > > > > will shortly be subject to some additional effort > > > > (hopefully > > > > > > > > from > > > > > > > > > > > > Kevin). > > > > > > > > > > > > > > > > > > > > > > > > > > Thus, I'd conclude that we should concentrate our > > > > efforts on > > > > > > > an > > > > > > > > M2 > > > > > > > > > > > which > > > > > > > > > > > > > only includes: > > > > > > > > > > > > > > > > > > > > > > > > > > Java Broker (with a caveat on the clustered broker > > code) > > > > > > > > > > > > > Java Client > > > > > > > > > > > > > C++ Broker > > > > > > > > > > > > > C++ Client > > > > > > > > > > > > > .NET Client > > > > > > > > > > > > > Python Client > > > > > > > > > > > > > > > > > > > > > > > > > > I hope that this tallies up with the group > > consensus. > > > > I'll > > > > > > > email > > > > > > > > > > > > > separately > > > > > > > > > > > > > on release branching and management. > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks & Regards, > > > > > > > > > > > > > Marnie > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Martin Ritchie > > >
