Derek and all. Would there be an easy way to track module releases? Perhaps an RSS feed on drupal.org only for release nodes only? That should do the trick. Any better ideas? ---------- Forwarded message ---------- From: Khalid B Date: Jan 15, 2007 1:17 PM Subject: Re: [consulting] casetracker 5.x-1.1 released To: A list for Drupal consultants and Drupal service/hosting providers < consulting@drupal.org> On 1/15/07, Morbus Iff wrote:
Are these sorts of updates important to consulting folk? I'm only continuing because I know a lot of folk here expressed interest in CT.
Yes, they are. Which brings up the point of whether we should have a central place where module releases are announced. Maybe a forum on Drupal.org just for module releases (RSS goodness), or a dedicated mailing list?
Hello, all, Maybe I'm missing something but I just subscribe to http://drupal.org/taxonomy/term/14/0/feed Is there a better way, or something that slips through the cracks here? Cheers, Bill Khalid B wrote:
Derek and all.
Would there be an easy way to track module releases?
Perhaps an RSS feed on drupal.org <http://drupal.org> only for release nodes only?
That should do the trick.
Any better ideas?
---------- Forwarded message ---------- From: *Khalid B* Date: Jan 15, 2007 1:17 PM Subject: Re: [consulting] casetracker 5.x-1.1 released To: A list for Drupal consultants and Drupal service/hosting providers < consulting@drupal.org <mailto:consulting@drupal.org>>
On 1/15/07, *Morbus Iff* wrote:
Are these sorts of updates important to consulting folk? I'm only continuing because I know a lot of folk here expressed interest in CT.
Yes, they are.
Which brings up the point of whether we should have a central place where module releases are announced. Maybe a forum on Drupal.org <http://Drupal.org> just for module releases (RSS goodness), or a dedicated mailing list?
Maybe I'm missing something but I just subscribe to http://drupal.org/taxonomy/term/14/0/feed
This is for new modules only, not new releases of modules. -- Morbus Iff ( you're just a copy of an imitation ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
Maybe I'm missing something but I just subscribe to http://drupal.org/taxonomy/term/14/0/feed
This is for new modules only, not new releases of modules.
Hrm. Releases for 5.x get automatically tagged with "5.x", so, theoretically, the following would be "new releases for 5.x": http://drupal.org/taxonomy/term/78 -- Morbus Iff ( you're just a copy of an imitation ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
On Jan 15, 2007, at 10:27 AM, Khalid B wrote:
Would there be an easy way to track module releases?
there are 2 feature requests about this already on the future work list: http://groups.drupal.org/node/1830 1) allow email subscriptions for new release nodes per project: http://drupal.org/node/94137 2) RSS feed of new release nodes per project: http://drupal.org/node/94138 patches or funding welcome. ;) meanwhile, yes, you can subscribe the taxonomy RSS feed for a specific drupal core compatibility term (as suggested by morbus), e.g.: http://drupal.org/taxonomy/term/78 cheers, -derek
Parse error: parse error, unexpected '&', expecting T_VARIABLE or '$' in /home/yktdan/public_html/drupal5/modules/contrib/fquery/fquery.module on line 76 Similar bugs in coder and widgedit and probably elsewhere
On Jan 15, 2007, at 12:23 PM, Walt Daniels wrote:
Parse error: parse error, unexpected '&', expecting T_VARIABLE or '$' in /home/yktdan/public_html/drupal5/modules/contrib/fquery/ fquery.module on line 76
Similar bugs in coder and widgedit and probably elsewhere
a) these are all contrib modules, so your subject was both a little misleading and a lot scary at first. ;) b) please post these bug reports where they belong, into the issue queue of each corresponding project where you see the bug. e.g. to report this error for fquery, you'd use: http://drupal.org/node/add/project-issue/fquery/bug for other projects, just replace "fquery" in that URL, or change the "Project" drop-down selector on the above form. c) actually, before submitting, please search for existing issues in each project, first. these might already be well-known bugs. hehe, for example: http://drupal.org/node/109596 thanks, -derek (dww)
Op maandag 15 januari 2007 19:27, schreef Khalid B:
Derek and all.
Would there be an easy way to track module releases?
Perhaps an RSS feed on drupal.org only for release nodes only?
That should do the trick.
Any better ideas?
(crosspost from consultant ML this is a better place to continue the thread) I would vote for an extra feed-category in aggregator on Drupal. That way we can simply add our own feeds (a special term on our sites off course) to push out new + interesting posts. Own site over Drupal has two benefits: Kudos/Recognition plus we all know/like our own platform best. Downside is the time required to administrate the feeds on d.d.o. Bèr -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl
participants (6)
-
Bill Fitzgerald -
Bèr Kessels -
Derek Wright -
Khalid B -
Morbus Iff -
Walt Daniels