Since the rc1 https://github.com/SimpleMachines/SMF2.1/milestone/6 is hard to follow
if a point is covered or not
i like to create this check list.
"Error Sources/Security.php" is not clear to me if it fixed or not.
legend:
No mark

mark

strike
text = pr is merged
at smf team feel free to edit by your self
Can we add this to RC as well? #1401
Much more important than the avatars issue IMO.
ask @colinschoen for me is this list only impoirtant to see if they covered by a pr or not
Can we add this to RC as well? #1401
Much more important than the avatars issue IMO.
Agreed. Added.
I've added #1178 to RC1 as well. We don't want to put out a release candidate that contains a way for people to bypass part of the permissions system.
This one always bothered me, & felt like it should be resolved before RC: Issue #2939 . force_ssl = 1 (login & reg only) doesn't work at all. It should either work, or the option should be eliminated.
Added.
I have a suggestion...
Before we officially tag the release as RC, can we have a few days' warning? I have a normal barrage of tests I run that I'd like to do once we think we're ready.
When Beta 3 came out, it felt to me like we had a flurry of activity, & then it was immediately released. But it had a few kinda big issues, we could have easily caught. I'd like to avoid that if we could for RC.
A few days of 'test only', then we could doc & prioritize bugs. Allow for possible regressions due to all of the updates.
My pov is that the talk is out of scope of this issue.
Create a own issue or create a topic with this questions.
@sbulen that should be discussed on team boards ideally. usually a release has to be scheduled/approved etc. so there should be notice posted there.
@colinschoen Seems like this is almost ready to go! Maybe you can have a look at the remaining PRs to get RC1 ready to release?
Update the list to get a better overview again
close this :octocat: ?
Most helpful comment
Agreed. Added.