Hi!

So - WE'RE DOING A RELEASE! (;

My plan aims to provide a release year after the previous version, so we 
can expect 0.6.0 to be tagged around 10th of August (assuming no major 
problem will be found).

A rough schedule (for information and for acceptance):
- till ~10th of July - merging last patches
- ~10th of July - merge window closes, first RC is tagged
- from ~10th of July to ~25th of July - testing first RC, merging fixes
- ~25th of July - second RC (if required)
- from ~25th of July to ~10th of August - testing second RC, only 
critical fixes or improvements to non-code portions (docs, NEWS, etc.)
- ~10th of August - tagging 0.6.0 release, opening of merge window

If no issues would be found&fixed in the first RC phase, the second RC 
phase would be skipped, extending the first one to a month.

Any objections?

Now - second part of this message - what are the things we intend to 
merge for the 0.6.0? I think MPSSE is mostly ready, but it would need 
some mention in the docs and NEWS (possibly indicating it's experimental 
for now). Any other major stuff in the queue? Post your proposals in 
reply so we could focus on them.

Anything I forgot about?

4\/3!!

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to