On Tue, Jan 28, 2014 at 06:20:12AM -0500, Karl Dahlke wrote: > Yes I think it would be easier if all this was moved into master, > if Adam then had permission to push into masster, as I do, > if that's ok with you chris, and it's ok with me of course.
Ok, looks like I've been added. I guess it's ok if I start pushing changes? > A piece of my brain thinks there should be some backward compatibility, > like a flag to makefile to build the old way against 185, > for those who don't have 24 yet, > but then a larger piece of my brain thinks about the linux kernel, > where they really discourage that sort of thing. > Youre just expected to keep up! > Linux has a means of conditional compilation > #if version <= 3.2.7 > That kind of thing, but I tell you, you hardly ever see it in the kernel code, > because if you ever started your code would be full of #if versions > maybe all the way back to 2.4, and impossible to read, > so they just tell you generically not to do it. > So I have come to understand the practical point of view of > marching forward, and if you want the latest of this you better get > the latest of that. Yeah, I think in this case the changes are too large to sustain any sort of backward compatibility and it'd just make debugging that bit harder. > Anyways I digress; I think master would be fine, > the only thing we really have to stop nad pause and well test is the threshold > of version 3.4.11. > I think we all have to say yea before we do that. Yes, definitely. There're a few bugs I know about and think need squashing before 3.4.11 happens, but the list is thankfully shrinking slowly. Do we have some form of issue tracker which works with edbrowse (I'm not sure how edbrowse-friendly the github setup is)? On the subject of 3.4.11, apart from the js lib change and other bug fixes, are there any other features or major changes we want to make before it happens, or do we want to get out the js update and then start pushing features etc in the next release? Cheers, Adam. _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
