On 23/05/2019 08:44, Chris Johns wrote:
On 23/5/19 3:40 pm, Sebastian Huber wrote:
On 23/05/2019 07:35, Chris Johns wrote:
On 23/5/19 12:25 am, Sebastian Huber wrote:
We definitely need a repository to store the requirements files (Doorstop,
YAML). This is the first thing we have to know. If i
On 23/5/19 3:40 pm, Sebastian Huber wrote:
> On 23/05/2019 07:35, Chris Johns wrote:
>> On 23/5/19 12:25 am, Sebastian Huber wrote:
>>> We definitely need a repository to store the requirements files (Doorstop,
>>> YAML). This is the first thing we have to know. If it later turns out that
>>> the
On 23/05/2019 07:35, Chris Johns wrote:
On 23/5/19 12:25 am, Sebastian Huber wrote:
We definitely need a repository to store the requirements files (Doorstop,
YAML). This is the first thing we have to know. If it later turns out that the
choice was bad, we can still remove it from one repository
On 23/5/19 12:25 am, Sebastian Huber wrote:
> We definitely need a repository to store the requirements files (Doorstop,
> YAML). This is the first thing we have to know. If it later turns out that the
> choice was bad, we can still remove it from one repository and do a subtree
> import in another
Hello Joel,
On 22/05/2019 16:06, Joel Sherrill wrote:
Where to store the artifacts and what component to do first are
independent topics and should be on separate threads. I have changed
the subject.
On Wed, May 22, 2019 at 7:29 AM Ting Peng
mailto:ting.p...@embedded-brains.de>>
wrote:
Where to store the artifacts and what component to do first are independent
topics and should be on separate threads. I have changed the subject.
On Wed, May 22, 2019 at 7:29 AM Ting Peng
wrote:
> Hello,
>
> As to the requirements documentation, we need to decide a place to store
> those require
