-
Notifications
You must be signed in to change notification settings - Fork 96
Release3.1.0
This is the list of proposed plugins for core. The Maintainer is the person responsible for making a plan for the release, organize the different contributions and will be the one that decides when the plugin is ready for release (no new features from that point, stable enough). Reviewer should be some other person that validates the plugin (it works for him too, the API is not useless and not intelligible). Contributors are people that believe have elements to be included in that plug-in, want to take care of some aspect or simply want to "help" (up to the maintainer to do the coordination).
||Plugin name || Info || Status || Maintainer||Reviewer(s)|| Contributors || ||org.csstudio.core.feature || Keep track of core plugins || || Release manager (Jan for 3.1.0)|| One for each site || || ||org.csstudio.core.util.feature || Keep track of core-util plugins || || Release manager (Jan for 3.1.0)|| One for each site || || ||org.csstudio.auth || || || || || || ||org.csstudio.csdata || || || || || || ||org.csstudio.csdata.ui || || || || || || ||org.csstudio.dal || || || || || || ||org.csstudio.data || || || || || || ||org.csstudio.java || || || || || || ||org.csstudio.logging || || || || || || ||org.csstudio.ui.menu || || || || || || ||org.csstudio.ui.util || || || || || || ||org.csstudio.remote || || || || || || ||org.csstudio.statistics || || || || || || ||org.csstudio.startup || || || || || || ||org.csstudio.utility.pv || || || || || || ||org.csstudio.utility.pvmanager || || || || || || ||org.csstudio.workspace || || || || || ||
Motion 1: Release date is 1/31/2012 (Feature freeze 12/31/2011)
Motion 2: Release name is ?
Motion 3: Update CSS target platform to Eclipse 3.7
Motion 4: Create a single "Epics 3 support" feature that enables epics for all data providers (DAL, utility.pv, PVManager). Given the multiple providers, that the user should not be aware of which ones each application uses, and the limitation of the eclipse plug-in system, we propose that the features install all plugins for all data providers, even if not installed. At runtime, the unused plugins would not be activated.
Motion 5: Incorporation of unit testing into the headless build process
Motion 6: PVManager Interface to write data (right now, limited to monitors)
Motion 7: Debug plugin for PVManager to see the status of data source connections.
Motion 8: Transition from utility.pv to PVManager.
Motion 9: Review main page so that it formats properly (currently main part may go below side menu).
Motion 10: Review help system
Motion 11: Investigate a better way to handle external library dependencies.
Motion 12: Standardize on features - review features to make them as much as possible usable out of the box by a product developer and by a user with a generic Eclipse RCP platform.
Motion 13: Check/Update org.csstudio.utility.product from SNS and KEK to share it between other sites.
Motion 14: org.csstudio.statistics as separate plug-in.
Motion 15: Refactoring/Renaming of dal plug-in.
Motion 16: Update and test remote management and remote update with target platform Eclipse 3.7.
Motion 17: Create new GUI for remote management in CSS and remove CSS dependencies from remoteRCP.