Thank you Phil, for providing that summary. And, although I don't want to toss
around a little gasoline (petrol), I have to ask:
=== System Tests ===
Returning to another discussion point, note that the proton/tests
folder
will contain both Python and Java test suites, each of which can
On Fri, Jan 25, 2013 at 12:07:46PM -0500, Ken Giusti wrote:
I'd like to know if the intent is to keep both the Java and Python test
suites synchronized. That is, when I write a new python test, am I expected
to provide a similar test in Java?
If we hold off that decision for later the
On Fri, Jan 25, 2013 at 9:56 AM, Phil Harvey p...@philharveyonline.comwrote:
As promised, here is a proper write-up of how we're planning to modify the
Proton build system.
=== Requirements ===
I've updated the Proton build system requirements wiki page:
On 25 January 2013 18:07, Ken Giusti kgiu...@redhat.com wrote:
Thank you Phil, for providing that summary. And, although I don't want to
toss around a little gasoline (petrol), I have to ask:
=== System Tests ===
Returning to another discussion point, note that the proton/tests
folder
On 24 January 2013 14:43, Rafael Schloming r...@alum.mit.edu wrote:
On Wed, Jan 23, 2013 at 6:10 PM, Rob Godfrey rob.j.godf...@gmail.comwrote:
On 23 January 2013 19:09, Rafael Schloming r...@alum.mit.edu wrote:
I've added another wiki page that documents the proton release steps as
best I
On Wed, Jan 23, 2013 at 6:44 PM, Rob Godfrey rob.j.godf...@gmail.comwrote:
Firstly I think it would be helpful if you made clear the requirements you
consider to be essential, nice to have, unimportant and/or detrimental.
On 23 January 2013 20:17, Rafael Schloming r...@alum.mit.edu wrote:
What are people's views on the relative priority of these requirements?
Are there any I've missed? I think answering these questions is a
prerequisite for agreeing the technical solution.
With the aim of stimulating discussion regarding our requirements and
to reach a consensus, I've
I've added another wiki page that documents the proton release steps as
best I can remember. I'll updated it more during the 0.4 release:
https://cwiki.apache.org/confluence/display/qpid/Proton+Release+Steps
I think it's important to understand the overall release and testing
process as it is a
On Wed, Jan 23, 2013 at 8:01 AM, Keith W keith.w...@gmail.com wrote:
Essential
3. To change proton-api, all that is required is to edit a Java file.
- Developer productivity
This seems to be kind of a leading requirement so to speak, or at least
it's phrased a little bit oddly. That said I
On 23 January 2013 19:09, Rafael Schloming r...@alum.mit.edu wrote:
I've added another wiki page that documents the proton release steps as
best I can remember. I'll updated it more during the 0.4 release:
https://cwiki.apache.org/confluence/display/qpid/Proton+Release+Steps
I think it's
Firstly I think it would be helpful if you made clear the requirements you
consider to be essential, nice to have, unimportant and/or detrimental.
On 23 January 2013 20:17, Rafael Schloming r...@alum.mit.edu wrote:
On Wed, Jan 23, 2013 at 8:01 AM, Keith W keith.w...@gmail.com wrote:
On 21 January 2013 18:05, Rafael Schloming r...@alum.mit.edu wrote:
On Mon, Jan 21, 2013 at 9:33 AM, Rob Godfrey rob.j.godf...@gmail.com
wrote:
Ummm... it's a dependency... you're familiar with those, yeah?
The same way that the Qpid JMS clients depend on a JMS API jar, for which
the
On Tue, Jan 22, 2013 at 4:22 AM, Rob Godfrey rob.j.godf...@gmail.comwrote:
On 21 January 2013 18:05, Rafael Schloming r...@alum.mit.edu wrote:
On Mon, Jan 21, 2013 at 9:33 AM, Rob Godfrey rob.j.godf...@gmail.com
wrote:
Ummm... it's a dependency... you're familiar with those, yeah?
It sounds like we're still a little way away from reaching a consensus. As
a step towards this, I would like to clarify the relative priority of the
various requirements that have come up. I've therefore created a page on
the wiki that lists them, with a child page briefly describing the various
Thanks for posting this, I think it's a very useful step. I'd suggest
adding another Stakeholder -- someone testing a release artifact. Rob makes
a good point that the release manager is a distinct view, but I think the
desire to minimize deltas between the svn tree and the release artifacts is
I would echo some of Robs points (since he beat me to saying them msyelf :)
) and add some of my own.
I also dont see a need to check out proton-c or proton-j in isolation, if
the tests for both of them sit a level up then thats what people should be
grabbing in my mind.
Duplicating code sounds
On 21 January 2013 15:11, Rafael Schloming r...@alum.mit.edu wrote:
On Mon, Jan 21, 2013 at 7:10 AM, Rob Godfrey rob.j.godf...@gmail.com
wrote:
This results in something that is quite awkward for the C build. For
one
thing I'm not sure an svn export of the proton-c directory
On Mon, Jan 21, 2013 at 9:33 AM, Rob Godfrey rob.j.godf...@gmail.comwrote:
Ummm... it's a dependency... you're familiar with those, yeah?
The same way that the Qpid JMS clients depend on a JMS API jar, for which
the source is readily available from another source. The JNI binding would
build
On Mon, Jan 21, 2013 at 8:03 AM, Robbie Gemmell robbie.gemm...@gmail.comwrote:
I would echo some of Robs points (since he beat me to saying them msyelf :)
) and add some of my own.
I also dont see a need to check out proton-c or proton-j in isolation, if
the tests for both of them sit a
On Sat, Jan 19, 2013 at 5:48 PM, Phil Harvey p...@philharveyonline.comwrote:
I worked with Keith on this proposal so I should state up front that I'm
not coming to this debate from a neutral standpoint.
Hopefully we can find a solution that is acceptable to everyone. To this
end, we listed
I worked with Keith on this proposal so I should state up front that I'm
not coming to this debate from a neutral standpoint.
Hopefully we can find a solution that is acceptable to everyone. To this
end, we listed our understanding of the requirements on
On Fri, Jan 18, 2013 at 2:29 PM, Rafael Schloming r...@alum.mit.edu wrote:
The nub of the problem is the sharing of the Java Proton-API between
both proton-c and proton-j trees. Solutions based on svn-external and
a simple tree copy have been considered and discussed at length on
conference
22 matches
Mail list logo
