Aidan/Justin,

That was precisely what I was hoping for :)
Any ways I have a bunch of patches and it will take till friday to get
them in completely.
I will try to post them as soon as possible in review board say end of
wednesday.
Based on that lets make a call about what items can be approved or not.

Rajith

On Tue, Jun 14, 2011 at 10:47 AM, Justin Ross <[email protected]> wrote:
>
> I agree, and that's why I prefer to set the deadlines to the middle of the 
> week.  That way if we slip a little, there's still a chance we'll get it that 
> week and not the next.
>
> Rajith (or anyone else facing a similar problem), are the changes you'd like 
> to see in 0.12 looking like they will land by end of day Wednesday?  Just so 
> I can determine when we can accept it, what's the new feature and what is its 
> current status?
>
> Justin
>
> ----- Original Message -----
> From: "Aidan Skinner" <[email protected]>
> To: [email protected]
> Sent: Friday, June 3, 2011 1:43:45 AM
> Subject: Re: 0.12 release update - upcoming dates
>
> I'm really only passing through qpid-dev, so feel free to ignore me,
> but IME Friday deadlines turn into Monday deadlines turn into
> Wednesday the week after deadlines all too easily.
>
> - Aidan
>
> On Thu, Jun 2, 2011 at 2:21 PM, Rajith Attapattu <[email protected]> wrote:
> > Justin,
> >
> > Wondering if you could move the beta date to 17th of June (friday) instead
> > of the 15th?
> >
> > Regards,
> >
> > Rajith
> >
> > On Tue, May 31, 2011 at 5:19 PM, Justin Ross <[email protected]> wrote:
> >
> >> Hi, folks.  Here are some of the upcoming dates for the 0.12 release
> >> of Qpid.
> >>
> >>  - 3 March - 0.12 trunk opened
> >>  - 15 June - 0.12 alpha (in a little over 2 weeks)
> >>  - 28 June - 0.12 beta
> >>  - 27 July - Target date for the final 0.12 release candidate
> >>
> >> The alpha date is the deadline for landing major features.  Said
> >> features must be functionally complete, with all distribution-related
> >> integration complete.
> >>
> >> After the alpha, we may still be able to accept a new feature, but it
> >> must be something (a) quite small or (b) isolated from the other code.
> >> In addition, it must not change the existing distribution artifacts in
> >> any significant way.
> >>
> >> With the beta, we will create the 0.12 release branch, and 0.14
> >> development can then begin on trunk.
> >>
> >> The release page[1] has links to the jiras for 0.12 and an overview of
> >> the schedule.
> >>
> >> Thanks!
> >> Justin
> >>
> >> ---
> >> [1] https://cwiki.apache.org/confluence/display/qpid/0.12+Release
> >>
> >> ---------------------------------------------------------------------
> >> Apache Qpid - AMQP Messaging Implementation
> >> Project:      http://qpid.apache.org
> >> Use/Interact: mailto:[email protected]
> >>
> >>
> >
>
>
>
> --
> Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org
> "A witty saying proves nothing" - Voltaire
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to