[Pkg-bitcoin-devel] Bug#718272: Bug#718272: backport branches are available

[Luke-Jr]

On Wednesday, September 04, 2013 4:58:58 PM Scott Howard wrote:
> How are those updated? It appears whenever there is a current-version
> micro-release, those commits are backported to the stable branches.

I have a lot of different projects, and tend to cycle through them. Outside of 
that routine, I try to get stable updated and released only after master has 
released a final versions, so as to avoid taking away from testing of those 
release candidates.

> Are only security and network related commits backported?

I've been backporting fixes for bugs that affect the older versions (not 
necessarily only security-related, and also not including some more 
complicated but relatively unimportant fixes that may create new bugs), 
mandatory network changes (only), and translation updates (when possible).

> Is there a stable micro-release when those are backported, or is this
> something that is more of a rolling stable branch.

When there are security fixes or network changes, I bump the version number in 
git. There have been releases in the past, but due to lack of interest I've 
been more inclined to maintain them as a simple rolling branch lately. It's 
simple enough to add tags, however, so I'll probably keep doing that at 
logical commits.