Official 5.x backport
jrguitar21 - November 27, 2008 - 17:23
| Project: | FeedBurner |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
I'm getting bitten by this annoying bug in 5.x-0.5, but am weary to update to dev version on a production machine with large user base, ESPECIALLY when it says in bold: use at your own risk.
I understand you have a development version that fixes a few things from 5.x-0.5. The outstanding bugs reported seem to be few.
How stable is 5.x development at this point? Would it be possible for a 1.0 release for D5?
Thanks!
#1
When I started working on the 6.x version, I started from scratch. I've resumed working on this module again to get an offical 6.0 release out. Once that happens, I can start backporting to 5.x again. The 5.x-1.x release is available at http://drupal.org/node/162489 and it was the last 'recommended' release that seems like it works without any major bugs.
#2
As I'm working on some of these new features for 6.x, I'm realizing that the official 5.x version of this module will have to be a 'lite' version of the module without some of the cool features, because they are not possible in Drupal 5.
#3
thats cool. thanks for helpful explanation!
Im going to check out your "stable" D5 version linked above.
#4
Not sure I'm ever going to get to this. Drupal 7 port will be a priority over the Drupal 5 backport and will be much easier for me to do. I'll accept valid and functional D5 patches.