On Fri, Jan 04, 2013 at 03:56:54PM -0500, Rafael Schloming wrote:
> > Not difficult, no. We just have to pass it through a similar filter as
> > would be done when using autoconf. For development purposes the version
> > doesn't matter, just when we're creating those artifacts.
> >
> > So we could
On Fri, Jan 4, 2013 at 1:22 PM, Darryl L. Pierce wrote:
> On Fri, Jan 04, 2013 at 11:21:07AM -0500, Rafael Schloming wrote:
> > > I pushed a patch this morning that bumped the Perl and Ruby versions.
> > > Can you please include that in RC2? Thanks.
> > >
> >
> > That will be picked up for RC2, b
On Fri, Jan 04, 2013 at 11:21:07AM -0500, Rafael Schloming wrote:
> > I pushed a patch this morning that bumped the Perl and Ruby versions.
> > Can you please include that in RC2? Thanks.
> >
>
> That will be picked up for RC2, but I really think we need one and only one
> place to bump the versio
en we branch, the above files
> > > should all have their versions bumped on trunk. Right now we've got 0.2
> > > for proton-c in the 0.3 RC1 tarball, Ruby is saying 0.1 (my bad) and
> > > Perl is 0.2 (same).
> > >
> >
> > Can we make these all r
bindings/perl/ChangeLog
> > proton-c/bindings/ruby/lib/qpid_proton/version.rb
> > proton-c/bindings/ruby/ChangeLog
> >
> > Though probably the easiest thing is, when we branch, the above files
> > should all have their versions bumped on trunk. Right now we've got
mp the release
> number in the following files:
>
> proton-c/CMakeLists.txt
> proton-c/bindings/perl/Makefile.PL
> proton-c/bindings/perl/ChangeLog
> proton-c/bindings/ruby/lib/qpid_proton/version.rb
> proton-c/bindings/ruby/ChangeLog
>
> Though probably the easiest thing is, when
bindings/ruby/lib/qpid_proton/version.rb
proton-c/bindings/ruby/ChangeLog
Though probably the easiest thing is, when we branch, the above files
should all have their versions bumped on trunk. Right now we've got 0.2
for proton-c in the 0.3 RC1 tarball, Ruby is saying 0.1 (my bad) and
Perl is 0.
Rafi,
If you are spinning another RC please include [1] ?
It's done to ensure we close tcp connections.
Please see [2] for details.
[1] http://svn.apache.org/viewvc?rev=1425124&view=rev
[2] https://reviews.apache.org/r/7934/diff/3/?file=236677#file236677line108
Rajith
On Fri, Dec 21, 2012 at 2
I hit a python problem on Centos-5 - which uses python 2.4:
[kgiusti@localhost tests]$ ./proton-test
Traceback (most recent call last):
File "./proton-test", line 553, in ?
m = __import__(name, None, None, ["dummy"])
File
"/home/kgiusti/work/proton/RC3/qpid-proton-c-0.3/tests/proton_tes
On Fri, Dec 21, 2012 at 9:32 AM, Ken Giusti wrote:
> Ok, thanks Darryl - I'll give it a try.
>
> In any case, the README file in the release candidate needs to be updated
> - I imagine most folks just starting out with proton want to be able to
> evaluate it without needing root privs.
>
I'll up
Ok, thanks Darryl - I'll give it a try.
In any case, the README file in the release candidate needs to be updated - I
imagine most folks just starting out with proton want to be able to evaluate it
without needing root privs.
-K
- Original Message -
> On Thu, Dec 20, 2012 at 03:24:20PM
On Thu, Dec 20, 2012 at 03:24:20PM -0500, Ken Giusti wrote:
> make install (as per readme) fails on my Fedora 17 box when installing ruby
> binding:
>
> $ cmake -DCMAKE_INSTALL_PREFIX=/home/kgiusti/work/proton/RC3/install ..
>
> $ make all docs
>
> $ make install
> [ 64%] Built target qpid-prot
make install (as per readme) fails on my Fedora 17 box when installing ruby
binding:
$ cmake -DCMAKE_INSTALL_PREFIX=/home/kgiusti/work/proton/RC3/install ..
$ make all docs
$ make install
[ 64%] Built target qpid-proton
[ 67%] Built target proton
-- Installing:
/home/kgiusti/work/proton/RC3/i
Sources posted here: http://people.apache.org/~rhs/qpid-proton-0.3rc1/
Java binaries here:
https://repository.apache.org/content/repositories/orgapacheqpid-061/
Note that there are the following known issues:
- perl binding tarball has been omitted as the release script didn't work
(still instal
14 matches
Mail list logo
