So today cause i am kinda pissed off I decided to scroll through the archive announcement board just to see how much time has been between initial announcements until a final, then an announcement to the next release and when that actually got released.
So the first post was by David, on September 30, 2003
The Simple Machines team is happy to announce that the first beta package of SMF is now ready for all Charter Members! Thanks go to all the people who contributed in its development, including but not limited to Compuart, [Unknown], Jeff Lewis, Gobalopper, Omar Bazavilvazo, Andrea Hubacher, Joseph Fung, and David Recordon – not to mention all the people who helped with beta testing and language file translations as well as those involved in dreaming this up.
Please do not request a copy of this beta as the license prohibits a Charter Member from distributing their copy, if they do so their Charter Membership will be revoked. We hope to have a public beta in the near future but if you cannot wait purchase a Charter Membership today.
Thanks for all of your support and ideas over the past few weeks, this software would not be where it is today without all of you!
So from the initial announcment to the final release of 1.0 was just over a year later, this was done by [unknown], on December 30. 2004:
We are happy to bring you the final release of Simple Machines Forum 1.0. While there may be later updates, we believe this to be stable enough for production usage – and we are now focusing our development efforts on the next release, 1.1 Beta 1.
We encourage everyone to update to this new version. Mods, themes, third-party software integration bridges, and various other things may require this new version. If you need any help updating your themes, custom modifications, or anything else – please post a new topic in General English Support.
For those using YaBB SE, we also strongly encourage you to now update to this new version. Official support has been dropped for YaBB SE, and nearly all new development – whether it be mods, integration, themes, or anything else – is now being done for SMF. If you need any help moving custom modifications to your YaBB SE forum to SMF, converting mods you used with SMF, or simply working with SMF – please, don’t hesitate to post in General English Support. Furthermore, if you feel the new template system is too complicated, please feel free to use the old YaBB SE way instead. You may also want to read these instructions on upgrading from YaBB SE.
If you feel you have found a security hole or very serious bug, it is best to e-mail firstname.lastname@example.org as to make sure the correct people are notified. However, if it is not critical, it will be more quickly addressed if it is posted to SMF Coding Discussion or General English Support. For other problems, please post in the appropriate section of General English Support.
For those updating from SMF 1.0 RC2, the following is a list of changes made:
* package manager improvements.
* typos, whether in the displayed text or just in comments to the code.
* minor polish in various places.
* added a “last post” icon to ease migration; not mandatory, and won’t be shown if you don’t have it.
* an issue with polls for Mambo integration.
* some internationalization concerns.
* optimization and changes to better handle InnoDB tables, if used.
Please see the changelog for a more detailed list of these changes, and for changes since previous versions.
If you are upgrading from RC2 or 1.0 (preview), you only need to use the “update” package because it includes just the changed files. However, if you have any mods installed it would be better to use the “upgrade” package. Remember that you can use the “upgrade” package to go from any previous version of SMF. You can also use it to upgrade from YaBB SE.
You can always find information posted here about things like installation, upgrade, and more. The zip files themselves also include these manuals.
This was SMF’s first stable release under the name SMF, the team did an amazing job to get it out within over a year. The next release was 1.1 beta 1 and this was in the quick turn around time of 6 months if that, yet again announcement was by the then Project Manager David, a great guy and I have had pleasure of meeting him:
We are very proud to announce the release of SMF 1.1 Beta 1 to Charter Members tonight. This is another large milestone that adds many new features and refines areas of our interface. You’ve been able to use this version of our software here for the past week or so as we completed internal beta testing. Like when we were in a closed beta of SMF 1.0, we will not be releasing this beta beyond our group of Charter Members. We’d like to once again thank everyone who has helped SMF from its conception to the point it is at today.
Some of the major changes made in this release are:
* Added a search section to the admin center, including new options for search – like fulltext support
* Changed the way that avatars can be handled, offering the option for storing avatars separate to attachments (for a speed improvement), and the ability to force external avatars to be downloaded to the server
* Added additional notification settings, for selecting whether a user wishes to be notified on all events, and whether they wish to receive the message body in the notification
* Revamp of the theme settings area, to vastly improve theme management including more user friendly editing of themes, and a preview for style sheet editing.
* Overhauled the current registration system, including better handling of activation methods and optional COPPA compliance
* Added a sidebar to the personal message area, including support for “labeling” personal messages, and the option to display a capacity bar showing the state of the users inbox
* Attachments are no longer lost on preview
* Added support for custom message icons – by theme and board
* Added PM support for users accessing the forum through WAP2 or iMode.
* Extended the current xml feeds to include atom and rdf
* Added support for previewing posts without reloading the page, and username autocompletion when sending PMs
* Added new BBC tag “html”, to allow administrators to add HTML to their posts
* Added a new setting for maximum time after a post has been made that it can be edited or deleted
* Calendar management given it’s own area in the admin center, where holidays can be edited and/or added
* It is now possible to post events that are not locked to a specific topic
* Improved the admin interface to be cleaner, and more user friendly
* Added a currently hidden feature to use memcached or MMCache/ZPS/eAccelerator shared memory.
Thank you for your continued support,
The Simple Machines Team
This was release March 28, 2005, then 18 months later Grudge announced the release of the final of 1.1, this was December 02, 2006:
Simple Machines is extremely proud to announce the release of SMF 1.1 Final.
This release marks the transition of SMF 1.1 into the current stable release of SMF and we encourage all users to upgrade to 1.1 Final as soon as is convenient. For users of SMF 1.1 RC3, this release is a relatively minor change consisting primarily of bug fixes – although we have added a couple of options to help combat the rise in personal message spam. For users of SMF 1.0, the changes between 1.0 and 1.1 are too numerous to list here – but we’re sure you will be delighted with the new items on offer.
In summary, the changes/fixes since SMF 1.1 RC3 include:
* Option to require visual verification when sending a personal message
* Adjusted readability of visual verification system
* Added option to limit number of personal messages that can be sent per hour
* Fixed time offset bug
* Disallowed multiple failures with visual verification
* Made several UTF8 fixes
* Fixed various undefined index errors
Upgrading from your current version of SMF to the latest version could not be simpler, just follow the standard procedure of executing upgrade.php. But, please remember to make a backup!! The upgrader can be used for any installation from YaBB SE 1.5.5 all the way up to the latest version of SMF. You can always find information posted in the Online Manual about things like installations, upgrades, and more.
We also invite you to checkout the new Webinstall for even easier upgrading and installing.
With this release we’d like to take the opportunity to recognise the effort and dedication of all the people who have volunteered their time to help the Simple Machines project. Over the eighteen months since 1.0 Final we have given our site a face lift, relaunched the Mod Site, launched the Theme Site and added the Online Manual. In addition, our support team has grown and is actively supporting a community of over 60,000 members. So, we’d like to thank everyone, past and present, who has contributed to SMF’s development over the past three years. In particular, we’d like to extend special thanks to [Unknown], without whom SMF would never have been possible. We wish him all the best in his future endevours.
Download SMF 1.1 Final
So so far we can see releases have been pretty stable. SMF 2.0 is now put forward a healthy 5 months later, yet again by the Developer at the time Grudge:
For many months now we’ve been asked questions about what the plans are for the next release of SMF – what features it will have and when it will be available. We are now in a position to answer some of these questions. Simple Machines is proud to announce that the next version of SMF will be version 2.0 – in recognition of the scale of the changes implemented since SMF 1.1.
SMF 2.0 represents a significant step forward from the current version of SMF and has been in development alongside SMF 1.1 since December 2005. As well as adding new features SMF 2.0 makes considerable changes “under the hood” with improved caching, database abstraction and a move towards “Model, View, Controller” functions to improve integration and simplify mod writing. Whilst we are reluctant to announce all the features for this upcoming version the ones currently implemented include:
* Database abstraction – with support for PostgreSQL and SQLite planned alongside that of MySQL.
* Automatic installation of packages into themes other than just the default.
* Email templates to simplify customization of forum emails.
* Moderation center including post, topic and attachment moderation – to allow approving of user content before it is made public.
* User warning system.
* Additional group functionally including group moderators and requestable/free assignable groups.
* WYSIWYG editor to provide an intuitive user interface to those users not familiar with BBC.
* Permission improvements such as group inheritance and permission profiles to further reduce the complexity of the permissions system.
* File based caching for a performance increase on all forums regardless of whether an accelerator is installed.
* Mail queuing system to stagger the sending of emails to improve performance on large forums.
* Advanced signature settings to allow the administrator of a forum to more tightly control the contents of users signatures.
* Personal messaging improvements including ability to automatically sort incoming messages and a variety of display options.
* Improved upgrade script with better timeout protection and simpler user interface.
* Custom profile fields to enable administrators to add additional member fields from the administration center.
This is only a handful of the many improvements made in 2.0. Whilst we are not able to commit to a firm timetable for release of 2.0 we are hoping to get an initial beta in the hands of our Charter Members come June this year, with the first public beta likely to be around late October.
This was April 08, 2007, three years later we have release of 2.0 RC3 by the then Dev Aaron:
We are pleased to announce the immediate release of SMF 2.0 RC3 to the public. This version marks the third release candidate for 2.0, including about 350 new entries in the change log, consisting mostly of bug fixes, interface tweaks and fine-tuning of the new Curve theme.
We strongly recommend all users of earlier development releases to upgrade to this release, for it contains several security fixes.
While we are confident that there are no major problems with this release, we want to remind you that it is still not to be considered stable software. We do not recommend its use in live environments and if you are not comfortable with using this release candidate, we advise you to wait until the release of the final version before using the 2.0 line.
Highlights of this release include:
* Several security-related fixes.
* Better compatibility with RTL languages.
* Added curvy headers to loads of tables throughout SMF for the best Curve experience.
* Fine-tuned conversation view in the personal messages section.
* Improved read tracking of topics; e.g. topics are now marked as read by pages, to allow easier resuming of reading.
* Several tweaks to the WYSIWYG editor; now automatically disabled on mobile devices.
* Post screens (new topic, etc) are center aligned again.
* Buttons are now aligned much more consistently throughout SMF.
* Row color alternation to most of the tables in the administrative areas.
* Redesigned profile statistics centre.
* Fixed install and upgrade script for PostgreSQL.
* Updated help section.
* Revamped SSI examples page.
* Rephrasing of several error messages.
* Improvements to the package manager’s archive extraction algorithm.
* Toggling of full size versions of resized images.
* Altered styling for quotes and code blocks.
Those interested in the detailed changelog may like to download it from our download page.
Finally – please do not use this topic for any support requests. You will get a much more prompt response by visiting the relevant support board!
Its interesting every release has been a year or just over since it gets announced, what makes 2.0 so slow we should be on smf 3.0 now, not 2.0, I wonder is this to do with how the attitude in the team has changed, the little motivation that’s left in the team, even when I joined the team I saw issues between different cliches, but even at that smf 2.0 should be history, the software is getting outdated yet it is not even final yet … when will we get 2.1 at this rate it will be in 2015 another 5 years as 2.0 is still not even gold.