Release3.0.0

{{{ #!html }}}

= Release 3.0.0 (Alluring Albatross) =

== Motions ==

Motion 1: release date 5/31/2011. Accepted

Motion 2: the next release number shall be CSS-Core 3.0.0. Accepted

Motion 3: there should be a cute name to indicate the release, like other projects do (like Ubuntu Gutsy Gibbon, …). Accepted

Motion 4: “Alluring Albatross” for first release. Accepted

Motion 4.5: The next release name is picked by DESY, the following by SNS. Accepted

Motion 5: the main theme should be modularization. Accepted

Motion 6: create new features for "core" and "core-utils" so that it’s more clear what they are. Accepted

Motion 7: create org.csstudio.platform.core.feature that will contain all plugins that everybody requires (one site not wanting it makes it not part of this feature). Accepted

Motion 8: create org.csstudio.platform.util.feature that will contain all plugins that anybody believe should be part of core (one site wanting it makes part of this, the maintainer has to agree to give support and keep the interfaces somewhat stable). Each site will include any number of these plug-ins. The feature is there so that once a plug-in is part of the feature the build will pick it up. Accepted

Motion 9: org.csstudio.logging plugin. Accepted

--> Add motions for Kays proposals

Motion 10: org.csstudio.java: Basic Java utilities for strings, files, ... Accepted

Motion 11: org.csstudio.ui: Utilities for SWT/JFace/Draw2D to create Dialogs, ... Accepted

Motion 11.5: org.csstudio.csdata.ui for ui elements that depend on the data structures. Accepted

Motion 12: workspace: Workbench, workspace tools. Accepted

Motion 13: org.csstudio.platform.auth: Authentication/Authorization. Accepted

Motion 14: org.csstudio.platform.csdata: Control system data types (PV name, time, alarm, values). Accepted

Motion 15: remote control as separate plug-in. Accepted

Motion 16: org.csstudio.statistics as separate plug-in. Accepted

Motion 17: org.csstudio.platform.dal as separate plug-in. Accepted

Motion 18: utility.pv as a core plug-in. Accepted

Motion 18.5: IValue as now used by utility.pv and archive code as a separate plugin. Accepted

Motion 19: PVManager as a core plug-in. Accepted

Motion 20: the org.csstudio.platform will remain. As pieces are taken out, platform will depend on these pieces. Accepted

Motion 20.5: To make it more obvious what 'remains' and what has been re-designed, stop using 'platform' for the new plugins. Accepted

Motion 20.6: Don't put anything in the plugin name that determines whether it's core or core-utils, given that plugins may change status. Accepted

Motion 21: we should have a cs-studio-stable-branch which contains only released plug-ins, at least for core. Any pushed plug-in there should increase the release number of the plug-in. Accepted

Motion 22: create a script that crawls the repository and creates an HTML page with the plug-in maintainers and pushes it on sourceforge. Accepted

Motion 22.5: Each plugin source contains an INFO file with brief information that's also included in the HTML page, so it can be a table of Pluging Name, Maintainers, Info. Rejected

Motion 22.6: Use Bundle-Description for the info field. This way we parse one thing, it's actually distributed and recognized by OSGi. Eclipse does not have a field in the UI editing for this, but if you put "Bundle-Description" in the MANIFEST.MF it's recognized. Accepted

Motion 23: investigate how to include/run the unit tests as part of the build (BNL/DESY both proposed something similar). Accepted

Motion 23.5: Move test code in fragments (e.g. plugin org.csstudio.pvmanager and fragment org.csstudio.pvmanager.test). We get rid of test code and the mock-libs in CSS products. Accepted