Yes, this is exactly what I needed; thanks! - MLD
On May 27, 2013, at 10:09 PM, Johnathan Corgan wrote:
> "release" -> v3.6.5
> "devel" -> maint branch
> "next" -> master branch
>
> It will be a few weeks at least before we're ready to call 3.7.0 stable; in
> the interim, 3.6.5 is the stable re
On Mon, May 27, 2013 at 6:59 PM, Michael Dickens wrote:
> I'm looking at these changes and trying to come up with a good way to
> integrate them into the MacPorts gnuradio {release, devel, next} ports.
> Updating the release to 3.6.5 seems like a good idea. I'd prefer to keep
> the devel port
I'm looking at these changes and trying to come up with a good way to integrate
them into the MacPorts gnuradio {release, devel, next} ports. Updating the
release to 3.6.5 seems like a good idea. I'd prefer to keep the devel port on
3.6.5 + bug fixes, since that's what it is supposed to repres
And don't forget that we have a wiki page designed to help us
transition from the 3.6 API to 3.7:
http://gnuradio.org/redmine/projects/gnuradio/wiki/Move_3-6_to_3-7
The page is not complete, though we are doing our best, so please help
us by adding and editing text on here as you find it or as th
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,
