HI,
> Some of the information are kind of overlapping in all three files,
> I'm a little confused what to add where.
> All the incenses information are in the LICENSE file, what should go
> to the DISCLAIMER?
DISCLAIMER include the disclaimer and lists any issues that the user should be
aware of
Some of the information are kind of overlapping in all three files,
I'm a little confused what to add where.
All the incenses information are in the LICENSE file, what should go
to the DISCLAIMER?
I moved both "FAT long file names" and tools/ under NOTICE. Or do you
think we should remove the "too
Hi,
> First thing is to created DISCLAIMER, LICENSE and NOTICE files.
> I created a draft PR
> (https://github.com/apache/incubator-nuttx/pull/392) where I added
> these files.
> Please check it and share your thoughts.
I’d like to see more than just "* Releases may have incomplete licensing
con
Hi,
The release process is:
- Create an release candidate and vote on the release on this list
- If that vote passes then ask the IPMC to vote on the release on the
general@incubator list
A vote passes if you get 3 or +1 votes and more +1 votes than -1 votes. A -1
vote is not a veto. Only (P)PM
I'm still happy to do this. I have just not been available the last few
weeks. I'll set aside some time this weekend though to at least get the
disclaimer and notice in, as well as some low hanging fruit around the
license headers.
--Brennan
On Thu, Feb 27, 2020, 3:16 AM Xiang Xiao wrote:
> As
On Thu, Feb 27, 2020 at 5:43 PM Abdelatif Guettouche
wrote:
>
> > but we need to determine how
> > many minimum PPMC / IPMC signatures are required to release.
> Do we need to determine the number of signatures? Doesn't the RM's
> signature suffice?
> (I believe I read this in the documentation, b
> but we need to determine how
> many minimum PPMC / IPMC signatures are required to release.
Do we need to determine the number of signatures? Doesn't the RM's
signature suffice?
(I believe I read this in the documentation, but it's kind of hard to
go back and retrieve the relevant article).
The
On Thu, Feb 27, 2020 at 8:55 AM Gregory Nutt wrote:
> The existing ChangeLog and ReleaseNotes files will not be maintained;
> they may as well be deleted as well.
I don't understand. Don't projects usually have a CHANGES file and
release notes? We should tell people what's so great about this
rel
On Thu, Feb 27, 2020 at 8:15 AM Abdelatif Guettouche
wrote:
> We also need to define our release process.
> Something like:
> Create a branch from master that will serve as a release candidate.
> Make the necessary modifications in preparation of a release (update
> release notes, documentation, e
not build yet. I thought in the past ALL the builds were built
> before a release.
>
>
> -Original Message-
> From: Abdelatif Guettouche [mailto:abdelatif.guettou...@gmail.com]
> Sent: Thursday, February 27, 2020 6:10 AM
> To: dev@nuttx.apache.org
> Subject: Re: Pr
However, we can make progress by taking care of some of Apache's requirements.
Justin, summarized what we should do in an earlier thread. [1]
First thing is to created DISCLAIMER, LICENSE and NOTICE files.
I created a draft PR
(https://github.com/apache/incubator-nuttx/pull/392) where I added
t
Guettouche [mailto:abdelatif.guettou...@gmail.com]
Sent: Thursday, February 27, 2020 6:10 AM
To: dev@nuttx.apache.org
Subject: Re: Progress on making a release
With the nightly build in place, we would want to wait for some clean
builds to consider a release.
We want to make sure that the code is stable
With the nightly build in place, we would want to wait for some clean
builds to consider a release.
We want to make sure that the code is stable enough.
However, we can make progress by taking care of some of Apache's requirements.
Justin, summarized what we should do in an earlier thread. [1]
Fir
As I remember correctly, Brennan want to take the release manager role
to finish the first release.
On Thu, Feb 27, 2020 at 9:24 AM Nathan Hartman wrote:
>
> On Wed, Feb 26, 2020 at 8:05 PM Justin Mclean
> wrote:
> > Where is the project at in moving forward to make it’s next release?
>
> I thi
On Wed, Feb 26, 2020 at 8:05 PM Justin Mclean wrote:
> Where is the project at in moving forward to make it’s next release?
I think we should begin to plan our release procedures and release schedule.
The first thing we need is a Release Manager (RM). This need not be a
fixed role; we could have
Hi,
Where is the project at in moving forward to make it’s next release?
Thanks,
Justin
16 matches
Mail list logo
