-
Notifications
You must be signed in to change notification settings - Fork 111
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
Keep this alive? #22
Comments
3b65832 and just tagged 1.10.4. I agree with you ! I'm not doing much web anymore so I'm not really keeping up with updates, but I'll try to check more often. (another option is adding people to the components repo) |
Okay, thanks for the update. We can notify you via issues or PRs when we release a new version. For sending PRs, could you briefly document what you do to provide new versions? |
issues would be good, no need for more. I don't build from your repo usually, I just download the whole source zip (and take |
This is not a code issue, just a way to contact the authors of this repo. I'm on the jQuery UI team and we've been discussing bower support recently. Due to various limitations of bower itself, we currently think the best approach for bower users is to keep this separate repo up-to-date, providing both individual and compiled files (for example,
ui/jquery-ui.js
). Are you okay with that? We'd be happy to keep things as-is.If you wonder what limitations I'm talking about: It mostly comes down to the lack of publishing files, comparable to how npm handles that. If we were to take over the 'jqueryui' bower package, we'd have to go back and update old tags to include compiled files. Even then, the structure of our repo doesn't match the structure of this repo, so we'd likely end up breaking existing applications. I don't think that's in anyones interest.
The text was updated successfully, but these errors were encountered: