There was a discussion on whether to put all the fuel plugins into the single repository or have them separate. The problems with all the fuel plugins in single repository are following:
- it is impossible to make a branch on a single plugin, branch is applied to the whole repository and all the plugins - plugins may have different release cycles, we will get lots of unnecessary merges/rebases - rebasing can be a pain. If I have a branch, I have to rebase when some other plugins change - there should be someone who manage merging to master, the person who "owns" all the plugins Having all the plugins in single repository will cause interference. if I do some plugin, I have to consider what developers of other plugins do. Anton On Tue, Jan 6, 2015 at 7:00 PM, <samuel.bar...@orange.com> wrote: > Hello, > > > > Actually there is two different fuel plugins git repositories. One in > stackforge and the other in mirantis: > > https://github.com/stackforge/fuel-plugins > > https://github.com/Mirantis/fuel-plugins > > > > it is a little bit confusing. Why needing two different repositories? > > > > which one should be used in order to: > > -add new plugin > > -update/correct exisiting one (for example adding 7-mode and e-series > support to cinder netapp plugin according to > https://bugs.launchpad.net/fuel/+bug/1405186) > > How are going to be manage version? There is a stable/6.0 branch from > stackforge repo but not mirantis one > > > > Regards, > > > > Samuel Bartel > > Orange > > > > > > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
