There certainly is a lot of content. I'll give it serious consideration.
In the mean time, anyone who wants reliable access to the latest build I just ran this aft can get it from:
Doug.
Based on the commit log, the following bugs were committed following the SR2 release. Since we need a number of those fixes in a coming release it would be very helpful for us to have an 8.0.3 release.
On 09/03/2012 12:21 PM, Doug Schaefer wrote:
That is a good question. There are a couple of fixes that I put in supporting our BB NDK users. And there's probably one more I want to put in to decouple the project references from the CDT build config references. But we also want to look at moving to
8.1/Juno.
If there is enough interest, we could cut an 8.0.3.There's a bit of work to that so I'll wait to hear from more people. I still have 8.1.1 to get going.
BTW, watching the commits there are a lot of change in the 7.0 branch as well since we released. It's just how we've always operated. The hope is that these are all bug fixes and don't change things too dramatically.
Hi all,
A number of fixes have been made in the CDT-8.0.x Stream after 8.0.2 , and builds are available from Hudson :
http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/log/?h=cdt_8_0
https://hudson.eclipse.org/hudson/job/cdt-legacy/
But with those fixes sitting in Hudson and git only, they are practically not accessible to end users.
Which means that commercial vendors who need those fixes deployed have to deploy by themselves… creating a risk of fragmentation and incompatibilities.
I would thus like to propose releasing an official CDT-8.0.3 some time soon.
Fixes to include and timing could be voted on by committers.
What do you think ?
Thanks,
Martin
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/cdt-dev