# Close to tagging and releasing 3.5.3, merging next branch

**URL:** <https://www.ruby-forum.com/t/close-to-tagging-and-releasing-3-5-3-merging-next-branch/218616>\
**Category:** GNU Radio\
**Created:** [April 5, 2012, 10:53pm UTC](https://www.ruby-forum.com/t/close-to-tagging-and-releasing-3-5-3-merging-next-branch/218616 "2012-04-05T22:53:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [April 5, 2012, 10:53pm UTC](https://www.ruby-forum.com/t/close-to-tagging-and-releasing-3-5-3-merging-next-branch/218616/1 "2012-04-05T22:53:24Z")

</div>

At this point, the master branch of the repository is ready for  
tagging and releasing as 3.5.3, which is the last planned release of  
the 3.5.x series. It will have a maint branch, so there is a  
possibility of a 3.5.3.x bug fix release, but no plans for a 3.5.4  
with new features.

If there are minor patches or bugfixes you’ve been holding on to, now  
is the time to submit them.

Shortly after tagging 3.5.3, we’ll be merging the next branch back  
into master, which will switch the master branch to 3.6.x.

The 3.6 API hasn’t changed that much from 3.5, but some important  
structural changes have occurred that may create problems for people  
who routinely pull from master:

- The autotools build system has been removed, and CMake has become  
the official build system. Build scripts will need to be adjusted to  
account for this.

- All scripts that get installed into $PATH have had their file  
extensions stripped. So for example, scripts that call  
uhd\_rx\_cfile.py will need to be changed to call uhd\_rx\_cfile without  
the extension.

There will be more documented about actual feature changes in 3.6 on the  
wiki.

Johnathan

---

<div class="post-metadata">

**Author:** ![jconley](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/90ced4/32.png) [@jconley](https://www.ruby-forum.com/u/jconley)\
**Post date:** [April 7, 2012, 2:07am UTC](https://www.ruby-forum.com/t/close-to-tagging-and-releasing-3-5-3-merging-next-branch/218616/2 "2012-04-07T02:07:03Z")

</div>

On Thu, 5 Apr 2012 13:51:42 -0700  
Johnathan C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> At this point, the master branch of the repository is ready for  
> tagging and releasing as 3.5.3, which is the last planned release of  
> the 3.5.x series. It will have a maint branch, so there is a  
> possibility of a 3.5.3.x bug fix release, but no plans for a 3.5.4  
> with new features.

Johnathan, I wrote a signal source block for Matlab files. It needs more  
testing, and is only for .mat level 4 files. Is there interest in  
adding this now, or is there a preference to leave it for 3.6?

John

---

<div class="post-metadata">

**Author:** ![jconley](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/90ced4/32.png) [@jconley](https://www.ruby-forum.com/u/jconley)\
**Post date:** [April 7, 2012, 2:13am UTC](https://www.ruby-forum.com/t/close-to-tagging-and-releasing-3-5-3-merging-next-branch/218616/3 "2012-04-07T02:13:52Z")

</div>

On Fri, Apr 6, 2012 at 17:05, John C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Johnathan, I wrote a signal source block for Matlab files. It needs more  
> testing, and is only for .mat level 4 files. Is there interest in  
> adding this now, or is there a preference to leave it for 3.6?

Let’s get it into the master branch after the 3.6 merge, which should  
be tomorrow sometime. We don’t expect it it take too long to clean up  
master for a 3.6.0 release, so it would probably end up being part of  
that.

Johnathan