This task is to note that we want to have a code freeze for SecurePoll with the upcoming Board Elections. Please ONLY prioritize work that is extremely urgent. And please loop in @jrbs and @Niharika before doing so.
The dates for the freeze are set for September 1 until the election results are publicly released.
cc @Novem_Linguae @SD0001 as I think you've been working on a few tasks for the upcoming en election.
Thanks for the ping. If it's ok, will keep working until exact dates are given. I imagine we will want to buffer this by a week or more from the start of the vote to factor in how the train works.
At the moment we're looking at August 1 through September 10. If that will impact anything we're not aware of feel free to let us know.
Has this period changed due to the delay of the board election? Also, would it apply to maintenance work (dropping tables)? Context: T395928
Yes, sorry for the delay in updating here. I am anticipating it will move up to match, so will re-begin on 1 September.
Also, would it apply to maintenance work (dropping tables)? Context: T395928
No. My understanding is that the goal of the freeze is to prevent potentially breaking user-facing changes.
I don't think the board vote has started, so the freeze will probably be extended a few more weeks. Maybe @Niharika can confirm?
Board vote has indeed started! But I think generally we shouldn't push anything while that is open either, in case it causes a regression that impacts the results.
I'm going to assume the SecurePoll code freeze end date is when the BoT election results are published. That'll ensure that the tallier doesn't get broken by a code change.