-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Is gulp dead? #1782
Comments
No. Gulp is made up of many small modules. If you look at our github org, much work is being done in other repos. Issues like this are very demoralizing for the people working on the project, please don't open them. |
@nikolay Yeah, shit is happening in a bunch of other projects. gulp is a very thin layer on top of all of these other projects, there's really no reason for us to commit to this project often. Your contributor graph shows you haven't committed anything in over two weeks, does that make you dead too? |
I understand it all but I honestly asked as at this pace, it's not gonna be released anytime soon and issues like #1604 will be v4. |
If I ever write a list of the top 10 most irritating issue titles, this will rank near the top. I would block this user. |
@jonschlinkert Well, you can block me, whatever, but you should better take care of your easy and unsubstantiated irritability first, which could be devastating, and which is near the top of world's evils. |
@nikolay that warning means nothing. You aren't passing user input directly to gulp (or else you really shouldn't be). This thread has gone long enough. I'm locking it. |
Last commit on the v4 branch is more than 2 months old.
The text was updated successfully, but these errors were encountered: