I figured this might be better to break off of the release discussion.
So Nathan has done an awesome job getting a start on the release notes for
9.1, but so far he has done all of the work and it is a little hard to see
where we have left off and to work together adding the content.
https://cwiki.
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
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 rel
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
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 2
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.
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.
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 serio
-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 defa
-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 defaul
-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 l
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
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
13 matches
Mail list logo
