Re: Why are old changes from master not in the release branches?

2018-01-12 Thread Andreas Schildbach
Master is ongoing development, currently heading towards 0.15. The current release (0.14) is on release-0.14. Generally I only backport bugfixes and security issues. The tx v2 support should be quite easily backportable, but also we could work towards releasing 0.15 sooner (maybe move SegWit to

Re: Why are old changes from master not in the release branches?

2018-01-09 Thread Manfred Karrer
Another question: Is the master branch tested sufficiently to be considered safe or it is a pure dev branch where more profound testing is done only in releases? Am Dienstag, 9. Januar 2018 14:58:00 UTC+1 schrieb Manfred Karrer: > > I wanted to merge the v2 tx support changes to our fork based

Why are old changes from master not in the release branches?

2018-01-09 Thread Manfred Karrer
I wanted to merge the v2 tx support changes to our fork based on release 0.14.4 but I see that there are many old trivial changes like "Add a generic copyright statement" (https://github.com/bitcoinj/bitcoinj/commit/3773a4343c53634f3bc8ab24eff16ecb31109aa6) or "use generic type"