[Dev] Release Candidate Feathercoin 0.9.6 - Check List : final issues
-
Just noting : Build test of 0.9.6 under Ubuntu 16.04 is failing at
In file included from bitcoin.cpp:226:0: bitcoin.moc:11:2: error: #error "This file was generated using the moc from 4.8.7. It" #error "This file was generated using the moc from 4.8.7. It"
I’ve “reinstalled” all the dependencies as in documentation (some mods pushed) :
https://github.com/FeatherCoin/Feathercoin/tree/master-0.9/doc
“PPA” didn’t show up zxing, so build from scratch and installed zxing, Lumenesence checked.
I would seem to be some dependencies change in 16.04, as I’ve been compiling 0.9.3.2 etc previously (Aug).
-
Will build for Ubuntu 16.04 next week with the OBS.
For dependencies you may check this: https://build.opensuse.org/package/view_file/home:wellenreiter01/feathercoin/feathercoin.dsc?expand=1
That is what I use to build the installation packages for Debian and Ubuntu.
Not tested for Ubuntu 16.04 yet -
Comming back to the headline “Final Issues”
We should check the Issue list on Github https://github.com/FeatherCoin/Feathercoin/issues
and try to fix as much as possible before we release 0.9.6
If someone forks to his/her ;) own branch and creates a pull request, please state the issue number solved as part of the request
-
Note 16.04 is failing here as well : https://build.opensuse.org/package/show/home:wellenreiter01/feathercoin
-
Will start to build for Ubuntu 16.04 next week.
It should be possible to solve the problem -
Download 0.9.6 http://www.ftc-c.com/pack4/feathercoin-setup-0.9.6.exe
-
FTC - O.9.6 has not been “officially released”.
I am recommending the official release be 0.9.7, I will start a new thread.
-
To clarify the releases:
- all 0.9.x and 0.11.x branches on Github are developement branches.
- they may have the status ‘release candidate’, which is mentioned in the readme.md file on github then
- the production flag for these releases are set to false
- when a new official release is released:
- The 0.9.x/0.11.x branch is merged/copied to the master branch
- the release flag in the master branch is set to true
- the 0.9.x/0.9.11. x branch is flagged as release in the releases tab on github and the previous production release is marked as ‘old production’ in the readme.md file and the release description in the releases tab on Github.
- the binary files for windows (and mac?) are attached to the new release
- Linux installation packages are build and published on software.opensuse .com.
- finally the new release is announced on forums and social media.
-
Hi,
Should I try to compile it for Windows ? Or it is too early ?
Thanks for all the work !!
-
Wait with the compile until we are ready with the latest bug fixes and changes.
I will give you a shout to start.
-
The fixes are mainly to the build instructions and finish running all the automatic tests.
It’s worth setting up a test build environment, there should be no issues with any of the versions. It’s worthwhile to have test builds on any Linux distro or other OS like BSD as well, where there have been builds in the past.