Hey everyone, Nathan and I have been going through the branches, to work out which to keep, which ones we can merge, which ones we can turn into issues, and which to delete. Here is the current list I have compiled:
• ❎ build_system
@cgogolin: Branches off projectQ_plugin
. Simply adds a makefile. To delete.
• ❎ parameter_pass_on
@cgogolin: branches off projectQ_plugin
. A proposal to check for whether a plugin requires credentials. small, likely be deleted and turned into an issue.
• 📥 new_intro
@co9olguy: branches off master
. Can be merged back into master - essentially the latest version of master.
• ❎ projectQ_plugin
@cgogolin: branches off master. Based on Ville's old interface, recommend to delete, if the new interface version is feature complete, thoughts?
• ✔️ new_user_interface_with_projectQ_plugin
@cgogolin: branches off projectQ_plugin
, with a merge from new_user_interface
.
The current ProjectQ plugin branch, should be spun off into it's own repo, with it's own issue tracker.
• ❎ new_user_interface_suggested_minor_improvements
@cgogolin: branches off new_user_interface
. I've already manually merged this into new_user_interface
. Can be deleted.
• ❎ new_user_interface_pseudo_code_exampple_christian
@cgogolin: branches off new_user_interface
, simply contains an additional user interface example. Can be deleted, potentially turned into an issue if needed.
• 📥 cv_gradients
@smite: branches off master
, just prior to new_intro
. Contains Ville's work on implementing CV gradients. Should be eventually merged/archived, and Ville should move his new code to the branch containing the new user interface.
• ❎ ui_update
@smite: branches off cv_gradients
. Implements a modified user interface, by modifying Ville's original interface. Inspired by the new user interface (i.e. plugin
becomes device
, must define a quantum function with a return
statement, explicitly create QNode
, evaluate it via QNode.evaluate()
.). Can be moved to a github issue?
• ✔️ new_user_interface
@josh146: branches off new_intro
, but essentially is a massive refactor, and cannot be easily merged back.
Does anyone have any thoughts/comments on the above list?