Hi Julien and Jan, > -----Original Message----- > > > Somewhat related. When should we branch for the release and set > > > CONFIG_DEBUG=n? > > > > > > I think we would at least need a RC with CONFIG_DEBUG=n but IIUC we > > > usually do it at a point where the tree is nearly frozen. > > > > > > AFAICT, there are still a few things in flight (including fix for > > > XSA-409). So I am not sure we are in position yet to branch. Any opinions? > > > > +1 to it being too early to branch. I would suggest that the XSA batch > > should have gone in first and release blockers should have been dealt > > with (unless for some it is clear that they're going to be unintrusive), > > to limit what needs applying to staging and the new branch. > > I agree, therefore I think we can switch to CONFIG_DEBUG=n in the RC > next week after the Nov. 1 XSAs. So we have at least a week after the RC3. > > Does this sound ok?
Thank you both for the suggestions! Just in case I forget this...I saw the xenstore XSAs been merged yesterday, and hence may I please ask for a clarification if you are ok with the above plan so we can tag RC3 this week later after master branch is synced with smoke/staging? Also I think we need to submit a patch to make the default CONFIG_DEBUG to n in Kconfig? Thanks! Kind regards, Henry
