Re: [Bitcoin-development] Proposed BIP status changes

2014-10-16 Thread Wladimir
Shouldn't we be doing this in a GitHub PR rather than spamming up the ML? Not really. BIP changes should be discussed on the mailing list, that's the way to get community consensus (as specified in BIP1). Wladimir --

Re: [Bitcoin-development] Proposed BIP status changes

2014-10-16 Thread Luke Dashjr
On Thursday, October 16, 2014 6:22:04 AM Wladimir wrote: Shouldn't we be doing this in a GitHub PR rather than spamming up the ML? Not really. BIP changes should be discussed on the mailing list, that's the way to get community consensus (as specified in BIP1). Wladimir Discussion vs

Re: [Bitcoin-development] Proposed BIP status changes

2014-10-15 Thread Matt Corallo
On 10/15/14 08:47, Wladimir wrote: These BIPs should go to Final state - they are implemented all over the place, and are thus entirely fixed in place now. Any changes would require a new BIP as amandment: - BIP 14 (BIP Protocol Version and User Agent) - BIP 21 (URI Scheme) ACK. -

Re: [Bitcoin-development] Proposed BIP status changes

2014-10-15 Thread Luke Dashjr
On Wednesday, October 15, 2014 8:47:18 AM Wladimir wrote: These BIPs should go to Final state - they are implemented all over the place, and are thus entirely fixed in place now. Any changes would require a new BIP as amandment: - BIP 14 (BIP Protocol Version and User Agent) ACK - BIP 21