|
1 | | -## Status |
| 1 | +# Project Moved |
2 | 2 |
|
3 | | -As you may have noticed we are working through the backlog of issues and pull requests |
4 | | -and trying to get those caught up. Couple of quick notes related to this. |
5 | | - |
6 | | -1. A new gem with Rails 4 support HAS BEEN recently RELEASED (1.0.12). |
7 | | -2. If there is a specific feature that is in master, but not in the gem I strongly suggest you |
8 | | - point to the specific changeset that addresses your issue rather than directly at master. There |
9 | | - are going to be a lot of changes going on here and while we will do our best; there will probably |
10 | | - be some breakage on master in the short term. Use at your discretion! |
11 | | -3. Some pull requests have been submitted to address the same functionality; in those cases we will try |
12 | | - to pick the best/optimal solution, accept that and close out the other tickets. |
13 | | -4. Backwards compatibility is considered a high priority, so if a pull request is a great idea, |
14 | | - but it breaks backwards compatibility, it will be closed and noted that it causes breakage |
15 | | - to backwards compatibility. If anyone passionately wants the feature they are welcome to update |
16 | | - in a way that maintiains backwards compatibility and issue new pull reqs. |
17 | | -5. Performance is critical. If a feature is a nice to have, but has been implemented in such a way that it causes |
18 | | - performance degradation to existing searches; it will be rejected. |
19 | | -6. Thanks to everyone who is submitting pull requests, issues, comments, etc... I appreciate the help |
20 | | - from each one of you. Sometimes it has to get worse before it gets better. But I promise, |
21 | | - it will get better! |
22 | | - |
23 | | -------- |
24 | | - |
25 | | -Thanks to David @ crowdint for creating this gem and all of his hard |
26 | | -work on it in the past. |
27 | | - |
28 | | -Just posting this update to let everyone know this project is still |
29 | | -alive and has a new maintainer. Over the next couple of weeks we will |
30 | | -be reviewing existing pull requests and you will see updates shortly. |
31 | | - |
32 | | -Thanks for your patience. |
33 | | - |
34 | | - |
35 | | - |
36 | | -------- |
37 | | - |
38 | | -Unfortunately, I don't have much time to work on this gem, I'm looking for |
39 | | -someone to help with its maintenance. Send me an email if you are interested in |
40 | | -getting push privileges to this repo. |
41 | | - |
42 | | - |
| 3 | +There has been some confusion around the naming as to where to find the Rails4 version of this gem due to the original naming. With the latest release I have taken the opportunity to address this by moving the official repo. |
43 | 4 |
|
| 5 | +The official repo is now located at [rails-jquery-autocomplete](http://github.com/bigtunacan/rails-jquery-autocomplete) |
44 | 6 |
|
45 | 7 | # rails3-jquery-autocomplete |
46 | 8 |
|
|
0 commit comments