Hey all,
So according to the plan from a couple weeks ago, tomorrow the 22th we
are going to be cutting the 9.1.0-R0 release and putting it up for a
vote. In the last couple weeks there has been a lot of moving bits on
master and we have not backported anything to the 9.1 branch. I have
done some
Hi,
I took care of the remaining PRs in the Projects' backlog. Only the
CI one is still there, we don't have any entry for CI related changes
in our release note template, I think we should add one.
With regards to bringing the release notes to the repo, that needs to
go to master then backporte
On Mon, Jun 22, 2020 at 7:01 AM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
>
> With regards to bringing the release notes to the repo, that needs to
> go to master then backported to the release branch. Are we all on the
> same page with this?
+1
We also need to update a cou
On Mon, Jun 22, 2020, 4:01 AM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> Hi,
>
> I took care of the remaining PRs in the Projects' backlog. Only the
> CI one is still there, we don't have any entry for CI related changes
> in our release note template, I think we should add o
With regards to bringing the release notes to the repo, that needs to
go to master then backported to the release branch. Are we all on the
same page with this?
+1
We also need to update a couple of documentation files to add any new
board, chip or architecture.
Yes, there is the STM32G4
On Mon, Jun 22, 2020 at 10:35 AM Gregory Nutt wrote:
> I created PR 1277 to add that to documentation:
> >
> > https://github.com/apache/incubator-nuttx/pull/1277
> The Confluence landing page needs to be updated too (usually not more
> than half dozen words).
>
Done. Thanks for the reminder.
I created a PR copying the release notes from Confluence to ReleaseNote file.
I did not copy the "Compatibility Concerns" part, that's valuable
information but I don't think it belongs to that file, just because
there is a lot of explanation and code snippets which are not well
suited for the templ
On Mon, Jun 22, 2020 at 4:46 PM Abdelatif Guettouche
wrote:
> I created a PR copying the release notes from Confluence to ReleaseNote file.
> I did not copy the "Compatibility Concerns" part, that's valuable
> information but I don't think it belongs to that file, just because
> there is a lot of
On Mon, Jun 22, 2020, 5:38 PM Nathan Hartman
wrote:
> On Mon, Jun 22, 2020 at 4:46 PM Abdelatif Guettouche
> wrote:
> > I created a PR copying the release notes from Confluence to ReleaseNote
> file.
> > I did not copy the "Compatibility Concerns" part, that's valuable
> > information but I don'
On Mon, Jun 22, 2020 at 10:13 PM Brennan Ashton
wrote:
> On Mon, Jun 22, 2020, 5:38 PM Nathan Hartman
> wrote:
>
> > On Mon, Jun 22, 2020 at 4:46 PM Abdelatif Guettouche
> > wrote:
> > > I created a PR copying the release notes from Confluence to ReleaseNote
> > file.
> > > I did not copy the "
> Hmmm... I believe that the whole point of Release Notes is to point
> out things like Compatibility Concerns that our downstream users and
> developers will want to know about before they attempt to update and
> learn the hard way that their code doesn't build or doesn't run
> correctly. But that
11 matches
Mail list logo