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

-next? #99

Open
dcsan opened this issue Jun 23, 2015 · 7 comments
Open

-next? #99

dcsan opened this issue Jun 23, 2015 · 7 comments

Comments

@dcsan
Copy link
Contributor

dcsan commented Jun 23, 2015

is this the repo for the old version? I'm confused, crowducate-next points back here, but then it says

The current version only works with Meteor 0.83

is it still stuck in dev limbo?

@Rahbaran
Copy link
Member

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.

@dcsan
Copy link
Contributor Author

dcsan commented Jun 23, 2015

do does the new branch work?

you might wanna update the README then to make it clear how to get started

@Rahbaran
Copy link
Member

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 :)

@dcsan
Copy link
Contributor Author

dcsan commented Jun 24, 2015

i guess i could follow those instructions, but its so confusing and counter intuitive it would put me off trying. why not just git clone and then run? why mash two different versions of meteor into one repo?

@dcsan
Copy link
Contributor Author

dcsan commented Jun 24, 2015

closing because i guess you have your reasons that are non-technical.

@dcsan dcsan closed this as completed Jun 24, 2015
@Rahbaran Rahbaran reopened this Jun 24, 2015
@Rahbaran
Copy link
Member

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.

@brylie
Copy link
Member

brylie commented Jun 24, 2015

I created a 1.0.0-a1 release for people to download and test.

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

3 participants