Wondering if this will always be free? See why free is better.
Started by Colin, May 31, 2017, 09:21:59 PM
Quote from: Bigguy on December 17, 2018, 08:00:12 PMIt's close. Of course this could change in a minute or two as well, lol. For now though the milestones look good:https://github.com/SimpleMachines/SMF2.1/milestones
Quote from: landyvlad on December 21, 2018, 12:33:40 AMCoolio! Nice Christmas present maybe.
Quote from: Sesquipedalian on December 21, 2018, 04:02:12 PMQuote from: landyvlad on December 21, 2018, 12:33:40 AMCoolio! Nice Christmas present maybe. * Sesquipedalian points at signature.
Quote from: Bigguy on December 21, 2018, 10:10:02 PMChecking that the list of things to be done for that version is actually completed and there are as few bugs as possible. Changing the version in the files and maybe a few more checks here and there. I would guess. This is just what I think but who knows what the Devs will do before releasing.
Quote from: CoreISP on December 22, 2018, 09:49:08 AMWhen a version is (close to) being ready for release, there's several things we do in a release process.Over the years the policy has changed to be a bit more rigorous as we had a couple of releases that had mistakes. Admittedly, sometimes sloppy mistakes that could have been prevented by taking more time testing the packages - which we acknowledged and promised to do better.In general when a release is imminent: all kinds of tests start happening. A few examples are checking if the packages build OK on the server, checking if language packs are generated (properly) and of course packages are created for internal use with what we think will become the release. This package is distributed to the team and a couple of member groups so that the installation, upgrade and patches (if applicable) can be tested for errors; both during install as issues that come up (shortly after) installing it. If errors occur that are actually caused by our code, they are fixed and an updated package is created to test it again. If there are no issues, we proceed. So when we're happy: fireworks start, hymns are sung, the servers shake in terror and beg the sysadmins to save them for what is about to come - and the release is actually made to the public. There's a lot more stuff/testing that is being done (by various teams, not just devs!), but this is one of the most fundamental examples about what's going on behind the scenes during a planned release of a new version. This way we try to ensure, even for beta/RC releases, there are no (significant) issues with installing/upgrading.So there's quite a lot happening in the background for each release and there's a good amount of testing taking place.
Quote from: Sesquipedalian on December 23, 2018, 02:28:16 AMJust to be clear, folks, CoreISP's post merely describes in general the processes involved in creating a release. For anyone trying to read between the lines, the anticipated release date of RC1 in particular remains what it has always been: when it's ready.
Quotethe anticipated release date of RC1 in particular remains what it has always been: when it's ready.
Quote from: Bigguy on December 24, 2018, 03:29:33 PMSince it was marked RC1 about 20 more bugs were found. It will not be out I would think until they are resolved.
Quote from: Bigguy on December 24, 2018, 07:32:55 PMSorry about that. What he said.