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

SatSolver yankability #50

Open
perdasilva opened this issue Oct 20, 2022 · 3 comments
Open

SatSolver yankability #50

perdasilva opened this issue Oct 20, 2022 · 3 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Milestone

Comments

@perdasilva
Copy link
Contributor

perdasilva commented Oct 20, 2022

User Story

As a user, I would like to have a choice of (underlying) sat solver, s.t. if the one included in Deppy is insufficient, I can substitute it by something else

Summary / Background

Deppy is a framework for creating/configuring solvers for any purpose. The underlying sat solver should be a pluggable component of the framework

Acceptance Criteria

  • SatSolver package can be yanked to its own repo without side-effects
  • There's sufficient layers of abstraction between the Solver API and the sat solver to make the sat solver pluggable

Scenarios

Assumptions

Links (docs, drawings, designs, etc)

Deppy-as-a-Framework

Dependencies

Definition of Done

  • unit tests
  • integration tests (should be ok to create a mock service directly from the test)
  • extensive godoc (this is a framework after all)
  • reviewed and merged
@github-actions
Copy link

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 20, 2022
@m1kola m1kola modified the milestones: v0.1.0, backlog Oct 4, 2023
@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 5, 2023
Copy link

github-actions bot commented Dec 4, 2023

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 4, 2023
@grokspawn grokspawn added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 9, 2024
Copy link

github-actions bot commented Dec 9, 2024

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
Status: Todo
Development

No branches or pull requests

3 participants