Re: Release 9.1
Abdelatif, I haven't tried my instructions on macOS... when I was first starting out, I got stuck, and switched to Linux. But I will give macOS a try again in the next few days, and update the instructions if I succeed. Good idea. Re: the release notes, maybe we can start using a template for PR text? That would make going through them easier. For instance: ### Bug or Feature? ### One line summary ### Impact ### Limitations / TODO ### Detail ### Testing If we had this filled out for every PR, it would make creating the Release Notes a lot easier. -adam On Wed, Jun 3, 2020 at 2:12 PM Abdelatif Guettouche < abdelatif.guettou...@gmail.com> wrote: > For the licensing, we are taking baby steps by changing only the files > that we know won't cause any issue. > I think we will continue to do that until we get the necessary ICLAs > then we can do a massive substitution. > But as have been said in the very beginning, this should not stop us > from making releases. > The most important part is that we make progress with each release. > We are definitely making progress technically, what Brennan is > referring to is the fact that IPMC members found it hard to build from > source. I think most of their issues came from not > installing/configuring kconfig-frontends which is in a separate > repository. > BTW, Adam, have you tried the steps of your companion in a fresh > installation of, say, macOS? That might be all we need. > > Generating release notes is the part that has the most painful work, > it took 4 of us last time to get it done. I still wonder if there is > a way to automate that, maybe with good PR summaries and consistent > labeling. > Nathan created a confluence page to prepare release notes for the 9.1 > ahead of time. > > On Wed, Jun 3, 2020 at 4:58 PM Adam Feuer wrote: > > > > Brennan, > > > > What, in your opinion, needs to be done to improve the onboarding > process? > > > > And what would you like to see happen to improve the licensing issues? > > Another pass through the files of another section (like we did with > sched) > > and updating headers? Or...? > > > > -adam > > > > On Wed, Jun 3, 2020 at 8:44 AM Brennan Ashton > > > wrote: > > > > > On Wed, Jun 3, 2020, 6:16 AM Gregory Nutt wrote: > > > > > > > Hi, all > > > > > > > > If we are serious about getting on a two month release cycle again, > now > > > > is the time to begin thinking about the 9.1 release. We created the > 9.0 > > > > release branch sometime before the 15th of April. We signed the > > > > release on April 23rd. So we have some time, but also we need to > start > > > > get some plans and organization in place. And we need to think about > > > > doing everything we can to make the master stable for that branch. > We > > > > should hold off large, sweeping changes until we get past that point. > > > > > > > > Duo... you mentioned that you were interested with assisted with the > > > > releases? Abdelatif was the point man last time. Perhaps you would > > > > want to discuss his experiences with him? > > > > > > > > Greg > > > > > > > > > > I would agree, but we have made zero progress on improving the > onboarding > > > process in terms of build and documentation, nor have we made progress > on > > > the licensing process. I'm not confident that the release would pass. > > > > > > I am also happy to share more on the steps of the actual release > process > > > outside of the release notes and branching (thank you Abdelatif that > was a > > > lot of work) if someone wants to take that on, or I can offer to do > that > > > portion again. I am happy to do it. It's a lot of little steps but > none of > > > them are that complicated. > > > > > > --Brennan > > > > > > > > > > > > > > > > -- > > Adam Feuer > -- Adam Feuer
Re: Release 9.1
For the licensing, we are taking baby steps by changing only the files that we know won't cause any issue. I think we will continue to do that until we get the necessary ICLAs then we can do a massive substitution. But as have been said in the very beginning, this should not stop us from making releases. The most important part is that we make progress with each release. We are definitely making progress technically, what Brennan is referring to is the fact that IPMC members found it hard to build from source. I think most of their issues came from not installing/configuring kconfig-frontends which is in a separate repository. BTW, Adam, have you tried the steps of your companion in a fresh installation of, say, macOS? That might be all we need. Generating release notes is the part that has the most painful work, it took 4 of us last time to get it done. I still wonder if there is a way to automate that, maybe with good PR summaries and consistent labeling. Nathan created a confluence page to prepare release notes for the 9.1 ahead of time. On Wed, Jun 3, 2020 at 4:58 PM Adam Feuer wrote: > > Brennan, > > What, in your opinion, needs to be done to improve the onboarding process? > > And what would you like to see happen to improve the licensing issues? > Another pass through the files of another section (like we did with sched) > and updating headers? Or...? > > -adam > > On Wed, Jun 3, 2020 at 8:44 AM Brennan Ashton > wrote: > > > On Wed, Jun 3, 2020, 6:16 AM Gregory Nutt wrote: > > > > > Hi, all > > > > > > If we are serious about getting on a two month release cycle again, now > > > is the time to begin thinking about the 9.1 release. We created the 9.0 > > > release branch sometime before the 15th of April. We signed the > > > release on April 23rd. So we have some time, but also we need to start > > > get some plans and organization in place. And we need to think about > > > doing everything we can to make the master stable for that branch. We > > > should hold off large, sweeping changes until we get past that point. > > > > > > Duo... you mentioned that you were interested with assisted with the > > > releases? Abdelatif was the point man last time. Perhaps you would > > > want to discuss his experiences with him? > > > > > > Greg > > > > > > > I would agree, but we have made zero progress on improving the onboarding > > process in terms of build and documentation, nor have we made progress on > > the licensing process. I'm not confident that the release would pass. > > > > I am also happy to share more on the steps of the actual release process > > outside of the release notes and branching (thank you Abdelatif that was a > > lot of work) if someone wants to take that on, or I can offer to do that > > portion again. I am happy to do it. It's a lot of little steps but none of > > them are that complicated. > > > > --Brennan > > > > > > > > > > -- > Adam Feuer
Re: Release 9.1
Brennan, What, in your opinion, needs to be done to improve the onboarding process? And what would you like to see happen to improve the licensing issues? Another pass through the files of another section (like we did with sched) and updating headers? Or...? -adam On Wed, Jun 3, 2020 at 8:44 AM Brennan Ashton wrote: > On Wed, Jun 3, 2020, 6:16 AM Gregory Nutt wrote: > > > Hi, all > > > > If we are serious about getting on a two month release cycle again, now > > is the time to begin thinking about the 9.1 release. We created the 9.0 > > release branch sometime before the 15th of April. We signed the > > release on April 23rd. So we have some time, but also we need to start > > get some plans and organization in place. And we need to think about > > doing everything we can to make the master stable for that branch. We > > should hold off large, sweeping changes until we get past that point. > > > > Duo... you mentioned that you were interested with assisted with the > > releases? Abdelatif was the point man last time. Perhaps you would > > want to discuss his experiences with him? > > > > Greg > > > > I would agree, but we have made zero progress on improving the onboarding > process in terms of build and documentation, nor have we made progress on > the licensing process. I'm not confident that the release would pass. > > I am also happy to share more on the steps of the actual release process > outside of the release notes and branching (thank you Abdelatif that was a > lot of work) if someone wants to take that on, or I can offer to do that > portion again. I am happy to do it. It's a lot of little steps but none of > them are that complicated. > > --Brennan > > > > -- Adam Feuer
Re: [OT] Linux now using 100 char lines as default
So sorry to be a radical humorist. I did not understand it was humor. A smiley face would have helped. Sorry. The chaos of this project is getting to me. Then, in that vein, why not just remove newlines altogether. ;) Each file can just be one long line.
Re: [OT] Linux now using 100 char lines as default
So sorry to be a radical humorist. I did not understand it was humor. A smiley face would have helped. Sorry. The chaos of this project is getting to me.
Re: [OT] Linux now using 100 char lines as default
So sorry to be a radical humorist. Sebastien Le 03/06/2020 à 15:57, Gregory Nutt a écrit : -1 I like it the way it is. And thoroughly opposed to increate the default line width. There has been BS talk about it. But it is just BS and amounts to nothing. No one should be taking this seriously. There has been no change to the coding standard. There has been no change to default line width. Any PR C file with 100, 128, or 132 character line with will be declined. Critical parts of the coding standard can be changed with a full vote of the PPMC. It is not going to happen by a few radicals commenting on an [OT] conversation.
Re: [OT] Linux now using 100 char lines as default
-1 I like it the way it is. And thoroughly opposed to increate the default line width. There has been BS talk about it. But it is just BS and amounts to nothing. No one should be taking this seriously. There has been no change to the coding standard. There has been no change to default line width. Any PR C file with 100, 128, or 132 character line with will be declined. Critical parts of the coding standard can be changed with a full vote of the PPMC. It is not going to happen by a few radicals commenting on an [OT] conversation. Any [VOTE] should also be preceded by a [DISCUSS] phase so that all people can express their preference. After all of the pros and cons are on the table in the [DISCUSS] and after we understand how this change would help and hurt other people, then it would be appropriate to start a [VOTE].
Re: [OT] Linux now using 100 char lines as default
-1 I like it the way it is. And thoroughly opposed to increate the default line width. There has been BS talk about it. But it is just BS and amounts to nothing. No one should be taking this seriously. There has been no change to the coding standard. There has been no change to default line width. Any PR C file with 100, 128, or 132 character line with will be declined. Critical parts of the coding standard can be changed with a full vote of the PPMC. It is not going to happen by a few radicals commenting on an [OT] conversation.
Re: [OT] Linux now using 100 char lines as default
-1 I like it the way it is. And thoroughly opposed to increate the default line width. There has been BS talk about it. But it is just BS and amounts to nothing. No one should be taking this seriously. There has been no change to the coding standard. There has been no change to default line width. Any PR C file with 100, 128, or 132 character line with will be declined. On 6/3/2020 7:39 AM, Sebastien Lorquet wrote: Or, Let's stick with usual console widths and make it 132? sebastien Le 01/06/2020 à 15:30, David Sidrane a écrit : Let's one up them and keep it binary at the same time 128! :) -Original Message- From: Alan Carvalho de Assis [mailto:acas...@gmail.com] Sent: Monday, June 01, 2020 4:22 AM To: dev Subject: [OT] Linux now using 100 char lines as default Interesting: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bdc48fa11e46f867ea4d75fa59ee87a7f48be144
Re: [OT] Linux now using 100 char lines as default
Or, Let's stick with usual console widths and make it 132? sebastien Le 01/06/2020 à 15:30, David Sidrane a écrit : Let's one up them and keep it binary at the same time 128! :) -Original Message- From: Alan Carvalho de Assis [mailto:acas...@gmail.com] Sent: Monday, June 01, 2020 4:22 AM To: dev Subject: [OT] Linux now using 100 char lines as default Interesting: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bdc48fa11e46f867ea4d75fa59ee87a7f48be144
Release 9.1
Hi, all If we are serious about getting on a two month release cycle again, now is the time to begin thinking about the 9.1 release. We created the 9.0 release branch sometime before the 15th of April. We signed the release on April 23rd. So we have some time, but also we need to start get some plans and organization in place. And we need to think about doing everything we can to make the master stable for that branch. We should hold off large, sweeping changes until we get past that point. Duo... you mentioned that you were interested with assisted with the releases? Abdelatif was the point man last time. Perhaps you would want to discuss his experiences with him? Greg
