Getting to 3.2 release
27 Nov
2016
27 Nov
'16
5:38 p.m.
My current thoughts have been to merge the obsolete function warnings and bad system name merge requests and then release 3.2. But perhaps this is a bridge too far. I'd be interested in opinions for and against bundling up the current version as 3.2, and moving on to 3.2.x and 3.3 release candidates. Also, separately, I'd be interested in more discussion of how changes to the image and program operations will affect others. I tend to lose track of these, since I don't use them myself. Thanks, r
2992
Age (days ago)
2992
Last active (days ago)
0 comments
1 participants
participants (1)
-
Robert Goldman