Hi, I would like to thank everybody for testing rc1, we received some very valuable input and I think this weekend would be the right time to do rc2.
My plan so far: Starting tomorrow's morning merge all of http://openocd.zylin.com/#/q/status:open+label:Code-Review%253D2,n,z . I'm having doubts about http://openocd.zylin.com/1562 (is it appropriate this late in the release cycle?) and either Seth or somebody else would need to push http://openocd.zylin.com/2064 rebased on current code to pass verification. If the latter is not going to be merged, I'd like to have http://openocd.zylin.com/#/c/2083/ (but I'd amend the comment to mention 2064 and then 2064 would just need to remove it). Also, need to be decided on and most probably merged: http://openocd.zylin.com/#/c/2100/ http://openocd.zylin.com/#/c/2088/ and its deps http://openocd.zylin.com/#/c/2101/ http://openocd.zylin.com/#/c/2081/ probably http://openocd.zylin.com/#/c/2099/ If everything goes well, tomorrow afternoon rc2 will be tagged and uploaded. If you have something to add, please say it now :) Have fun, and happy hacking. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected]
pgpV3FiKtCEWP.pgp
Description: PGP signature
------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
