Community
Participate
Working Groups
I propose to provide a sandbox repository that shall be used to create every new plugins for Papyrus. The idea is that a new plugin is developped in the sandbox, and once ready, it is proposed to other commiters. This laters then check the plugin, and after a short delay say go/nogo to move the plugin in the head. This process have severals advantages: - clearly separate 'stable' plugins from the one that are in developements - give other commiters a chance to test, check and comment new plugin before it is fully part of Papyrus. This will allow to choose altogether the definitive plugin name, its target repository (core, uml, ...) and to check that coding rules are respected. - this should lead to more robust and well written plugins - maybe simplify the nightly build process - ... Please comment the idea ... The process of creating or adding a new plugin to Papyrus will be the following: - create/add the plugin(s) in the sandbox repository - develop and test the plugin - when you are happy with your new plugin, says it to other commiters and ask to be able -- commiters can test it, check the names, the code
(In reply to comment #0) > I propose to provide a sandbox repository that shall be used to create every > new plugins for Papyrus. > The idea is that a new plugin is developped in the sandbox, and once ready, it > is proposed to other commiters. This laters then check the plugin, and after a > short delay say go/nogo to move the plugin in the head. > > This process have severals advantages: > - clearly separate 'stable' plugins from the one that are in developements > - give other commiters a chance to test, check and comment new plugin before it > is fully part of Papyrus. This will > allow to choose altogether the definitive plugin name, its target repository > (core, uml, ...) and to check that coding rules are respected. > - this should lead to more robust and well written plugins > - maybe simplify the nightly build process > - ... > > Please comment the idea ... > > > > > The process of creating or adding a new plugin to Papyrus will be the > following: > - create/add the plugin(s) in the sandbox repository > - develop and test the plugin > - when you are happy with your new plugin, says it to other commiters and ask > to be able > -- commiters can test it, check the names, the code +1 for this process, this would ensure better naming of projects, and stability in the build process. Rémi
Ok, we will create such repository. We need to find a more appropriate name. Proposals: - incoming - entrylock - entrygate - waitinggate - sandbox - incubation
The repository 'incoming' is created in branches and trunk. New plugin proposal should use these repository. New plugin proposal submition process is explain in the wiki: http://wiki.eclipse.org/Papyrus_New_Plugin_Submition_Process
The review process should be fast to avoid blocking development of dependent modifications, especially for small plugins. We have to be careful when moving the plugin from incoming to its final folder to avoid the loss of the SVN history. I think we should also think about a git branch based process, but I think the git eclipse plugin is not enough stable/feature complete yet.
Closed
