Status of new development
daneyuleb - September 10, 2008 - 13:12
| Project: | User Relationships |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I'm very glad to see the project has been taken over. I know it's early, but have you had enough time to give any idea of the situation? Is this now on a "fast track" to version 6 stability? I'm trying to decide if I should attempt to wrench buddy list 2 into doing what I want, or if this very nice module will be ready for prime time soon and make my life much easier :)
#1
I've been using User Relationships for some time now, though not all of its features (notably not blocks as and implied relationships). The API is good, and I consider it stable. So I'm not expecting to make any changes in that area.
Things that are immediately outstanding for a stable release are Views support (working on that now); that and blocks need to be fixed as well, as most of them are unusable because of the argument problem (http://drupal.org/node/257198). At that point another beta release will come out.
Further changes will depend on feedback and any bugs. I'd like to implement a few more features, like more control over which roles can create what relationships; also integration with invites, to auto-create relationships when inviting someone to the site; better express through the UI the functionality of UR Node Access (blocks and/or Views filters).
So, to your point, it should be safe to build dependencies on the API if it already supports your use cases. As it's not officially frozen yet, we can look at anything that it doesn't do for you, that plugin modules cannot solve.
#2
@alex.k
there are quite a few patches pending in various states. Would you consider reviewing and commiting those if appropriate? Cleaning up the issue queue (and when those are already resolved through patches) can help you gain momentum again.
Also there are quite a few feature requests. You may want to quickly triage them and mark postponed (atleast the ones that will never get fixed in 5.x).
#3
It would probably speed things up if alex.k had some help in that regard. If others were going through and applying patches themselves to see if they actually work or not, closing out duplicate bug reports, etc. then it would make it much easier for him to focus on getting a stable release out.
#4
I'm reviewing patches and responding on their issues if more work is needed. If anyone wants to revisit these issues and review them, it'd be just great.
As for feature requests, I want to gauge how much interests there is among users of 5.x branches. Just created a poll on g.d.o http://groups.drupal.org/node/14867 to gauge the user base, please vote! Once some results have been gathered it'll be easier to make support decisions. Thanks.
#5
Cleaning up the issue queue.
#6
Automatically closed -- issue fixed for 2 weeks with no activity.