[
https://issues.apache.org/jira/browse/PROTON-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall reassigned PROTON-249:
-
Assignee: Keith Wall
Build fails on Win8 / VS 2012 with path error
[
https://issues.apache.org/jira/browse/PROTON-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13585836#comment-13585836
]
Keith Wall edited comment on PROTON-249 at 2/25/13 12:56 PM:
-
[
https://issues.apache.org/jira/browse/PROTON-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-249:
--
Priority: Blocker (was: Major)
Build fails on Win8 / VS 2012 with path error
[
https://issues.apache.org/jira/browse/PROTON-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13585838#comment-13585838
]
Keith Wall commented on PROTON-249:
---
Marked as Blocker as this currently prevents users
Hi Paul
I've successfuly reproduced your issue and are tracking our progress
under PROTON-249. We don't need your debug output at this stage.
Kind regards, Keith.
On 24 February 2013 00:27, Paul O'Fallon p...@ofallonfamily.com wrote:
I filed this as
I think I will be landing it in the code tree first, and
from there, I don't know. Any suggestions?
In the code -- I assume it should be at the top level?
i.e. a sibling of the README file? i.e.
qpid-proton-0.4/pulitzer_prize_winning_documentation
or something along those lines?
I'm strong believer in maintaining our docs in the source tree, as it
makes it easy to release docs along side the code.
Also it helps keep the docs current.
The wiki based documentation in the past had many issues, the chief
complaint being stale most of the time.
We could look at doing
Irina Boverman created PROTON-250:
-
Summary: Add -fvisibility option when building shared libraries
Key: PROTON-250
URL: https://issues.apache.org/jira/browse/PROTON-250
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Irina Boverman updated PROTON-250:
--
Description:
Add an option to hide symbols in shared libraries except when they are
declared
The vote carries with 5 +1's and 0 -1's. I'll upload the artifacts shortly.
--Rafael
On Thu, Feb 21, 2013 at 1:54 PM, Rafael Schloming r...@alum.mit.edu wrote:
Hi everyone, I've spun an RC3 with fixes for the two immediately soluble
issues that turned up with RC2. Please check it out and cast
I've uploaded the artifacts and updated the download page[1]. It will be
about 24 hours or so until the mirrors are fully synced.
[1] http://qpid.apache.org/proton/download.html
--Rafael
On Mon, Feb 25, 2013 at 12:44 PM, Rafael Schloming r...@alum.mit.edu wrote:
The vote carries with 5 +1's
[
https://issues.apache.org/jira/browse/PROTON-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13586391#comment-13586391
]
Alan Conway commented on PROTON-215:
The approach is slightly different to that
Hi Michael,
I know you mentioned plans to write some bigger document ... it is not
entirely clear to me, whether this is supposed to be a standalone
introduction or just a first chapter of the larger document. It suppose the
second is correct, right?
Also, is it introduction to Proton or just to
Hi Michael,
I'm rather a foreigner in the land of Proton, but that point of view might
make the feedback useful as well :-). As someone who didn't worked with
proton much, I would probably raise following questions ...
a) If I remember correctly, in (some of) the old Qpid APIs the flow control
I do agree with you that having documentation committed alongside code is
the right approach.
I propose that we write this documentation in Markdown syntax. That gives
us (or our users) the option of easily generating HTML whilst keeping the
barrier to entry low for authors.
I recognise that
15 matches
Mail list logo
