While looking into what might be involved to fix the install issue, I
found that Andrew actually noticed and corrected it on Thursday,
http://git-wip-us.apache.org/repos/asf/qpid-proton/commit/16da86eb. He
didn't raise it as a reason to stop the release, which could be taken
as him thinking it wasn't one, although he hasn't voted either way
yet.

Whilst I agree its a bit silly given it is the first release the
'core' bit is to be in, if it doesnt break existing stuff (with votes
thus far suggesting it does not) then I am inclined to proceed with
release given the fix is trivial and folks building the source can
easily adjust it themselves should they want to use it before the next
release. Does anyone strongly disagree?

I also want to begin the process of making proton-j and proton-c
independent, with this release needing finished before I do, and
respinning would delay that until next year as I'll be taking vacation
from the weekend. I aim to release proton-c and proton-j again very
soon after that work is done to really complete the process, so the
next release isn't going to be far away at this point anyway.

Robbie

On 9 December 2016 at 21:36, Chuck Rolke <[email protected]> wrote:
> +0
>
> Observed that file qpid-proton-core[d].dll is built in all cases but
> installed in none. If that's acceptable then +1.
>
> * Verified MD5
>
> * Compiled on VisualStudio cross product of
>   [2008, 2010, 2012, 2013, 2015]
>   [x86, x64]
>   [Debug, RelWithDebInfo]
>
> * Ran several self tests on random builds - all OK.
>
> * Ran several helloworld cpp examples - all OK.
>
> * Did NOT try against any Qpidd instances.
>
>
> ----- Original Message -----
>> From: "Robbie Gemmell" <[email protected]>
>> To: [email protected]
>> Sent: Thursday, December 8, 2016 12:26:01 PM
>> Subject: [VOTE] Release Qpid Proton 0.16.0
>>
>> Hi folks,
>>
>> I have put together a first spin for a 0.16.0 Qpid Proton release, please
>> test it and vote accordingly.
>>
>> The source archive can be grabbed from:
>> https://dist.apache.org/repos/dist/dev/qpid/proton/0.16.0-rc1/
>>
>> The maven artifacts for proton-j are staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1094
>>
>> The JIRAs currently assigned are:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12338399
>>
>> It is tagged as 0.16.0-rc1 from the 0.16.x branch.
>>
>> Regards,
>> Robbie
>>
>>
>> P.S. If you want to test things out using maven (e.g with your own build)
>> you can temporarily add this to your poms to access the staging repo:
>>
>>   <repositories>
>>     <repository>
>>       <id>staging</id>
>>       
>> <url>https://repository.apache.org/content/repositories/orgapacheqpid-1094</url>
>>     </repository>
>>   </repositories>
>>
>> The dependency for proton-j would then be:
>>
>>   <dependency>
>>     <groupId>org.apache.qpid</groupId>
>>     <artifactId>proton-j</artifactId>
>>     <version>0.16.0</version>
>>   </dependency>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to