- Development - lists.drupal.org

Re: development Digest, Vol 39, Issue 5
by David K Norman 02 Mar '06

02 Mar '06

For admin approving account: http://drupal.org/node/37353#comment-56461 I'm modifying and testing the attachment and I'll commit it to CVS today as contrib module user_status for 4.6. I won't have time to roll it for 4.7, but there sure seems to be enough interest for someone to pick up that FAPI conversion. development-request(a)drupal.org wrote: > Date: Thu, 02 Mar 2006 07:10:49 -0500 > Subject: Re: [development] email when admin approves account: can it > get into 4.7? > > I suspect that it won't - we're working on critical bugfixes > ONLY at the moment, and this is neither a bugfix, nor critical. >

1 0

Which modules should be categorized as developer?
by Kieran Lal 02 Mar '06

02 Mar '06

http://drupal.org/node/50091 Neil Drumm requested that developer be a specific category for modules. If there are some modules that you believe should be tagged developer please respond on the issue and I'll update the spreadsheet. Dries can update http://scratch.drupal.org/project/modules from the spreadsheet. Cheers, Kieran

6 7

javascript in 10 minutes
by Adrian Rossouw 02 Mar '06

02 Mar '06

This helped jog my memory of the little javascript I did several years ago, perhaps it will be of some use to other people who are currently rusty =) http://javascript.infogami.com/Javascript_in_Ten_Minutes -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com

1 0

Out of Office AutoReply: [feature] Event should use node teaser on calendar view (e.g. event/2006/03/02/week/all/all)
by Steve Parks 02 Mar '06

02 Mar '06

I'm out of the office until Tuesday 7th March, and will have very limited access to emails. I'll get back to you as soon as I can. Thanks Steve

1 0

Out of Office AutoReply: [bug] Reply to non existent comments
by Steve Parks 02 Mar '06

02 Mar '06

I'm out of the office until Tuesday 7th March, and will have very limited access to emails. I'll get back to you as soon as I can. Thanks Steve

1 0

Re: [development] OpenID
by Jonathan Daugherty 02 Mar '06

02 Mar '06

> What's the status of this module? I'd like to begin using it on my > personal site. Robin and others, Sorry I've taken so long to get back to you about this. We've been working hard on getting the PHP library (and others) ready for a 1.0 release. Hopefully we'll have 1.0 ready by the end of this week or by early next week. Once 1.0 is out, I'll update the Drupal module I posted to work specifically with 1.0 and I'll also begin work on implementing server support in Drupal. Please contact me off-list if you have any further questions. Thanks! -- Jonathan Daugherty JanRain, Inc.

1 0

critical bugs vs release (candidate)
by Ray Zimmerman 01 Mar '06

01 Mar '06

On 28 Feb 2006, at 22:23, Dries Buytaert wrote: > We're down to 13 critical bugs. > > I guess we'll release a beta 5? I don't think we had 0 critical > bugs left when we released either Drupal 4.5 or Drupal 4.6 but I'm > willing to try. I have this feeling that it might take us many > more weeks to fix them all. On Feb 28, 2006, at 4:52 PM, Karoly Negyesi wrote: > Why not RC , really? Disclaimer: I'm relatively new around here, so please ignore this if the community already has clearly defined conventions for these that I'm not aware of. In order for the terms "critical bug" and "release candidate" to carry consistent meaning, I would suggest that we insist on getting down to 0 critical bugs before release. IMHO, either a bug is not critical or the code is not ready for release (i.e. not a release candidate). If that is not the case, then it sounds to me like we need yet another higher priority level for "show stopper" bugs. Consistent with that, "release candidate" to me means, "this is the version we plan to release if no critical issues arise in the next x days", in which case I think we might be ready for a beta 5, but not for a RC. On a related note, I think it would be useful to have a link on the issue submission pages that points to a help page with some guidelines clarifying the options for the different fields (e.g. how to decide whether to report a bug as normal or critical, etc). Thanks to all of you for making Drupal happen, Ray

1 0

cool comment trick
by Karoly Negyesi 01 Mar '06

01 Mar '06

/* some optional code here /**/ now, if you change the first line to //* some optional code here /**/ then the optional code will run. This is prolly the simplest way (one char!) to switch on-off blocks of code. Regards NK

3 2

Re: [development] unmaintained modules listing
by Kobus Myburgh 01 Mar '06

01 Mar '06

Let me rephrase... Is the project module in CVS head the one used on Drupal.org? Regards, Kobus >>> dries.buytaert(a)gmail.com 3/1/2006 11:56:20 AM >>> With the project module in CVS head, we can show the 'last changed' date for each of the projects. Kobus, care to help improve the project module? That would be invaluable. :) -- Dries Buytaert :: http://www.buytaert.net/

2 1

Re: [development] unmaintained modules listing
by Kobus Myburgh 01 Mar '06

01 Mar '06

> Kobus, care to help improve the project module? That would be > invaluable. :) Dries, thanks for the vote of confidence, but I am not sure I am *that* clued up yet. I can try though. Do I download the project module from the download site, or what do I do? I am sure that the project module on Drupal.org is not stock standard? Regards, Kobus

1 0