[debian-mysql] mysql 8.0 branch

[Lars Tangvald]

On 03/23/2017 03:41 PM, Robie Basak wrote:
> Hi Bjoern,
>
> I just noticed that you've branched for mysql 8.0 in VCS, but I don't
> remember you telling anyone about this.
>
> I presume you will watch and cherry-pick any changes pushed to 5.7
> master? If not, what is your plan? Who are you expecting to upload this
> when it is ready?
>
> We already had this happen once with the 5.7 upload where you appeared
> with own branch and we had to throw it all away because you hadn't
> coordinated it with anyone else. Let's make sure this doesn't happen
> again.
>
> Please can you not push things like "disabled non working patches for
> now" to the master branch? This stuff would be fine in an experimental
> personal branch. But if that sort of thing is necessary, I don't think
> it is suitable for a master branch that we all share. Consider the
> disabling tests that you did previously in this way, for example, that
> slipped through and caused other people extra work.
>
> I really feel that you could do a better job coordinating with the rest
> on the team on this. Please try and be more communicative.
>
> Thanks,
>
> Robie
Yes, please send a heads-up (though I should have noticed the new 
branch). The commits that are there look good to me, so I can add my own 
work onto it without any trouble, I think.
On the whole, the changes needed for 8.0 are pretty simple, as from a 
packaging perspective very little has changed from 5.7 (unlike 
5.6->5.7). Need to look through my local commits, but I think it was 
pretty much just changing 5.7 to 8.0 and doing updates for the changes 
in binaries built. The reason I didn't push my local work earlier is 
that 8.0.0 has a license issue reported by lintian:
We updated the rapidjson library, and the new version has some code 
under the non-free json license. We don't use any of this code, so we 
could patch it out, but since it'll be resolved upstream with the next 
dmr I decided to just wait for that.

--
Lars