Unfortunately, the down side to announcing such "updates" is that people become impatient to get them:
----------------------------------------------------
"We've just finished coding a new gallery bridge than integrates XF with [insert gallery products] - Yeah us!!!! We're off for some coffee and buns now."
Next post: "Oh, fantastic, I've been waiting for this to convert to XF from [insert forum patform] - when is it going to be available? Is it ready now?"
"Sorry, no, it's not available yet. We've only just coded the basic 'alpha' of the bridge, we still need to test it and get some real-world conversions done first to iron out any bugs."
Next post: "Yeah, sure, but when will you be releasing it? I *need* this to migrate and I want it as soon as possible!!!"
"Erm, it's a long way off being released. We've got so much other stuff to work on too, so it'll come as part of a package of updates in the next general release of XF."
Next post: "Yes, I understand that - but WHEN? Geez, I'm totally desparate to convert my site. Can't you release it now?"
"No. It's not ready, and won't be release on its own, it'll be part of a package - as we've already said."
Next post: "Oh FFS this is just f***** stupid. You've already coded it, why can't I just have it and sort out any problems if they come up? Can't you PM me a separate download package with it in?"
"Erm. Please don't swear. No, we can't do a separate download. We've already explained the position; you'll just have to wait for the next release. Besides, giving people alpha versions is not good practise."
Next post: "Well that's just f****** stupid. I'll take all the responsibility. I can't do anything until I get this feature. You've already coded it, yet you are forcing me to stick with my old software. It stinks! Why tell people about it when it isn't even f****** anywhere near ready?"
"Okay, well this is the sort of reaction we'd hoped to avoid, so we're going to stop announcing up-coming features and just tell people about them once they are ready to be released."
THREAD CLOSED!
----------------------------------------------------
Now imagine that scenario over the tens/hundreds of "feature requests" or "in development" items that XF are dealing with, and it's easy to see how announcements are just simply not worth investing time in for the XF team at the moment.
It's not just about the announcement, it's about managing people's expectations and dealing with the fallout if customers become disappointed. You're far better off being informed about things that are
actually happening - that
are going to be included - than getting all excited about "possibles" and then being let down when they don't materialise.
Someone quoted IPS as an example; all of their recent 3.2 announcements have been about features THEY HAVE ALREADY INCLUDED in their next version - I'm sure the XF team will do similar once they get rolling and have the opportunity. (You'll also find lots of
speculative IPB 3.2 threads on the Invision forums too - and a fair few grumbles because feature x, y, or z doesn't appear to have been included in the announcements thus far. So they're not telling everyone everything either!!!).
Cheers,
Shaun
(NB: The poetic license is totally a liberty of my taking and doesn't represent anyone from XF or any particular customer and/or feature. Just thought I'd mention that in case anyone took it seriously ....
)
let kier work on the code............
That's the kind of updates I'm talking about.
