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 represent -- will there
be a GIT branch for the 3.6.5 series, kept separately from the post-next-merged
master? Right now, I'll sent it to check out the 3.6.5 tag. Given that many
projects out there do not yet support the 3.7 API (e.g., gr-osmosdr, which I
just checked tonight), I'd like to keep the next port on the 3.7 API, which is
now the GIT master. I think this division makes sense, and is less confusing
to end-users from a MacPorts perspective (release is release, devel is for
bug-fixes on the release, and next is for the next API purposes -- the bleeding
edge as it were). Thoughts? - MLD
On May 23, 2013, at 11:05 PM, Johnathan Corgan <johnat...@corganlabs.com> wrote:
> 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. [snip] 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. [snip] 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.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
