I'd like to release a 1.0 version of this thing. It's my hunch that people are hesitant to install the module while in development. So we need to stabilize and release.

What do we need to do be ready for this?

Bugs:
I don't see any other bugs in the issues list. JB and Gwen you two have been working through the features of the module, how far along are you? Would you consider the current source bug free enough for a release?

Features:
There are more than enough features for basic use. I know that views is a big thing, but I think it can wait for 1.1. What are your thoughts on this?

What's left:
Buddy list migration. This definitely needs to be in 1.0. I don't think it'll take too long to do. I'll try and get it done in the evening some time.
The blocks patch should be another plugin. Providing basic page views is the only essential to the API.

Let me know what you think.

Comments

gwen’s picture

gwen commented

Bugs:
I just entered a minor bug that probably ought be fixed prior to official release: http://drupal.org/node/177651.

Views:
I think that views integration can wait for 1.1, but I don't think the module will get wide adoption until we get that done.

Blocks:
My 2 cents. I feel the blocks actually belong in core. The blocks are very basic keeping with the stripped down philosophy of core and I think most site admins are going to want to have some form of relationships blocks, be they themed out versions of the basic blocks or blocks generated custom via views. And since the blocks we're giving folks are *really* basic (just username and relationship name in the case of all), I don't think it's enough functionality to warrant a separate module. My gut feeling is that most site admins (myself included) prefer keeping the number of installed modules to a minimum so would appreciate the basic blocks be in core. Additionally, if the blocks aren't activated, the block code will never be called, so I don't think there are any performance worries. But I may be in the minority on this. Anyone else have opinions about this?

Release:
I think we're close but not yet at official release. Aside from resolving the block issue one way or another, we haven't had a chance to thoroughly test the module. Most of the bugs we've found have been things that have come up as we've been theming things out. I think that before doing an official release, it's worth the time for someone (be it us or someone else) do QA separate from development. Maybe someone out in the community's done that already?

prfctns6@gmail.com’s picture

prfctns6@gmail.com commented

Regarding blocks: I agree with Gwen. It seems to me to be core functionality. It doesn't extend the functionality of user relationships at all - it just gives administrators more flexibility in viewing the basic functionality. I vote for blocks living in core.

I also agree with Gwen that a bit more formal testing is warranted before we declare 1.0. I know of no specific issues that would prevent us from declaring 1.0, but we just found and fixed another small detail today, so, personally, I wouldn't feel comfortable saying it's 'released'.

sprsquish’s picture

sprsquish commented

Okay, I'll defer to you two on the block thing, core it is.

As far as running through the system, is there a percentage of each piece you could give me? I'll try to pick up the slack and check through the other parts.

One major outstanding problem is Zahor's: http://drupal.org/node/175518

Gwen and JB, you both have commit rights, so feel free to commit small things. Formatting differences are bike shed and I don't want that to get in the way of progress. I'd still like to look through larger blocks of code.

sprsquish’s picture

sprsquish commented
Status: Active » Closed (fixed)