Initial release? (Relation)

subscribing

subscribing

subscribe

subscribing :)

What needs to be done to get the ball rolling on this project. We require it for one of our sites fairly soon. I'm happy to help commit code or provide funding. Just let me know what the low hanging fruit are to get an initial release out with a firm foundation to build upon.

Cheers
Jordan

Looking forward to help test this.

With the module, I have errors already trying to 'relate' so will wait until a response given as to the next steps of development of the module here etc.

can't await this psychedelic thingee

subscribing

subscribing

can maintainers of this module list the issues that needs to be closed before the initial release, so we could help u out?

subscribing

subscribing

+1

Minimally, these need to be sorted (there is some overlap between them):
#1018408: Data storage concept
#869000: Relationships as entities
#989566: Finish adding all standard CRUD functions
#988970: Field Validation
#1012322: dummy Field UI / autocomplete
#981398: Bundle creation and UI
#948946: N-ary relationships?
#957744: Why are self-references actively prevented?

Once in Beta, these need to be sorted before a final release:
#996980: Produce awesome documentation for this awesome project
#894590: Views integration

Feel free to add the '1.0 blocker' tag to those issues, if you subscribe to them

I took the liberty of tagging the lot of them.

subscribing

subscribing

subscribing

subscribing

Thanks Shadlington.

subscribing

subscribing

Subscribe

Subscribing

subscribe

subscribing

sub

subscribing

subscribing

subscribing

subscribing

subscribing

Subscribing

/me is already subscribed to all Relation's issues but...

Subscribing

subscribing

subscribing

subscribing

subscribing

subscribing

subscribing

me too

Subscribing

Added module name to issue title to help distinguish it in lists involving multiple modules (such as "Your Posts").

subscribing

+1

...just a heads-up: people can help testing #1113654: Relation reboot (which is the follow-up of #1061688: Available entities browser). Testing and reporting back will help get a release out soon(er). Well, that issue + those listed in #14 ;)

it would be nice though, if people didn't fill that thread with subscribe comments. We will post here as soon as we make any kind o release, alpha, beta, or full.

Of course, any testing feedback is most welcome over there.

...don't worry about the feedback ned. From what I see in the module's usage stats, it's going up. I guess this might be due to the purpose of the module to replace a lot of very popular others. So I guess you might even be getting more feed back than you can handle pretty soon. 'Careful what you wish for.' isn't it what people say? ;)

Sure, but even when it's mostly noise, there's some signal :)

There we go! We're doing it again ;) ...seriously now, I'll shut up.-

39+ subscribe comments out of 52. I think this thread is already a lost cause ;)

double subscribe

While the subject's hot, why didn't they consider a "subscribe" button for the new drupal.org. I hate subscribing but otherwise, there's too many threads to follow

[UPDATE]
There's an effort already going on and I wanted to share the link so others can 'chip in' - http://3281d.com/2009/03/27/death-to-subscribe-comments

...this one too: #288726: Allow users to subscribe without posting a comment

The one you want is http://drupal.org/project/project - which runs the drupal issue queue, and
#34496: [meta] Add Flag module to allow users to subscribe/unsubscribe without posting a comment - the actual issue tracking this feature.

yep, I knew that... http://drupal.org/node/34496#comment-4325362

subscribing and desperately waiting for this.

subscribe

Interesting

                                                              ---------------
                                                              |  WE LIKE !  |
                                                              ---------------

Subscribing

sub

It seems that #894590: Views integration is the only pending issue!

Remon: That's because most of those issues are now irrelevant because of the restructure. We are very close to the first alpha, but there will likely be some other big issues to add to the list before a 1.0 release.

Sounds great!

So, how is it going now ? Could you maybe create a new list of issues you would like to solve and feature to be introduced before the first alpha is released ?

subscribing

The biggest problem right now that relation_query() does not have unit tests. Up until about 15 minutes ago it was always returning everything (opsie). This (and I mean the lack of tests) must be fixed before any release can come about.

Hokay! We have an Alpha!
http://drupal.org/node/1131944
It does mostly what it says on the box, and it does it reasonably stably, as far as I can tell. It's an alpha though, so testing has not been extensive. This is not intended for use on production sites, so please do not complain to us if something breaks and you loose all your valuable data. But you knew that already, right?

Bug reports and feature requests are more than welcome, so have a play and let us know how it goes on the issue queue.

Marking as fixed.

...thanx for the update ned!

...btw, can we please have an updated dev please? Thanx in advance.

Just pull from git from the 7.x-1.x branch. We won't be making -dev releases.
git clone --branch 7.x-1.x http://git.drupal.org/project/relation.git

Even if people do know how to get latest dev code from git, how would they know there's an update? There won't be any update info in our site's 'Available updates' report. I for once use dev versions of almost all modules I install in order to be able to test patches (which in most cases go against the latest available dev) + I evangelize on this practice in non-production sites. By not releasing a dev version relatively regularly you're making testing of fixes and/or new features hard(er) -especially for non-tech-savvy people-.

Please reconsider having the regular dev created after each important commit. Thanx in advance.

I rarely use the available updates page myself.
You can see when the last commit took place. The last one was 10 hours ago, for example.

Plus this module probably shouldn't be used by non-tech-savvy people just yet.

Dev releases are not the kind of thing you want to be advertising to everyone on the "available updates" page, because they are inherently untested and unstable. That's all the more reason for not making them. Dev versions should not be used by non-tech savvy people unless they need a specific fix to a specific problem, in which case they can come to the issue queue, and go from there. Sorry klonos, there will be no dev releases.

When I said "...how would they know there's an update?..." I didn't mean to actually ask for a way, but rather point the fact that most (again non-tech-savvy) site admins use the 'Available updates' page to *easily* update their site (think drupal.org newcomers). I believe it's enough that drupal already has the reputation of having a steep learning curve and the fact that we often ask people to "patch" things in order to achieve desired functionality. Also asking them to pull code from the repositories and learn git would chase people away -especially Windows/GUI accustomed admins-.

...this module probably shouldn't be used by non-tech-savvy people just yet.

...again, chasing people away. So, I'll kindly disagree on that. We can't be asking people to help on the one hand and then -once they are convinced and decided to try to- simply start throwing the "go learn how to use drush/git/etc" reply to them. I strongly believe we need testing and feedback by as many people as possible in order to move ahead faster. I mean, come on people! Is it so hard and time consuming for one of the maintainers to issue a command (that he already is familiar with) and have a dev get built every now and then, that we need to ask all potential testers to learn new things in order to help us test.

I am really sorry Tom, but what is that "visit drupal.org and check the commit log every now and then in order to find out if there's been an update" suggestion of yours. I really like my email notifications and the occasional checking of the site's status & updates pages to do this in a more automatic manner - thank you. That's why these features were developed and are there for in the first place anyways.

PS: Please don't get me wrong people. I don't mind the "we won't be releasing dev versions that often" answer. I simply don't appreciate the "we won't be releasing dev versions *ever*" thing.

My view doesn't represent the views of the maintainers of the module in any way.
I'm just saying 'no dev release is cool with me'.

...yes I get that Tom. The PS part of my comment was kinda meant for ned's comments in #73 and #76, but since he's not the only maintainer of the module I choose to use the word 'people' to refer to them all.

@naught101: I won't argue any further on this ned (it doesn't help this issue anyways) but do allow me to say this final thing - hopping I'm not busting anyone's b@@ls here:

You see, dev versions are not advertised on the "available updates" page by default. They only show up if someone has already installed a dev previously and they stop showing up as soon as they are upgraded to a stable release. In fact, you can even 'hide' them from public by choosing not to have them listed on the project's page. You even have the option to 'flag' them as not-officially-supported. So it's not as if you risk people coming back in the issue queue with silly questions/problems because they use dev despite the fact they shouldn't. It's as simple as...

- a person either has a bug to fix or a feature to implement and they want to help by testing
- they instal a dev instead of the stable because that's where the action is + patches are against latest dev too
- they get a series of updates about new dev releases in their site's available updates page
- they re-apply any available patch as they upgrade to successive dev versions and report back, making sure nothing else breaks as development of the new feature or bug fix moves on
- once the patch(es) they've been re-applying with each new dev get committed, they finally switch to the stable that now includes the code they helped test
- no more updates on dev versions "advertised" in their available updates page.

A legit dev 'life-cycle' don't you think?

Klonos, your wish is my command. -dev releases are now available :)

Thank you ned! I honestly appreciate it and am grateful for even taking the time to read my -lengthy- last comment. The "your wish is my command" thing though makes me feel kinda bad - never mind ;)

+1000! (#80, #81).

Subscribe

Please note that a beta release has now been made. From here on in there will be upgrade paths between releases. This does NOT mean that the software is stable, but it will be more stable than it has been so far.

Testing feedback would be very valuable, but please make sure to search the issue queue first. Cheers.

Hey everyone over here, if you get a few minutes, we'd like your ideas and use-cases for relation:
#1282376: Brainstorm: What do you want out of relation?