[Vote] Release RC6 as M4 Final

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

Here is the latest release candidate for M4:

http://people.apache.org/~rhs/qpid-M4-RC6/

Work is starting to get held up on trunk, so I'd like to encourage 
people to review and vote as soon as possible. If there are no major 
issues noted then I'll create a branch and open up the trunk early 
tomorrow afternoon. After that point fixes for the M4 release will be 
kept to an absolute minimum, so please speak up sooner rather than later 
if you spot any issues.

--Rafael

Re: [Vote] Release RC6 as M4 Final

[Jonathan Robie <jo...@redhat.com>]

+ 1

Jonathan

Re: [Vote] Release RC6 as M4 Final

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

I have fixed the licensing issues to the best of my knowledge during RC 4/5
cycles.
+1 for the release.

Rajith.

On Tue, Jan 6, 2009 at 10:25 AM, Carl Trieloff <cc...@redhat.com>wrote:

> Gordon Sim wrote:
>
>> Rafael Schloming wrote:
>>
>>> Here is the latest release candidate for M4:
>>>
>>> http://people.apache.org/~rhs/qpid-M4-RC6/<http://people.apache.org/%7Erhs/qpid-M4-RC6/>
>>>
>>
>> Looks good to me for qpidc, qpid-python and qpid-ruby. I vote to release
>> this.
>>
>
> I have checked licensing for consistency. I am +1 checking open issues we
> had in last RC have been fixed
>



-- 
Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

Re: [Vote] Release RC6 as M4 Final

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

Gordon Sim wrote:
> Rafael Schloming wrote:
>> Here is the latest release candidate for M4:
>>
>> http://people.apache.org/~rhs/qpid-M4-RC6/
>
> Looks good to me for qpidc, qpid-python and qpid-ruby. I vote to 
> release this.

I have checked licensing for consistency. I am +1 checking open issues 
we had in last RC have been fixed

Re: [Vote] Release RC6 as M4 Final

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

Aidan Skinner wrote:
> On Tue, Jan 6, 2009 at 3:19 PM, Alan Conway <ac...@redhat.com> wrote:
>> Gordon Sim wrote:
>>> Rafael Schloming wrote:
>>>> Here is the latest release candidate for M4:
>>>>
>>>> http://people.apache.org/~rhs/qpid-M4-RC6/
>>> Looks good to me for qpidc, qpid-python and qpid-ruby. I vote to release
>>> this.
>> +1
>>
>> I haven't reviewed the M4 package but I think we need to branch so the trunk
>> can re-open at this point.
> 
> I'm confused, is this a vote for the bits or for branching?

Just to be clear, there is no vote for branching. The only vote 
currently taking place is the vote for RC6 as M4.

Given that he says he hasn't reviewed the bits, I'm going to count it as 
warm and encouraging thoughts for the release process to succeed 
quickly, but not an actual vote. ;)

Alan: Please correct me if I'm missinterpreting you.

--Rafael

Re: [Vote] Release RC6 as M4 Final

[Aidan Skinner <ai...@gmail.com>]

On Tue, Jan 6, 2009 at 3:19 PM, Alan Conway <ac...@redhat.com> wrote:
> Gordon Sim wrote:
>>
>> Rafael Schloming wrote:
>>>
>>> Here is the latest release candidate for M4:
>>>
>>> http://people.apache.org/~rhs/qpid-M4-RC6/
>>
>> Looks good to me for qpidc, qpid-python and qpid-ruby. I vote to release
>> this.
>
> +1
>
> I haven't reviewed the M4 package but I think we need to branch so the trunk
> can re-open at this point.

I'm confused, is this a vote for the bits or for branching?

- Aidan
-- 
Apache Qpid - World Domination through Advanced Message Queueing
http://qpid.apache.org

Re: [Vote] Release RC6 as M4 Final

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

Gordon Sim wrote:
> Rafael Schloming wrote:
>> Here is the latest release candidate for M4:
>>
>> http://people.apache.org/~rhs/qpid-M4-RC6/
> 
> Looks good to me for qpidc, qpid-python and qpid-ruby. I vote to release 
> this.
+1

I haven't reviewed the M4 package but I think we need to branch so the trunk can 
re-open at this point.

Re: [Vote] Release RC6 as M4 Final

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

Rafael Schloming wrote:
> Here is the latest release candidate for M4:
> 
> http://people.apache.org/~rhs/qpid-M4-RC6/

Looks good to me for qpidc, qpid-python and qpid-ruby. I vote to release 
this.

Re: [Vote] Release RC6 as M4 Final

[Aidan Skinner <ai...@gmail.com>]

On Tue, Jan 6, 2009 at 3:44 AM, Rafael Schloming <ra...@redhat.com> wrote:

> Here is the latest release candidate for M4:
>
> http://people.apache.org/~rhs/qpid-M4-RC6/

I've reviewed the Java and .Net 0-8 packages and the source package,
they look ok. I think we need some text to go onto the wiki about the
0-10 WCF client's quality issues.

+ 1

- Aidan

-- 
Apache Qpid - World Domination through Advanced Message Queueing
http://qpid.apache.org

Re: [Vote] Release RC6 as M4 Final

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

2009/1/6 Steve Huston <sh...@riverace.com>:

> I've tried to come up with a more foolproof way to handle this. Visual
> C++'s make can't deal with including outside files (like the generated
> .mk files). It also doesn't have wildcards. MS Build can handle this,
> I believe, but unless/until VC++ migrates, that option is not
> available.

I also looked at this and could not believe that the VC++ project file
format was so inflexible. I can only guess that people in Microsoft
don't use VC++ project files.

I wonder if a really cheesy solution would work - how about having a
"template" .vcproj file will all the stuff in it apart from the
elements that list each file. The final stage of the code generator
(python) would just iterate through each file in the generated
directory and add the xml elements to the vcproj file? It wouldn't
have to parse the xml just go to a marker position in the file.

RG

RE: [Vote] Release RC6 as M4 Final

[Steve Huston <sh...@riverace.com>]

Hi Carl,

> Steve Huston wrote:
> >> Here is the latest release candidate for M4:
> >>
> >> http://people.apache.org/~rhs/qpid-M4-RC6/
> >>     
> >
> > -1
> >
> > Windows build fails in the broker - there were more changes to
> > generated files between RC5 and 6 - these break the Windows build
> > since the Visual Studio projects must be regenerated to match the
> > changes to generated C++ files.
>
> it their a way we can script this or generate these sections of the 
> project files, so they automajically stay in sync

I've tried to come up with a more foolproof way to handle this. Visual
C++'s make can't deal with including outside files (like the generated
.mk files). It also doesn't have wildcards. MS Build can handle this,
I believe, but unless/until VC++ migrates, that option is not
available.

I use a tool called MPC (MakefileProjectCreator:
http://ociweb.com/products/mpc) to generate the files locally, after
running the C++ code generator. It's possible for the release process
to run MPC and generate the files. The problem here is that it would
change a version-controlled artifact during release, which makes
control tough. Also, I imagine making Windows users obtain and run MPC
(which requires Perl) is a non-starter.

-Steve

Re: [Vote] Release RC6 as M4 Final

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

Steve Huston wrote:
>> Here is the latest release candidate for M4:
>>
>> http://people.apache.org/~rhs/qpid-M4-RC6/
>>     
>
> -1
>
> Windows build fails in the broker - there were more changes to
> generated files between RC5 and 6 - these break the Windows build
> since the Visual Studio projects must be regenerated to match the
> changes to generated C++ files.
>   

it their a way we can script this or generate these sections of the 
project files, so they
automajically stay in sync

Carl.

Re: [Vote] Release RC6 as M4 Final

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

Steve Huston wrote:
>> Here is the latest release candidate for M4:
>>
>> http://people.apache.org/~rhs/qpid-M4-RC6/
> 
> -1
> 
> Windows build fails in the broker - there were more changes to
> generated files between RC5 and 6 - these break the Windows build
> since the Visual Studio projects must be regenerated to match the
> changes to generated C++ files.
> 
> I'll open a jira, regenerate the project files, and commit them. I
> suggest a really speedy turnaround for RC7

Trunk now has several commits that shouldn't be part of the release. 
I've created the following branch from the RC6 revision of trunk. Please 
commit the regenerated files here:

https://svn.apache.org/repos/asf/qpid/branches/M4-RCs

Ping me when you're done and I'll generate RC7.

--Rafael

RE: [Vote] Release RC6 as M4 Final

[Steve Huston <sh...@riverace.com>]

> Here is the latest release candidate for M4:
> 
> http://people.apache.org/~rhs/qpid-M4-RC6/

-1

Windows build fails in the broker - there were more changes to
generated files between RC5 and 6 - these break the Windows build
since the Visual Studio projects must be regenerated to match the
changes to generated C++ files.

I'll open a jira, regenerate the project files, and commit them. I
suggest a really speedy turnaround for RC7

Also, the qmfconsole doesn't build (many compile errors) on Windows;
I'm not suggesting that this hold up M4.

-Steve