[VOTE][Qpid] M1 release

[Rajith Attapattu <ra...@gmail.com>]

Folks,

I think it's time to do a M1 release :)

Can we have a show of hands first of all for the release and then for the
components for the release.
This release is only for Java and the scripts.
Then lets create a thread on the release dates, code freeze and RC's.
So here is the format

[ ] M1 Release
[ ] Java Broker + client
[ ] Python and Ruby clients

And here is my +1 for all 3.

Regards,

Rajith

Re: [VOTE][Qpid] M1 release

[Bhupendra Bhardwaj <bh...@gmail.com>]

+1 for all three sets.

Regards,
Bhupendra Bhardwaj


On 11/6/06, Martin Ritchie <ri...@apache.org> wrote:
>
> +1 for all three from me.
>
> On 03/11/06, Rajith Attapattu <ra...@gmail.com> wrote:
> > Folks,
> >
> > I think it's time to do a M1 release :)
> >
> > Can we have a show of hands first of all for the release and then for
> the
> > components for the release.
> > This release is only for Java and the scripts.
> > Then lets create a thread on the release dates, code freeze and RC's.
> > So here is the format
> >
> > [ ] M1 Release
> > [ ] Java Broker + client
> > [ ] Python and Ruby clients
> >
> > And here is my +1 for all 3.
> >
> > Regards,
> >
> > Rajith
> >
> >
>
>
> --
> Martin Ritchie
>

Re: [VOTE][Qpid] M1 release

[Martin Ritchie <ri...@apache.org>]

+1 for all three from me.

On 03/11/06, Rajith Attapattu <ra...@gmail.com> wrote:
> Folks,
>
> I think it's time to do a M1 release :)
>
> Can we have a show of hands first of all for the release and then for the
> components for the release.
> This release is only for Java and the scripts.
> Then lets create a thread on the release dates, code freeze and RC's.
> So here is the format
>
> [ ] M1 Release
> [ ] Java Broker + client
> [ ] Python and Ruby clients
>
> And here is my +1 for all 3.
>
> Regards,
>
> Rajith
>
>


-- 
Martin Ritchie

Re: [VOTE][Qpid] M1 release

[Carl Trieloff <cc...@redhat.com>]

Robert Greig wrote:
> On 03/11/06, Carl Trieloff <cc...@redhat.com> wrote:
>>
>> I would like to do C++ also but maybe after the Java. Should we not add
>> the C# to that as it is not
>> in repo yet. i.e. do a M1 for C++ and C# a few weeks after Java. This is
>> our first time through,
>> and doing it in pieces might actually be faster so we don't have to fix
>> the same mistakes in multiple
>> places.... (if we make them, which I am sure we will)
>
> I would definitely like to get the .NET stuff in relatively quickly,
> since I believe it is stable. I don't want to do anything to delay the
> Java stuff though, so I'd be happy doing it after that. When you say
> "a few weeks" what did you have in mind?
If we do the set Rajith suggested, get the vote and take it to incubator 
PMC. they
might send us back a few times to fix stuff. Once we get it 
right/released, we do the next
set as then we will "have learnt" what we missed first time and should 
be easier for other
components. Thus the delay is basically as long as it takes for us to 
get the first set from vote to
Incubator PMC acceptance.

>
> I had not realised that we could do individual components of an M1
> release at different speeds. That is a big help.
>
> RG

Re: [VOTE][Qpid] M1 release

[Robert Greig <ro...@gmail.com>]

On 03/11/06, Carl Trieloff <cc...@redhat.com> wrote:
>
> I would like to do C++ also but maybe after the Java. Should we not add
> the C# to that as it is not
> in repo yet. i.e. do a M1 for C++ and C# a few weeks after Java. This is
> our first time through,
> and doing it in pieces might actually be faster so we don't have to fix
> the same mistakes in multiple
> places.... (if we make them, which I am sure we will)

I would definitely like to get the .NET stuff in relatively quickly,
since I believe it is stable. I don't want to do anything to delay the
Java stuff though, so I'd be happy doing it after that. When you say
"a few weeks" what did you have in mind?

I had not realised that we could do individual components of an M1
release at different speeds. That is a big help.

RG

Re: [VOTE][Qpid] M1 release

[Rajith Attapattu <ra...@gmail.com>]

If you look at Tuscany or Axis2 we have seperate release cycles for Java and
C.

So I think it's ok for us to do a Java M1 and then a C/C++ M1 a little later
on.
Cliff can you please comments on this?

Regards,

Rajith

On 11/3/06, Carl Trieloff <cc...@redhat.com> wrote:
>
>
>
> Robert Greig wrote:
> > On 03/11/06, Alan Conway <ac...@redhat.com> wrote:
> >
> >> > So here is the format
> >> >
> >> > [ ] M1 Release
> >> > [ ] Java Broker + client
> >> > [ ] Python and Ruby clients
> >
> > + 1 for all three.
> >
> > Can I also ask that we add the .NET client? I realise it has not yet
> > been committed to svn but that is due to the developer being off sick.
> > It is actually running in production now so it is stable (no changes
> > for several weeks) and just needs the files prepared for Apache. We
> > are hoping to have it done on Monday.
> I would like to do C++ also but maybe after the Java. Should we not add
> the C# to that as it is not
> in repo yet. i.e. do a M1 for C++ and C# a few weeks after Java. This is
> our first time through,
> and doing it in pieces might actually be faster so we don't have to fix
> the same mistakes in multiple
> places.... (if we make them, which I am sure we will)
>
> Rajith, if we stage, can we release them all as M1?
>
> +1 for all above in Rajith's list.
>
> Carl.
> >
> > RG
>
>

Re: [VOTE][Qpid] M1 release

[Carl Trieloff <cc...@redhat.com>]

Robert Greig wrote:
> On 03/11/06, Alan Conway <ac...@redhat.com> wrote:
>
>> > So here is the format
>> >
>> > [ ] M1 Release
>> > [ ] Java Broker + client
>> > [ ] Python and Ruby clients
>
> + 1 for all three.
>
> Can I also ask that we add the .NET client? I realise it has not yet
> been committed to svn but that is due to the developer being off sick.
> It is actually running in production now so it is stable (no changes
> for several weeks) and just needs the files prepared for Apache. We
> are hoping to have it done on Monday.
I would like to do C++ also but maybe after the Java. Should we not add 
the C# to that as it is not
in repo yet. i.e. do a M1 for C++ and C# a few weeks after Java. This is 
our first time through,
and doing it in pieces might actually be faster so we don't have to fix 
the same mistakes in multiple
places.... (if we make them, which I am sure we will)

Rajith, if we stage, can we release them all as M1?

+1 for all above in Rajith's list.

Carl.
>
> RG

Re: [VOTE][Qpid] M1 release

[Robert Greig <ro...@gmail.com>]

On 03/11/06, Alan Conway <ac...@redhat.com> wrote:

> > So here is the format
> >
> > [ ] M1 Release
> > [ ] Java Broker + client
> > [ ] Python and Ruby clients

+ 1 for all three.

Can I also ask that we add the .NET client? I realise it has not yet
been committed to svn but that is due to the developer being off sick.
It is actually running in production now so it is stable (no changes
for several weeks) and just needs the files prepared for Apache. We
are hoping to have it done on Monday.

RG

Re: [VOTE][Qpid] M1 release

[Alan Conway <ac...@redhat.com>]

+1 on all fronts.
On Fri, 2006-11-03 at 13:00 -0500, Rajith Attapattu wrote:
> Folks,
> 
> I think it's time to do a M1 release :)
> 
> Can we have a show of hands first of all for the release and then for the
> components for the release.
> This release is only for Java and the scripts.
> Then lets create a thread on the release dates, code freeze and RC's.
> So here is the format
> 
> [ ] M1 Release
> [ ] Java Broker + client
> [ ] Python and Ruby clients
> 
> And here is my +1 for all 3.
> 
> Regards,
> 
> Rajith

Re: [VOTE][Qpid] M1 release

[Gordon Sim <gs...@redhat.com>]

Rajith Attapattu wrote:
> [+1] M1 Release
> [+1] Java Broker + client
> [+1] Python and Ruby clients

Re: [VOTE][Qpid] M1 release

[Steve Vinoski <vi...@iona.com>]

+1 for all three.

On Nov 3, 2006, at 1:00 PM, Rajith Attapattu wrote:

> Folks,
>
> I think it's time to do a M1 release :)
>
> Can we have a show of hands first of all for the release and then  
> for the
> components for the release.
> This release is only for Java and the scripts.
> Then lets create a thread on the release dates, code freeze and RC's.
> So here is the format
>
> [ ] M1 Release
> [ ] Java Broker + client
> [ ] Python and Ruby clients
>
> And here is my +1 for all 3.
>
> Regards,
>
> Rajith

Re: [VOTE][Qpid] M1 release

[Rafael Schloming <ra...@redhat.com>]

Rajith Attapattu wrote:
> Folks,
> 
> I think it's time to do a M1 release :)
> 
> Can we have a show of hands first of all for the release and then for the
> components for the release.
> This release is only for Java and the scripts.
> Then lets create a thread on the release dates, code freeze and RC's.
> So here is the format
> 

[+1] M1 Release
[+1] Java Broker + client
[+1] Python and Ruby clients

The python client should be ready to release as is. I think I need to 
find a day or so to finish one last piece of the ruby client. I suggest 
we just go with simple tarballs/zips + a README file for packaging them. 
  I think we'll always want this as a distribution option, and we can 
get fancy with gems and RPMs and so forth later.

--Rafael