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.

Sign up for GitHub

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

Jump to bottom

Status of the project #42

Closed
shinzui opened this issue Sep 12, 2015 · 2 comments
Closed

Status of the project #42

shinzui opened this issue Sep 12, 2015 · 2 comments

Comments

@shinzui
Copy link

shinzui commented Sep 12, 2015

Hi,

I am trying to adopt either slush or yeoman for our internal microservices templates. I prefer the simplicity of slush but it looks, based on activity, that the project is abandoned. What's your plan for 2.0?

Thank you.
@joakimbeng
Copy link
Member

The project is not abandoned, but I haven't had that much time to invest in this.
One reason for this is that it "just works" ;)
For a 2.0 I want good composability, and better support for local installed generators (the latter needs a workaround at the moment, but I have prepared for solving this for real with the module-finder module). The composability is a harder nut to crack, I haven't figured out a good way for this and I welcome any ideas on the topic!

@shinzui
Copy link
Author

shinzui commented Sep 13, 2015

That's great. I strongly prefer slush over yeoman.

Would it make sense to release slush 2 with just gulp 4 support, and later release a 3.0 with support for good composability and locally installed generators? Decoupling the releases would keep slush current with the latest gulp version.

@shinzui shinzui closed this as completed Sep 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shinzui @joakimbeng