-
-
Notifications
You must be signed in to change notification settings - Fork 178
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
SlimeVR 1.0 Release #577
Comments
Can just say "Support OSCQuery for VRChat" |
I think these issues should also be included in 1.0 or clarified/updated to fit it: |
Eiren mentioned in #75 that its actually not necessary for 1.0, so I've updated the issue to clarify. |
Descoped OSCQuery due to conversations in #580 |
is there a tracking issue for having the tracker handling more than one server in the network? |
#622 is required for 1.0. |
We have so much that is blocking 1.0 ;( |
This is not how it works.1.0 is not a feature that we all wait when it can be implemented to be blocked. We work forward and we will get there eventually. |
IK, was making an observation that there is a lot that should be done before reviewers have this in hand. At the current pace of things, it seems unrealistic to assume everything on this list will happen before reviewers review. |
I love how this has nothing that we actually need for 1.0 or have done for 1.0 😢 |
at the time we made it, this is what people felt was necessary, so... All of these still look very important to me, except maybe the overlay stuff. |
This is a tracking issue for us to discuss and track updates on features, bugs, and UX that we want in a SlimeVR 1.0 release. Our goal of this release is to have the software "shippable". We would be confident that we did everything we needed for reviewers and users to be happy, especially by nontechnical users.
Issues remaining for 1.0:
Not needed for for 1.0:
Descoped due to blockers:
The text was updated successfully, but these errors were encountered: