I think thatās not a problem, I want this feature in 0.7.0.0 mainly so all pods with 0.7.0.0 or newer can understand that messages. I donāt expect anybody to use this feature from the start, because it would be only usable manually and I itās not officially supported that way. So if there is a bug, we can fix that in 0.7.1.0 and then only pods with 0.7.1.0 or newer can understand that message correctly. Itās the same as the new federation protocol is only fully compatible with 0.6.3.0 or newer, because 0.6.0.0 contained a bug with forward-compatibility.
It would be cool to have #71 merged before releasing, so if anybody has the time to have a look at it, that would be cool (@denschub or @comradesenya). Iāll create a release then.
One other issue related to the new release: is there anything which will need to be changed/updated in the tutorials, or elsewhere on the project site?
If so, let me know and Iāll try to take charge of this before the release date.
So, I think #6726 is nearly ready to merge \o/ But I saw that #6750 needs to be rebased and partly rewritten, so thatās probably some more work. When you fixed the remarks in #6726 and still have time, I think you can start with rebasing #6750 on top of #6726, even when I didnāt have the time to do the final review. Because I think #6726 is ready after fixing the last few things, and if there needs to be something changed again, it wonāt be something that breaks #6750 again, so I you can start working on that second PR without waiting for me to have time to approve the first PR
I donāt know how much time you have for your third open PR #7482 if there needs to be something fixed there (@svbergerem told us, heāll review that soon) , but I think we can find other people to finish that (@denschub or I) if needed. So you can focus on the migration PRs
I hope I can finish (and @denschub can review) rails 5 until the weekend, so we have some days before the freeze to test that and fix stuff if needed at the weekend.
Also:
If anybody of you wants to join the stream via mumble, itās probably a good idea to check if everything works before the stream. So I had the idea we can test that at the weekend and maybe do a little online hackathon to finish the last things needed for the freeze (I wanted to freeze sunday evening or monday). So please tell me if youāre interested, so we can find a time
I have already rebased and almost fully rewritten #6750 locally, I just didnāt push it in order to not creating mess in git (and the PR is in this state for months already). So Iāll push the new version just after you merge #6726.
Iāve started with the announcement of v0.6 last year, and have just started the process of updating it. So itās very rough at the moment, with a lot of the text from last year still in place. But itās there so anyone who wants can play with it.
Will go through the pulls in the 0.7.0.0 milestone and incorporate all the changes before asking you core guys for confirmation/comment.
So here is a small update what had been done and whatās still blocking the release:
So we have already merged #7482, #6726 and #7509. That are already 3 big things done, so huge thanks to everybody who helped with that! I also managed to get travis happy with #7514
But there is more to do
#7514 and #7182 need a review, @denschub told me, he can do that this weekend.
#6750 needs to be updated and reviewed, @comradesenya what is the state about this PR? I have the whole weekend time to review, so we can do quick cycles when there are changes needed.
#7519 needs to be done, @flaburgan what is the state of this?
I am confident that we can do this, and freeze soon (target is still sunday evening/night). When we can merge rails 5 this weekend, Iām fine when we need to delay the freeze for other things for 1-2 days, but I want to test rails 5 as long as possible, because itās the change where I see the highest risk of regressions even when travis is green.
Since the stream was announced without the release, we can do a silent freeze and donāt announce any release date. We can create a generic āthere were merged a few big things, please testā post. Then we can decide the day before the stream if we want to release during the stream or not (depending on how many bugs found). Or we could do a regular freeze and announce the release at the stream. What do you think?
I still work on it and I donāt think I can push it earlier than tomorrow evening. Of course I can push what Iāve done so far immediately, but Iām not sure it is useful to review it right now, since I still can move and change some code.
If you write what you plan to change (a list of planned todos in the PR description is enough), I can already review it, get used to the code/changes and see if I find something else. If you think itās in a too bad state, then you can also wait. I have no idea in what state it is If travis fails, thatās OK.
I added a general TODO list out of 4 points and pushed the present version of the PR. Feel free to comment, but some of the parts arenāt my final words
so if we manage to do the release, it will be a surprise-release? 
I also managed to get travis happy with 
