[Discuss-gnuradio] Releases planned, merge of 3.7 next branch into maste
From:
Johnathan Corgan
Subject:
[Discuss-gnuradio] Releases planned, merge of 3.7 next branch into master
Date:
Thu, 23 May 2013 20:05:45 -0700
The 3.7 'next' branch is nearing completion, and will be stable enough to merge back into the 'master' branch very soon. I'd like to detail the order that things will happen, so people can prepare.
First, we will tag and release a 3.6.4.2 tarball. This will be the last 3.6.4 maintenance release, and will have all the bugfixes that have occurred since 3.6.4.1 was released two months ago. If you have deployed applications that use 3.6.4 or 3.6.4.1, this will be a low-risk update. Git users will be able to check out the v3.6.4.2 repository tag to update.
Then, we will tag and release a 3.6.5 tarball. This will be the new stable release, and will have both bug fixes and a set of new features using the current 3.6 API, the most significant of which is the new OFDM PHY code. There are no API compatibility breaking changes, so upgrading to this release shouldn't force any changes to your application code, but there may be bugs in the new features. Git users will be able to check out the v3.6.5 repository tag.
Given that the new 3.7 API will require a number of changes to GNU Radio applications for compatibility, we'll be supporting 3.6.5 with bug fixes for awhile, even after 3.7.0 is released.
Finally, we are going to make the major leap and merge the 3.7 next branch back into master, and tag and release a 3.7.0rc0 tarball. For git users, once this happens, unless you take steps to check out the 3.6.5 release tag, you will be using the new API, and your applications will need to be modified accordingly. Most of the required changes are mechanical, involving renaming of classes and functions in C++ or importing modules from different locations in Python. Git users that track the master branch will get this automatically when you pull.
For awhile there will be no 'next' branch, and most of the development effort will be focused on addressing issues that arise from using the new API and stabilizing for the 3.7.0 release.
I anticipate that all the above will happen this weekend, unless our final planned merges and testing indicate that it isn't yet time.
-- Johnathan Corgan Corgan Labs - SDR Training and Development Services http://corganlabs.com