I think this is a good idea anyway, since the "undoing bunch of commits" message was to restore iBOB + BEE2. So I think it's natural to have a branch in the library.
On Tue, Feb 12, 2013 at 2:35 PM, Jason Manley <jasonman...@gmail.com> wrote: > Sorry Dave! The updates all happened when we updated all the tutorials for > our recent workshop. There should have been more consultation. > > If 14.x is breaking backwards compatibly, maybe we should freeze mlib_devel > as mlib_11.x as we did with the old v7.1 blocks when we moved to 11.x. It > would then be up to 11.x users to backport/cherry-pick from the development > branch. > > I'm afraid we don't have the capacity to maintain multiple versions and > SKA-SA's firmly on the 14.x + 2012b flow. > > Jason > > > > On 12 Feb 2013, at 21:12, David MacMahon wrote: > >> What's going on with recent mlib_devel pushes to casper-astro? Why so much >> activity from our South African friends there instead of in the ska-sa >> repository? Why the lack of any discussion (e.g. on this list) about this? >> >> I fetched from casper-astro on January 24th and got commit 9940104, but now >> I see that 18 cherry picked commits and an "Undoing bunch of commits" >> commit have been pushed to casper-astro since then. It's really hard to >> tell what's going on there. >> >> I dislike commit 2df7b03 (cherry picked from f22a98c) that puts 14.2 into >> system.xmp for the sole purpose of avoiding a "rev-up" when building. That >> may save 14.2 users a few seconds off their hours long build, but it forces >> every ROACH2 user to upgrade to 14.2. Do we really want to mandate that >> users get 14.2 if they want to do ROACH2 development? Not everyone gets >> donations and/or free upgrades of the toolflow software. >> >> Thanks, >> Dave >> >> > >
