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

Re-release v1.2 as a pre-release or beta #14

Closed
crcastle opened this issue Mar 30, 2015 · 3 comments
Closed

Re-release v1.2 as a pre-release or beta #14

crcastle opened this issue Mar 30, 2015 · 3 comments

Comments

@crcastle
Copy link

@abyssoft, I commend you open sourcing the code for teleport, but may I suggest that you "re-release" v1.2 as a pre-release or beta on the teleport website? It is really a huge change from the previously stable and great versions you've released in the past. I and many other users have struggled to get the new version working properly. If you care about teleport continuing to be used and loved by so many people, it's important to be transparent and upfront about the state of releases. v1.2 is not a stable release:

  1. Huge amount of reported issues with v1.2 in teleport forums.
  2. Many issues reported here in github issues
  3. Your statement that you "didn't have much time to test it"
  4. And tweets: 1, 2 (more detail)

Again, it's awesome that you've open sourced this! I'm sure there are many people excited to help out with it, but rushing a release only creates frustrated users.

EDIT: added tweets
EDIT: moved comment to its own thread from issue #10

@tjd2002
Copy link

tjd2002 commented Mar 30, 2015

I agree that 1.2 is pretty clearly in the 'beta' category and should be labeled as such. A download link to 1.1.3 on the Teleport site for users of ML/Mavericks would be helpful too.

But 1.1.3 is also not usable out of the box with Yosemite, so I don't think you can call that one the 'stable release'. (I was not able to get 1.1.3 working well at all under Yosemite, even after using this workaround, but 1.2 is working well for me--for now.)

I think that filing high-quality bug reports against 1.2 is the best way forward. That will allow Jul (or any other developer who wants to contribute or fork the repo) to use their time effectively.

@kwolk
Copy link

kwolk commented Apr 2, 2015

Yea, and it doesn't work on Lion like the release notes say it does.

@atljeremy
Copy link
Contributor

+1 to all of this

@abyssoft abyssoft closed this as completed Mar 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants