[platform-debug-dev] Re: [jdt-debug-dev] Build contribution process

["Darin Wright/WPG/OTI" <Darin_Wright@xxxxxxx>]

I agree with this proposal in theory, but in practice, there is a problem....

Currently, the "java debug ui" plug-in is at the top of the food chain. That is, "org.eclipse.jdt.debug.ui" requires the "org.eclipse.jdt.ui" plug-in. Not only that, it accesses non-public API in the Java UI plug-in (which we are aware of, and are working to clean up). Since we rely on non-public API, the "Java debug UI" plugin is relying on a "moving target". If we were only to submit the last know stable version of the "Java debug UI", it could easily be incompatible (have compilation errors), with the "org.eclipse.jdt.ui" plug-in that is submitted for an integration build.

Darin

jared_burns@xxxxxxx Sent by: jdt-debug-dev-admin@xxxxxxxxxxx 11/28/2001 09:40 AM Please respond to jdt-debug-dev

To:        platform-debug-dev@xxxxxxxxxxx, jdt-debug-dev@xxxxxxxxxxx         cc:                 Subject:        [jdt-debug-dev] Build contribution process

In the interest of improving the quality of the debugger build contributions, I propose the following: 

1. Every morning we version off our code, build the latest plugins, and distribute them to be used in our host. 
2. At the end of every day (or earlier) we declare the latest plugins stable or instable, based on both our experience using the plugins and the results of testing scenarios (smoke tests?). 
3. Each Tuesday we pick the most recent stable daily version and copy it from the HEAD stream to the STABLE stream. We submit this version from the STABLE stream. 
4. Any bugs that are reported in our submission to the Tuesday build are fixed in the STABLE stream. Note: the STABLE stream always consists of either the Tuesday submission or the Tuesday submission plus fixes (not feature additions or refactorings) to the Tuesday submission. 
5. On Thursday we submit the latest version of the STABLE stream, which consists of the Tuesday submission plus any fixes we made to that version. 
6. HEAD stream development continues at all times at our current pace. 

- Jared