Pages:
Author

Topic: 0.96 preliminary testing - page 7. (Read 6363 times)

staff
Activity: 3458
Merit: 6793
Just writing some code
February 10, 2017, 09:29:37 AM
#4
I currently have an open PR for translations: https://github.com/goatpig/BitcoinArmory/pull/89. The plan is to have this in for 0.96 so if people could test it and review it, that would be great.
legendary
Activity: 3766
Merit: 1364
Armory Developer
February 10, 2017, 04:45:33 AM
#3
Would it be possible to pull in my PRs on Github so as to get the Mac build going again and various other small things? Smiley Thanks.

Did #143 #148 #161 and #168. Other PRs need longer reviews and testing so that will have to wait till I get back.

To all people who submitted PRs, please rebase on top of dev. Thanks.
sr. member
Activity: 525
Merit: 282
February 10, 2017, 04:02:57 AM
#2
Would it be possible to pull in my PRs on Github so as to get the Mac build going again and various other small things? Smiley Thanks.
legendary
Activity: 3766
Merit: 1364
Armory Developer
February 09, 2017, 07:19:43 PM
#1
This time again.

Looking for people willing to build and try the dev branch. Changes can be seen here:

https://github.com/goatpig/BitcoinArmory/blob/dev/changelog.txt

This still needs some polish, but it's getting to the point where it's about done. SegWit is currently hardcoded disabled on mainnet, and enabled on testnet.

Due to the newly introduced script types, I strongly suggest people test this on testnet first before moving the mainnet.

Here is a list of what's missing/known as buggy, so that the testers can focus on what is supposed to be fully functional:

- The initialization progress bars are wacky atm.
- Still have to add a slider to the auto fee byte feature
- no .conf for the client yet
- have to redo the path settings GUI to go with the .conf addition
- still missing BIP9 rules detection to enable/disable SW
- armoryd is fubar

I'll be away from Friday to Monday, so don't expect me to reply to bug reports until then.

Happy testing!
Pages:
Jump to: