Hi Adam,
I think once the workflow is complete we should froze the master and
keep accepting patch into dev branch. This is my point of view, I
don't know if we will implement it.
Also we need to review all the committed patch to the master to create
the Changelog/Release Notes. This should be th
> What needs to be done to move closer to release?
We still don't have a release process in place. We still haven't
completed our workflow actually.
It was expected to miss one release cycle, but we should've at least
completed the requirements by now.
It's not reasonable to consider an Apache re
Sorry late to reply here. I'm now working on Apache NuttX nightly build CI
setup. According to Greg's testbuild information provided,
now I'm preparing some CI scripts under
https://github.com/liuguo09/nuttx_testing to work with apache jenkins. Once
done and pass tests,
I'll make pull request to a
I think once the workflow is complete we should froze the master and
keep accepting patch into dev branch. This is my point of view, I
don't know if we will implement it.
I think we should create a release branch and freeze nothing. Versioning
will need to extend to 3 numbers, so the next wo
It was expected to miss one release cycle, but we should've at least
completed the requirements by now.
Yes, I am not surprised that we are missing the mid-January release.
But when will be do the release? I had been releasing code every two
months, with is already a long release cycle.
> On Jan 13, 2020, at 5:14 AM, Gregory Nutt wrote:
>
>
>> I think once the workflow is complete we should froze the master and
>> keep accepting patch into dev branch. This is my point of view, I
>> don't know if we will implement it.
>
> I think we should create a release branch and freeze
On Mon, Jan 13, 2020 at 2:12 PM David S. Alessio
wrote:
>
>
> > On Jan 13, 2020, at 5:14 AM, Gregory Nutt wrote:
> >
> >
> >> I think once the workflow is complete we should froze the master and
> >> keep accepting patch into dev branch. This is my point of view, I
> >> don't know if we will imp
The person that does the work should have the biggest vote. We have a
problem with too many Chiefs and not enough Indians now. Guidelines and
advice are great. Doing the job is greater.
On 1/13/2020 1:35 PM, Nathan Hartman wrote:
On Mon, Jan 13, 2020 at 2:12 PM David S. Alessio
wrote:
> On Jan 13, 2020, at 11:35 AM, Nathan Hartman wrote:
>
> On Mon, Jan 13, 2020 at 2:12 PM David S. Alessio
> wrote:
>
>>
>>
>>> On Jan 13, 2020, at 5:14 AM, Gregory Nutt wrote:
>>>
>>>
I think once the workflow is complete we should froze the master and
keep accepting patch in
HI,
> Sorry late to reply here. I'm now working on Apache NuttX nightly build CI
> setup. According to Greg's testbuild information provided,
> now I'm preparing some CI scripts under
> https://github.com/liuguo09/nuttx_testing to work with apache jenkins.
Why is this work being done outside of
Sorry late to reply here. I'm now working on Apache NuttX nightly build CI
setup. According to Greg's testbuild information provided,
now I'm preparing some CI scripts under
https://github.com/liuguo09/nuttx_testing to work with apache jenkins.
Why is this work being done outside of the ASF r
Hi,
> When should we do this first Apache release? How do we do this? Who is the
> release manager? (hint: not me) Since the breakage is coming on a daily
> basis, how/when can we get a stable enough system to even consider a release.
Af far as an Apache release is concerned there is a set o
Hi,
> Isn't that just a local clone of a fork of
> https://github.com/apache/incubator-nuttx-testing (which is currently empty
> other and a README).
There is nothing to indicate this, IMO it should be a fork or a branch.
For example if you look at [1] you can see it a fork of an ASF repo.
Th
Isn't that just a local clone of a fork of
https://github.com/apache/incubator-nuttx-testing (which is currently empty
other and a README).
There is nothing to indicate this, IMO it should be a fork or a branch.
Could be anything I suppose. I created the incubator-nuttx-testing
repositor
Forgive me, I'm just returning from a much-needed holiday break with family
and still trying to sort through 1400+ email msgs...
To Greg's point: how is it that master is broken? How did we allow any
merge that hadn't yet been checked (at least to compile, if not function)?
It seems to me that so
On Mon, Jan 13, 2020 at 4:31 PM David Alessio
wrote:
> Forgive me, I'm just returning from a much-needed holiday break with family
> and still trying to sort through 1400+ email msgs...
Good luck with that! That's rough. More below:
> To Greg's point: how is it that master is broken? How did
To Greg's point: how is it that master is broken? How did we allow any
merge that hadn't yet been checked (at least to compile, if not function)?
It seems to me that somewhere in our workflow discussion(s) we've
put Descartes before the horse.
We need help getting that workflow document finis
On Mon, Jan 13, 2020 at 4:03 PM Nathan Hartman
wrote:
> On Mon, Jan 13, 2020 at 4:31 PM David Alessio
> wrote:
>
> > Forgive me, I'm just returning from a much-needed holiday break with
> family
> > and still trying to sort through 1400+ email msgs...
>
>
> Good luck with that! That's rough. Mor
We need help getting that workflow document finished. Would you be able to
help with that?
Yes, I'd very much like to.
Nathan.. do you know how to give David access to Confluence? There is a
sign-up button at the upper right of the page. Is that all there is to
it? https://cwikapache.or
On Mon, Jan 13, 2020 at 4:24 PM Gregory Nutt wrote:
>
> >> To Greg's point: how is it that master is broken? How did we allow any
> >> merge that hadn't yet been checked (at least to compile, if not
> function)?
> >> It seems to me that somewhere in our workflow discussion(s) we've
> >> put Desc
The point I'd like to make, is that I'd much rather the whole world stop
turning, nothing get merged into master until we sort out the process;
rather than allow anything to break master. I'd like for us to adopt a
philosophy that "Nothing is worse than breaking Master." Now, that's just
me,
The point I'd like to make, is that I'd much rather the whole world stop
turning, nothing get merged into master until we sort out the process;
rather than allow anything to break master. I'd like for us to adopt a
philosophy that "Nothing is worse than breaking Master." Now, that's
just
Also, I think that the build was fixed late today. I have verified most
configurations. I had to submit several PRs today for build problems,
compile errors and new warnings, but I think we do, finally, have a
clean build. But I do need to re-verify everything from beginning to
end tomorrow.
Justin,
As Greg says, it's really little out of sync : (
Before incubator-nuttx-testing repository initialized with master to fork,
I did some prepare work in my own nuttx-testing project.
Now I have forked apache/incubator-nuttx-testing, I'll switch to my own
fork to do work and then make PR to wo
Hi,
> Haitao Liu is the person in charge of developing the automated workflow, but
> we will start off simple.
Why he may be doing the work it’s probably not correct from an ASF point of
view to say he’s in charge. Any contributor should be able to come along and
help out, make suggestion and
Then you have the same situation where Nuttx came fromhaving Greg be that
only person. The only difference is people had to see the 1400+ mails also
reading this “signal”.
So is this problem solved? Is there a “buddylist” where tasks are consolidated?
Ben
Verstuurd vanaf mijn iPhone
> Op
Hello Greg and all,
>I think we should create a release branch and freeze nothing. Versioning
>will need to extend to 3 numbers, so the next would be 8.4.0. Every
Though I still can not catch up with all email, in my understanding the next
version would be 8.3.0.
Actually http://www.nuttx.org/D
27 matches
Mail list logo
