That last question was asking who built the previous, working version? Who built 0.6.3? Gavin, you, or other?
Ah. 0.6.3 was the build from bitcoin.org too. 
Topic: Bitcoin-Qt/bitcoind version 0.7.0 released - page 3. (Read 25323 times)
We updated today from 6020 to 70003 all went smooth, thank you very much!
One thing we can't figure out. Why bitcoind API can't return the senders address from a transaction?
We are still using third parties for this operation which is far from optimal. I believe that lot of others have the same needs as I read in other posts.
One thing we can't figure out. Why bitcoind API can't return the senders address from a transaction?
We are still using third parties for this operation which is far from optimal. I believe that lot of others have the same needs as I read in other posts.
hmmm, it sounds like there may be an OSX-specific problem.
What is the previous known working version?
Was that an official OSX build from Gavin, your own build, or a third party build?
Thanks.
0.6.3 also works fine here.What is the previous known working version?
Was that an official OSX build from Gavin, your own build, or a third party build?
Thanks.
0.7 was the official build from bitcoin.org.
That last question was asking who built the previous, working version? Who built 0.6.3? Gavin, you, or other?
hmmm, it sounds like there may be an OSX-specific problem.
What is the previous known working version?
Was that an official OSX build from Gavin, your own build, or a third party build?
Thanks.
0.6.3 also works fine here.What is the previous known working version?
Was that an official OSX build from Gavin, your own build, or a third party build?
Thanks.
0.7 was the official build from bitcoin.org.
A sincere "Thank you!" to all the developers.
First, thank you!
Second, if it's not too much trouble: two datetime columns on address Book would be great: created, last txn
Second, if it's not too much trouble: two datetime columns on address Book would be great: created, last txn
I'd like to request people using bitcoind to NOT upgrade and force the devs to deal with changes properly.
These 2 changes above are ridiculous.
Can we expect the next version of bitcoin to remove other things that people are using and simply say - bad luck - see you later?
Have any of the bitcoin devs ever worked in a real production environment?
This sort of change suggests the answer to that question is 'no'.
We already had a nightmare of problems back in April due to not dealing with change properly, why are we still seeing this lack of proper procedure here with this 0.7.0 release?
This is a major version update, so things like this can be expected. Even if they had left those features in, the upgrade still might not be seamless for business users. If you don't want to update immediately to the new version, old versions still receive bugfix-only updates for about 1 year or so.These 2 changes above are ridiculous.
Can we expect the next version of bitcoin to remove other things that people are using and simply say - bad luck - see you later?
Have any of the bitcoin devs ever worked in a real production environment?
This sort of change suggests the answer to that question is 'no'.
We already had a nightmare of problems back in April due to not dealing with change properly, why are we still seeing this lack of proper procedure here with this 0.7.0 release?
0.6.4 is currently being tested here:
https://bitcointalksearch.org/topic/please-help-test-bitcoin-stable-maintenance-versions-064rc3-etc-110231
0.7 quits unexpectedly immediately after launch on my OSX 10.5.8.
Is anyone else having this issue?
Is anyone else having this issue?
Yes, that's what I'm seeing.
hmmm, it sounds like there may be an OSX-specific problem.
Could be, hopefully Gavin will find something useful in my debug.log file.
What is the previous known working version?
0.6.3, which is running right now.
Was that an official OSX build from Gavin, your own build, or a third party build?
It was the official release.
0.7 quits unexpectedly immediately after launch on my OSX 10.5.8.
Is anyone else having this issue?
Is anyone else having this issue?
Yes, that's what I'm seeing.
hmmm, it sounds like there may be an OSX-specific problem.
What is the previous known working version?
Was that an official OSX build from Gavin, your own build, or a third party build?
Thanks.
. . . a real production environment . . . this 0.7.0 release?
From everything I've seen the bitcoin client has always appeared to me to be in Beta.Correct.
And beyond that, the RPC API has never had the same ironclad backwards-compat guarantees that the blockchain and P2P network have. From satoshi's time to present, RPC calls have been considered an internal control plane. Compatibility with existing use cases is very important, even with RPC API, but sometimes there are exceptions: deprecated, unused APIs; APIs where we've discussed and planned for changes ahead of time, etc.
From everything I've seen the bitcoin client has always appeared to me to be in Beta.
Are you insinuating we shouldn't use beta software to do real work? 
...
gavin any chance of seeing big endian/little endian compatibility someday?
For the main client it is low priority.
But in a blatant plug... https://github.com/jgarzik/pynode does support big + little endian out of the box.
From everything I've seen the bitcoin client has always appeared to me to be in Beta.
Are you insinuating we shouldn't use beta software to do real work? So - since the software is in beta the changes done shouldn't be treated appropriately? ...
And ... yes your quote is trying to create a link between 2 things I said that were not linked at all ...
I used ellipsis to show that content had been removed from the original and left the link there so that anybody who wants to can see the context. Not trying to hide anything.And ... yes your quote is trying to create a link between 2 things I said that were not linked at all ...
How were they not linked? You asked if the bitcoin devs had ever worked in a production environment and then complained about the way they were handling 0.7.0 which is a beta release.
Feel free to create competing software. It is open source after all, and the protocol is public knowledge. If you can provide a better product and do a better job of treating changes properly, then yours will likely become the new standard.
0.7 quits unexpectedly immediately after launch on my OSX 10.5.8.
Is anyone else having this issue?
Is anyone else having this issue?
Yes, that's what I'm seeing.
The Mac version crashes on launch on my Leopard box, so I guess I'll wait for 0.7.1 and see what happens.
. . . a real production environment . . . this 0.7.0 release?
From everything I've seen the bitcoin client has always appeared to me to be in Beta.And ... yes your quote is trying to create a link between 2 things I said that were not linked at all ...
. . . a real production environment . . . this 0.7.0 release?
From everything I've seen the bitcoin client has always appeared to me to be in Beta.Are you insinuating we shouldn't use beta software to do real work?
. . . a real production environment . . . this 0.7.0 release?
From everything I've seen the bitcoin client has always appeared to me to be in Beta. Bitcoin version 0.7.0 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.0/
We recommend that everybody running prior versions of bitcoind/Bitcoin-Qt
upgrade to this release.
...
JSON-RPC API
...
* Remove deprecated RPC 'getblocknumber'
* Remove superceded RPC 'getmemorypool' (see BIP 22, above)
...
I'd like to request people using bitcoind to NOT upgrade and force the devs to deal with changes properly.http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.0/
We recommend that everybody running prior versions of bitcoind/Bitcoin-Qt
upgrade to this release.
...
JSON-RPC API
...
* Remove deprecated RPC 'getblocknumber'
* Remove superceded RPC 'getmemorypool' (see BIP 22, above)
...
These 2 changes above are ridiculous.
Can we expect the next version of bitcoin to remove other things that people are using and simply say - bad luck - see you later?
Have any of the bitcoin devs ever worked in a real production environment?
This sort of change suggests the answer to that question is 'no'.
We already had a nightmare of problems back in April due to not dealing with change properly, why are we still seeing this lack of proper procedure here with this 0.7.0 release?
Anybody got a plain English explanation?
Jump to: