Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: The E on January 10, 2017, 04:25:46 am
-
As you may have noticed if you've been following the activity on our github (or just have been keeping up with the nightly builds), there have been a lot of under the hood changes that went in late last year. The move to OpenGL core, SDL everywhere, integration of better video players, a new flag system and a massive reorganization of the way lua is integrated into the project, to name but a few.
Overall, these are all features that I feel make for a pretty compelling reason to call our next release 3.8, but releasing now would be foolish. As these changes are all fairly wide in scope, they've also been responsible for introducing quite a few bugs, and I feel like we need to spend at least a bit of time polishing things up.
To that end, beginning right now, the SCP will be entering into a code freeze. We will not be accepting pull requests for new features, and will concentrate on fixing the bugs currently present (no matter whether they're logged on github or the SCP Mantis). In order to sweeten this admittedly bitter pill, Goober has graciously offered to sponsor the following bounties:
For number of actual bugs fixed during this time period (not necessarily corresponding to issues closed on Mantis or GitHub):
$50 Amazon gift card for first place
$25 for second
$10 for third
Additionally:
$25 for anyone who successfully resolves 25 Mantis or GitHub tickets. (Successfully closing a ticket for some other reason, such as obsolete/duplicate/unreproduceable will earn half credit.)
$25 for anyone who successfully resolves GitHub issue #1051 (https://github.com/scp-fs2open/fs2open.github.com/issues/1051) This has been solved, thanks to AdmiralRalwood, m!m, and z64555.
The code freeze will last until April 1st. Then we'll officially go into the RC stage for 3.8 and release shortly thereafter.
Happy hunting!
EDIT: Added bounty for GitHub #1051 // Goober5000
-
Does the code-freeze mean we will get no further nightly builds until the RC process begins?
-
That seems silly, Trivial Psychic. Surely they'll put out nightlies for bug fixes so people can test them. He said feature freeze, not code freeze.
-
Does the code-freeze mean we will get no further nightly builds until the RC process begins?
No, IIRC the SCP disabled nightly builds during a feature freeze once (for 3.6.14?) and it was agreed in the aftermath that it had been a bad idea. Nightly builds continuing means that the bug fixes are more easily available to be tested.
-
He said feature freeze, not code freeze.
Er...
To that end, beginning right now, the SCP will be entering into a code freeze.
[...]
The code freeze will last until April 1st.
Your point is otherwise correct; we're not actually halting all development on the code, it's just that we're not currently interested in merging new features. As niffiwan said, nightly builds continuing to be available makes it a lot easier for people to test bug fixes.
-
Huh. My memory played a trick on me...
-
I only brought it up because I haven't seen a new nightly since the announcement, and wanted to have that suspicion confirmed or denied early. I know that its not uncommon for there to be periods without nightly builds, but again, the timing did give me pause.
On the subject of 3.8, I've noticed a lot of documentation in the Wiki pertaining to table files, and there's a lot of features listed as 3.8 compatibility. Does that mean that they are features currently in nightly builds?
-
There hasn't been any new commits since 7th Jan until today, so it was just coincidence. There should be a new nightly "tonight".
The features listed as requiring 3.8 compatibility are currently available in the nightly builds.
-
On the subject of 3.8, I've noticed a lot of documentation in the Wiki pertaining to table files, and there's a lot of features listed as 3.8 compatibility. Does that mean that they are features currently in nightly builds?
That's exactly what that means. Some time ago (couple months, I think?) I consolidated how FSO version templates worked on the wiki because sometimes features were marked according to the first version they appeared in, and sometimes they were marked according to the first stable release they appeared in. The latter makes way more sense than the former, so now all version templates are for non-nightly version numbers (so any features introduced in 3.7.5 are labeled as FSO 3.8 features).
-
Me too, I agree with AdmiralRalwood here in all parts here.
-
I've edited the first post to add an additional bounty for GitHub issue #1051 (https://github.com/scp-fs2open/fs2open.github.com/issues/1051).
EDIT: Solved!
-
One month remains to get your bugs squashed! Remember, some bounties are awarded competitively, but some bounties are paid out to all bug hunters who reach a certain threshold.
-
One thousand meters to go. Thirty seconds and counting!
-
The code freeze has come to a conclusion, and the 3.8 Release Candidate 1 (http://www.hard-light.net/forums/index.php?topic=93392.0) has been posted. In the next week or two I'll tally up the number of bugfixes and closed tickets and distribute the bounties. :yes: Thanks to everyone who participated!
-
Since we have not created a branch to separate 3.8 development yet, I'd like to point out that the code freeze needs to remain in effect for the time being.
-
Unstickied, we can start a thread for the next release if it is warranted. Perhaps even to cement exactly what version that next release will be.