Archived Boards and Threads... > SMF Feedback and Discussion

What can we do to help grow our 3PDs?

<< < (23/23)

Don't forget that Charter members do get it ahead of the rest of us, but I can see what you're saying. You'd almost have to hand out a form of NDA to ensure it doesn't get distributed ahead of schedule.

Eliana Tamerin:

--- Quote from: aldo on July 03, 2009, 10:27:21 PM ---Not sure if this has yet been stated, but it is pretty important I think it wouldn't hurt to restate it XD.

Software previews... or something like that. I know SMF releases beta's and RC's, but for certain projects, it requires more than that. Like TinyPortal (Though the creator of that is/was a SMF dev :P) and SimplePortal which use SMF in many ways is a tough thing to do and can take lots of time for the developers to get it properly working with the new version. Developers might get their projects working with SMF beta's and RC's, but each time a new version is released, a lot has changed and then their product cannot be used by clients for awhile until they have it working with the new version.

Basically, these developers need to be able to see what and how SMF is changing before a version is released. I don't mean SMF tell them first, wait a week or more, then release it. But in some way allow third parties to have some kind of access to know more of what is changing in new versions of SMF in a day to day basis.

Basically what I am saying is kinda like what Microsoft and Apple do... When they are developing the next version of an operating system, they give developers access to SDK's earlier than others, sometimes even giving them the whole operating system so they can test on it and what not. It would be a lot for SMF to do, but you could have some kind of team to do something like that.

So yeah :)
Sorry if some things didn't make to much sense... I am sitting in a 90 degree room .-.

--- End quote ---


Beautiful idea. Great for the large and popular mods that often come head to head with the bugfixes and changes in SMF, which causes delays for users, especially with pre-release versions.

If SMF had a quicker release cycle it really wouldn't matter much. SMF has a great platform for notifying administrators of new updates, (although a notice on index wouldn't hurt) coupled with a more modular structure in the future (one can at least dream) SMF can basically update modules with small feature additions or changes instead of having to wait a year for a huge update. That way updates required to mods would be minimal at best, especially if each module provides an API and make as few changes as possible to that.

Giving out early releases would be a band-aid solution and would involve a lot of work with no real gain, IMO it's yet again a question about code structure.


[0] Message Index

[*] Previous page

Go to full version