-
Notifications
You must be signed in to change notification settings - Fork 74
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
-next? #99
Comments
the master branch is (still) the old version: we migrated -next to -platform/develop. so use the develop branch from this repo. the feature branches are also branches from the new -platform/develop branch. the -next-repo is obslete now. sorry for the confusion. we're working on it. |
do does the new branch work? you might wanna update the README then to make it clear how to get started |
Just clone the development branch from THIS repo and run meteor - all good. The /features branches should also work. I updated the README. If it's ok, feel free to close the issue. Otherwise, let me know if you there are any questions. Of course, you can also edit the README if you like :) |
i guess i could follow those instructions, but its so confusing and counter intuitive it would put me off trying. why not just |
closing because i guess you have your reasons that are non-technical. |
Main reason was that for most people the master branch was a bit hard to understand + difficult to port from 0.8 to 1.0. So the code was written from scratch. However, the confusion is only temporary. For the moment: run meteor on the development branch. That's it. |
I created a 1.0.0-a1 release for people to download and test. |
is this the repo for the old version? I'm confused, crowducate-next points back here, but then it says
is it still stuck in dev limbo?
The text was updated successfully, but these errors were encountered: