You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Rafael Schloming <rh...@alum.mit.edu> on 2014/10/28 20:59:53 UTC
Proton release planning
Hi Everyone,
I'd like to try to get the proton releases to be a bit more frequent, and
I'm also trying to get a bit more up front planning into them. To that end
I've put together a quick description of what I'd propose for timeline and
scope of the next release here:
http://qpid.apache.org/proton/development.html
Please have a look and let me know what you think.
--Rafael
Re: Proton release planning
Posted by Rafael Schloming <rh...@alum.mit.edu>.
It probably should. I will make that explicit in the document.
--Rafael
On Tue, Oct 28, 2014 at 4:53 PM, Steve Huston <sh...@riverace.com> wrote:
> Great - thanks - I can see it now.
>
> Question on the goals... does the API stabilization item include
> additional API exposed from Proton to detect frame boundaries needed for
> websockets implementations?
>
> Thanks,
> -Steve
>
> > -----Original Message-----
> > From: Rafael Schloming [mailto:rhs@alum.mit.edu]
> > Sent: Tuesday, October 28, 2014 4:23 PM
> > To: users@qpid.apache.org
> > Subject: Re: Proton release planning
> >
> > I'm not sure exactly what's going on. The link seems to randomly work
> > sometimes and not work at other times. I did just check it in only a few
> > minutes ago, so (random guess) maybe the svnpubsub process has only
> > partially updated whatever cluster serves those pages. I hope it will
> stabilize
> > soon, but until then you can read the source for the document here if you
> > want:
> >
> >
> > http://svn.apache.org/repos/asf/qpid/site/input/proton/development.md
> >
> > --Rafael
> >
> > On Tue, Oct 28, 2014 at 4:01 PM, Steve Huston <sh...@riverace.com>
> > wrote:
> >
> > > The requested URL /proton/development.html was not found on this
> > server.
> > >
> > > > -----Original Message-----
> > > > From: Rafael Schloming [mailto:rhs@alum.mit.edu]
> > > > Sent: Tuesday, October 28, 2014 4:00 PM
> > > > To: proton@qpid.apache.org; dev@qpid.apache.org;
> > > > users@qpid.apache.org
> > > > Subject: Proton release planning
> > > >
> > > > Hi Everyone,
> > > >
> > > > I'd like to try to get the proton releases to be a bit more
> > > > frequent,
> > > and I'm
> > > > also trying to get a bit more up front planning into them. To that
> > > > end
> > > I've put
> > > > together a quick description of what I'd propose for timeline and
> > > > scope
> > > of
> > > > the next release here:
> > > >
> > > > http://qpid.apache.org/proton/development.html
> > > >
> > > > Please have a look and let me know what you think.
> > > >
> > > > --Rafael
> > >
>
RE: Proton release planning
Posted by Steve Huston <sh...@riverace.com>.
Great - thanks - I can see it now.
Question on the goals... does the API stabilization item include additional API exposed from Proton to detect frame boundaries needed for websockets implementations?
Thanks,
-Steve
> -----Original Message-----
> From: Rafael Schloming [mailto:rhs@alum.mit.edu]
> Sent: Tuesday, October 28, 2014 4:23 PM
> To: users@qpid.apache.org
> Subject: Re: Proton release planning
>
> I'm not sure exactly what's going on. The link seems to randomly work
> sometimes and not work at other times. I did just check it in only a few
> minutes ago, so (random guess) maybe the svnpubsub process has only
> partially updated whatever cluster serves those pages. I hope it will stabilize
> soon, but until then you can read the source for the document here if you
> want:
>
>
> http://svn.apache.org/repos/asf/qpid/site/input/proton/development.md
>
> --Rafael
>
> On Tue, Oct 28, 2014 at 4:01 PM, Steve Huston <sh...@riverace.com>
> wrote:
>
> > The requested URL /proton/development.html was not found on this
> server.
> >
> > > -----Original Message-----
> > > From: Rafael Schloming [mailto:rhs@alum.mit.edu]
> > > Sent: Tuesday, October 28, 2014 4:00 PM
> > > To: proton@qpid.apache.org; dev@qpid.apache.org;
> > > users@qpid.apache.org
> > > Subject: Proton release planning
> > >
> > > Hi Everyone,
> > >
> > > I'd like to try to get the proton releases to be a bit more
> > > frequent,
> > and I'm
> > > also trying to get a bit more up front planning into them. To that
> > > end
> > I've put
> > > together a quick description of what I'd propose for timeline and
> > > scope
> > of
> > > the next release here:
> > >
> > > http://qpid.apache.org/proton/development.html
> > >
> > > Please have a look and let me know what you think.
> > >
> > > --Rafael
> >
Re: Proton release planning
Posted by Rafael Schloming <rh...@alum.mit.edu>.
I'm not sure exactly what's going on. The link seems to randomly work
sometimes and not work at other times. I did just check it in only a few
minutes ago, so (random guess) maybe the svnpubsub process has only
partially updated whatever cluster serves those pages. I hope it will
stabilize soon, but until then you can read the source for the document
here if you want:
http://svn.apache.org/repos/asf/qpid/site/input/proton/development.md
--Rafael
On Tue, Oct 28, 2014 at 4:01 PM, Steve Huston <sh...@riverace.com> wrote:
> The requested URL /proton/development.html was not found on this server.
>
> > -----Original Message-----
> > From: Rafael Schloming [mailto:rhs@alum.mit.edu]
> > Sent: Tuesday, October 28, 2014 4:00 PM
> > To: proton@qpid.apache.org; dev@qpid.apache.org; users@qpid.apache.org
> > Subject: Proton release planning
> >
> > Hi Everyone,
> >
> > I'd like to try to get the proton releases to be a bit more frequent,
> and I'm
> > also trying to get a bit more up front planning into them. To that end
> I've put
> > together a quick description of what I'd propose for timeline and scope
> of
> > the next release here:
> >
> > http://qpid.apache.org/proton/development.html
> >
> > Please have a look and let me know what you think.
> >
> > --Rafael
>
RE: Proton release planning
Posted by Steve Huston <sh...@riverace.com>.
The requested URL /proton/development.html was not found on this server.
> -----Original Message-----
> From: Rafael Schloming [mailto:rhs@alum.mit.edu]
> Sent: Tuesday, October 28, 2014 4:00 PM
> To: proton@qpid.apache.org; dev@qpid.apache.org; users@qpid.apache.org
> Subject: Proton release planning
>
> Hi Everyone,
>
> I'd like to try to get the proton releases to be a bit more frequent, and I'm
> also trying to get a bit more up front planning into them. To that end I've put
> together a quick description of what I'd propose for timeline and scope of
> the next release here:
>
> http://qpid.apache.org/proton/development.html
>
> Please have a look and let me know what you think.
>
> --Rafael
Re: Proton release planning
Posted by Rafael Schloming <rh...@alum.mit.edu>.
The grand scheme as I understand it is that the qpid-jms client is being
developed on top of proton as a standalone JMS client (i.e. not tied to any
broker, but obviously dependent on proton). This is distinct from the
"proton-jms" module which is in the proton contrib directory. The latter is
a bunch of utility code, but not an actual client.
--Rafael
On Wed, Oct 29, 2014 at 2:02 PM, Gibson, Jack <ja...@paypal.com.invalid>
wrote:
> No issue with the separation but was thinking back to the original
> exchange on this thread about there being a proton-jms driver in the long
> run (maybe I misread). So, guess the larger question is that in the grand
> scheme or will the JMS driver be attached to qpid-broker? Sorry if I
> didn¹t ask it the question clearly after re-reading it I can see how I
> wasn¹t clear.
>
> JG
>
>
> Jack Gibson
> Global Platform Services
> Ebay
>
>
>
>
> On 10/29/14, 12:29 PM, "Rafael Schloming" <rh...@alum.mit.edu> wrote:
>
> >On Wed, Oct 29, 2014 at 11:40 AM, Gibson, Jack
> ><ja...@paypal.com.invalid>
> >wrote:
> >
> >>
> >> Is the plan to keep JMS in a separate project and managed separately as
> >> part of qpid? How are the dependencies between Proton and Qpid-JMS
> >>going
> >> to be addressed?
> >>
> >
> >As of now the plan is to keep them separate. Both proton-j and qpid-jms
> >use
> >maven for building and dependency management.
> >
> >Is the separation an issue for you?
> >
> >--Rafael
>
>
Re: Proton release planning
Posted by "Gibson, Jack" <ja...@paypal.com.INVALID>.
No issue with the separation but was thinking back to the original
exchange on this thread about there being a proton-jms driver in the long
run (maybe I misread). So, guess the larger question is that in the grand
scheme or will the JMS driver be attached to qpid-broker? Sorry if I
didn¹t ask it the question clearly after re-reading it I can see how I
wasn¹t clear.
JG
Jack Gibson
Global Platform Services
Ebay
On 10/29/14, 12:29 PM, "Rafael Schloming" <rh...@alum.mit.edu> wrote:
>On Wed, Oct 29, 2014 at 11:40 AM, Gibson, Jack
><ja...@paypal.com.invalid>
>wrote:
>
>>
>> Is the plan to keep JMS in a separate project and managed separately as
>> part of qpid? How are the dependencies between Proton and Qpid-JMS
>>going
>> to be addressed?
>>
>
>As of now the plan is to keep them separate. Both proton-j and qpid-jms
>use
>maven for building and dependency management.
>
>Is the separation an issue for you?
>
>--Rafael
Re: Proton release planning
Posted by Rafael Schloming <rh...@alum.mit.edu>.
On Wed, Oct 29, 2014 at 11:40 AM, Gibson, Jack <ja...@paypal.com.invalid>
wrote:
>
> Is the plan to keep JMS in a separate project and managed separately as
> part of qpid? How are the dependencies between Proton and Qpid-JMS going
> to be addressed?
>
As of now the plan is to keep them separate. Both proton-j and qpid-jms use
maven for building and dependency management.
Is the separation an issue for you?
--Rafael
Re: Proton release planning
Posted by "Gibson, Jack" <ja...@paypal.com.INVALID>.
Is the plan to keep JMS in a separate project and managed separately as
part of qpid? How are the dependencies between Proton and Qpid-JMS going
to be addressed?
Jack
On 10/29/14, 9:13 AM, "Ken Giusti" <kg...@redhat.com> wrote:
>Hey Rafi - thanks for doing this.
>
>Can we add support for Python 3 in the timeline?
>
>----- Original Message -----
>> From: "Rafael Schloming" <rh...@alum.mit.edu>
>> To: proton@qpid.apache.org, dev@qpid.apache.org, users@qpid.apache.org
>> Sent: Tuesday, October 28, 2014 3:59:53 PM
>> Subject: Proton release planning
>>
>> Hi Everyone,
>>
>> I'd like to try to get the proton releases to be a bit more frequent,
>>and
>> I'm also trying to get a bit more up front planning into them. To that
>>end
>> I've put together a quick description of what I'd propose for timeline
>>and
>> scope of the next release here:
>>
>> http://qpid.apache.org/proton/development.html
>>
>> Please have a look and let me know what you think.
>>
>> --Rafael
>>
>
>--
>-K
Re: Proton release planning
Posted by Rafael Schloming <rh...@alum.mit.edu>.
On Wed, Oct 29, 2014 at 10:13 AM, Ken Giusti <kg...@redhat.com> wrote:
> Hey Rafi - thanks for doing this.
>
> Can we add support for Python 3 in the timeline?
>
Without a patch or some exploratory work on it, I'm not really sure where
I'd slot it in.
--Rafael
Re: Proton release planning
Posted by Ken Giusti <kg...@redhat.com>.
Hey Rafi - thanks for doing this.
Can we add support for Python 3 in the timeline?
----- Original Message -----
> From: "Rafael Schloming" <rh...@alum.mit.edu>
> To: proton@qpid.apache.org, dev@qpid.apache.org, users@qpid.apache.org
> Sent: Tuesday, October 28, 2014 3:59:53 PM
> Subject: Proton release planning
>
> Hi Everyone,
>
> I'd like to try to get the proton releases to be a bit more frequent, and
> I'm also trying to get a bit more up front planning into them. To that end
> I've put together a quick description of what I'd propose for timeline and
> scope of the next release here:
>
> http://qpid.apache.org/proton/development.html
>
> Please have a look and let me know what you think.
>
> --Rafael
>
--
-K