Hi Everyone,
I would like to propose that we branch the current master into a 5.0.x branch to track any additional changes required for the 5.0 release, and change the current master to target 5.1 so we can start to do some actual spec work.
This also brings up the question of what exactly will go into 5.1, what is the time frame we are looking at, and what will be our planning/release process in general going forward?
I was thinking in terms of planning and release timeframe we adopt an informal planning process based around group consensus. After a release has been done we send out an email asking for input on what should go into the next version, and what the timeframe would be. Once we have a general consensus we just make this publically available somewhere (github wiki maybe?), and start work. The aim of this planning process would be to set expectations based on timeframe and features, but it should not generally be used to to exclude any other additional work that is ready..
My feeling is that 5.1 should work on a relatively quick release cycle, with the main goal being to get the SameSite cookie support, with everything else we can include just being a bonus (everything else in this case likely being working through the issue backlog and attempting to clarify things).
Thoughts?
Stuart
