Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code refactoring: extract common parts from backends #39

Open
canasdiaz opened this issue Feb 20, 2013 · 4 comments
Open

Code refactoring: extract common parts from backends #39

canasdiaz opened this issue Feb 20, 2013 · 4 comments
Milestone

Comments

@canasdiaz
Copy link
Member

@sduenas suggested to improve the way backends are written. The idea of this enhancement is to study what the common parts are and move them to the shared code/objects.

@brainwane
Copy link
Contributor

I've started working on this. It'll be in a branch in my fork. I aim to have something worth reviewing this week, even if it's just a small advance on the current situation.

@brainwane
Copy link
Contributor

Sorry, this turned out to be more difficult than I thought, so I think I will aim on just fixing functionality bugs for now.

@canasdiaz
Copy link
Member Author

Don't worry @brainwane ;)

@brainwane
Copy link
Contributor

For future reference: right now, the Bugzilla, GitHub, Jira, and Launchpad backends use the Backend class (e.g., class LPBackend(Backend)); Allura, Gerrit, Google Code, Redmine, and Sourceforge backends don't (e.g., class Allura()).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants