Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
4.0 Ready Plugins?
Is there a way to tell which plugins are vetted for 4.0 compatibility without having to pick through the forum on a plugin-by-plugin basis? I checked textpattern.org but there doesn’t seem to be a way to search the plugins for compatibility version. I yearn for a system like they have over at Mozilla Update …
After enduring years of Art School, mild mannered Owen Waring noticed some unusual changes… the constant bombardment of criticism, it seems, had altered his DNA. Half pixel pusher, half programmer, he had become…. THE BIZARTIST
Offline
Re: 4.0 Ready Plugins?
that’s a nice idea but then i guess someone would have to vet the plugins one by one, and how do you deal with plugins that you don’t know if they’re supported or nto anymore – i suppose you would have to contact the authors to find out if they will still support it, or if they won’t then place it for grabs to be updated?
Good intiative though it would be quite useful
Offline
#3 2005-08-17 22:32:34
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: 4.0 Ready Plugins?
Yeah, its pretty much up to the plugin authors. As far as I know, mine all work in 4.0, since I tried to keep up with every revision.
Offline
Re: 4.0 Ready Plugins?
Plugins that worked for RC4 and RC5 should also work just as well with 4.0.
Yes, we have plans for adding information into plugins about which textpattern versions they work with. It will happen. Eventually. ;)
Offline
Re: 4.0 Ready Plugins?
granted, there are sever logistics hurdles, but I think it might be neccessary if we want to extend the capabilities out to the whole TXP community, and not just us forum surfers…
After enduring years of Art School, mild mannered Owen Waring noticed some unusual changes… the constant bombardment of criticism, it seems, had altered his DNA. Half pixel pusher, half programmer, he had become…. THE BIZARTIST
Offline
Re: 4.0 Ready Plugins?
cool beans! dang you guys are quick, barely got my post out…
After enduring years of Art School, mild mannered Owen Waring noticed some unusual changes… the constant bombardment of criticism, it seems, had altered his DNA. Half pixel pusher, half programmer, he had become…. THE BIZARTIST
Offline
Re: 4.0 Ready Plugins?
it might be worth getting a few people together, havinga test install of 4.0 and testing out the plugins or if one person wants the task….:)
Offline
Re: 4.0 Ready Plugins?
I would agree that its probably up to the plugin author to say if something is compatible or not. I’ve been thinking of a way to easily show what version of TXP a plugin will work with and the only thing I can think of is to include the TXP version as part of the plugin version.
Plugin versioning is pretty arbitrary right now with most people starting at 0.1 and going up. But some people also have started at 1.0.
My thought is to bring all plugins to version 4.0 to indicate that they work with TXP4.0. Then, if the plugin author makes an update it would be version 4.0.1 and keep moving up from there. Then, when TXP moves to 4.1, any plugin that only worked on that version would start with 4.1 and updates would follow with 4.1.1, etc.
A call for all plugin authors to change version number to 4.0 would also give a good indication of which plugins are being actively maintained. Any thoughts on coming up with some common version numbering like that?
Offline
Re: 4.0 Ready Plugins?
The only problem with version branding plugins, is that most plugins are generic enough to work with any version.
Offline
#10 2005-08-18 14:09:17
- igner
- Plugin Author
- Registered: 2004-06-03
- Posts: 337
Re: 4.0 Ready Plugins?
Personally, I’m not too keen on starting plugins at version 4 simply because it implies a maturity that isn’t necessarily there. I generally prefer the 0.x ++ numbering scheme; given that closed beta testing on the plugins is challenging given the diversity of environments, the only real way to test is to put them out there and wait for feedback, and to me the 0.x versioning scheme reflects that — an 0.1 release is an initial public release, possibly with a minimal feature set, on up. A 1.0 release to me implies a stable feature set, and a relatively bug-free code base.
And then my dog ate my badger, and the love was lost.
Offline
Re: 4.0 Ready Plugins?
I decided that none of my plugins would reach 1.0 until such time as I was sure that they would actually work with 1.0. I released version 4.0 of one the other day and intend to follow the others one as they complete testing.
Numbering them less than 1.0 while they are in test phase makes perfect sense. But numbering them 4.0 when they are fully released makes sense as well.
Offline
#12 2005-08-18 17:38:05
- igner
- Plugin Author
- Registered: 2004-06-03
- Posts: 337
Re: 4.0 Ready Plugins?
Except that I’m not so certain it does make sense to arbitrarily skip the interceding steps. Version 4 implies there have been 3 significant revisions since the original “release”. What happens when TXP 5 is released, and your plugins remain essential but need no change (because that piece of the TXP core doesn’t change)? Do you re-version your plugins? Or leave them at version 4? If the former, then the version number is effectively useless. If the latter, then what’s the point of using a version number to match the TXP version?
I realize a lot of the versioning is somewhat arbitrary, I just think it’s kind of disingenuous to arbitrarily release a numerical version based on the TXP version – so we’ll have a raft of initial plug-in releases at version 4.0, effectively subverting the whole concept of versioning. I suppose if developers are wedded to the concept of sychronizing plugin versions to the TXP version, I’d suggest the format of v4r1.0 – which then contains the TXP version number, as well as an incremental value for the plugin. Not that I’m particularly keen on that, either.
I think it’d make much more sense to add something like “Tested Under:” to the resources pages at textpattern.org for tracking version compatibility.
And then my dog ate my badger, and the love was lost.
Offline