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

Beta Release #23

Open
8 of 16 tasks
Und3rf10w opened this issue Feb 14, 2018 · 4 comments
Open
8 of 16 tasks

Beta Release #23

Und3rf10w opened this issue Feb 14, 2018 · 4 comments
Assignees
Labels
NEW_VERSION Issues that act as a milestone documentation hub for a planned new version of the project
Milestone

Comments

@Und3rf10w
Copy link
Owner

Und3rf10w commented Feb 14, 2018

Code in the master branch is considered tested and stable. Once all of the changes that need to be done for the beta release are complete, then we can push them into the master branch.

Tasks

The following tasks must be completed before the codebase can be considered ready for beta release:

  • Create pull request to implement all new features from the beta_stable branch to the dev branch.
  • Merge beta_stable into dev. (Blocked by all tasks below)
  • Merge dev into master

Server

  • Fix Add support for multiple clients #14 - implement support to handle multiple clients
  • Create and fix an issue to refactor and abstract the server Not needed
  • NOTSURE: Implement the ability to support different transports across different clients Not going to be a goal for beta release

Client

Transport

Base Logic

  • NOTSURE: Refactor the framework server interface so that we can support the management of multiple frameworks with a framework_manager. This may be out of scope for the beta release.

Documentation

Builder

@Und3rf10w Und3rf10w added the NEW_VERSION Issues that act as a milestone documentation hub for a planned new version of the project label Feb 14, 2018
@Und3rf10w Und3rf10w added this to the Beta Release milestone Feb 14, 2018
@Und3rf10w Und3rf10w self-assigned this Feb 14, 2018
@Und3rf10w
Copy link
Owner Author

Pushing anticipated release date to end of May 2018. Life happens unfortunately 😞

@Und3rf10w
Copy link
Owner Author

I'm gonna go ahead and close this as a wontfix for now. Please reference #26 for additional details.

@Und3rf10w
Copy link
Owner Author

Reopening. I'm gonna continue with the existing codebase for now and reconsider a rewrite for a later date.

@Und3rf10w
Copy link
Owner Author

Should probably consider whether or not we want to move towards a saner, more standardized style, as described here, as a target for this release.

This SHOULDN'T be terribly difficult, especially with something like PyCharm, but would be nice to have. This could also be done after beta, but we'll see.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NEW_VERSION Issues that act as a milestone documentation hub for a planned new version of the project
Projects
None yet
Development

No branches or pull requests

1 participant