So in summary, We retain the legacy behavior and bump them ALL to 1.7
In the 1.7 development drive (if and when we can) we make an effort to act on patched issues in an attempt to pick the low hanging fruit so to speak... if such a thing exists. best Lewis On Thu, Nov 29, 2012 at 3:56 PM, Julien Nioche < lists.digitalpeb...@gmail.com> wrote: > Good idea! I suspect that most of them will be dating from a looong time > ago and it won't be such a straightforward task to apply them, however this > would be a good way of sorting them > > > >> Additionally, may I suggest (and please shoot me down here if I sound >> cheeky) that we make it a priority in the next development drive, to >> harness the issues which are marked as patch submitted? It seems to be >> a waste for such issues to be stagnating. I am conscious that this >> comment may sound wide of me, this is not the intention, I do think >> however that it would be nice to work our way towards Nucth releases >> in a more strategic manner than we have been doing. Hopefully this >> proposal is a step in the right direction. > > > > > -- > * > *Open Source Solutions for Text Engineering > > http://digitalpebble.blogspot.com/ > http://www.digitalpebble.com > http://twitter.com/digitalpebble > > -- *Lewis*
