On 4/12/19 5:58 pm, Sebastian Huber wrote:
> On 04/12/2019 04:25, Chris Johns wrote:
>> On 3/12/19 5:01 pm, Sebastian Huber wrote:
>>> On 03/12/2019 00:06, Chris Johns wrote:
> The first use of Doorstop is done in the new build system. I will update
> the
> documentation to mention thi
On 04/12/2019 04:25, Chris Johns wrote:
On 3/12/19 5:01 pm, Sebastian Huber wrote:
On 03/12/2019 00:06, Chris Johns wrote:
The first use of Doorstop is done in the new build system. I will update the
documentation to mention this Doorstop release. I will use it to generate the
fingerprints of t
On 3/12/19 5:01 pm, Sebastian Huber wrote:
> On 03/12/2019 00:06, Chris Johns wrote:
>>> The first use of Doorstop is done in the new build system. I will update the
>>> documentation to mention this Doorstop release. I will use it to generate
>>> the
>>> fingerprints of the items.
>> Do we need t
On 03/12/2019 00:06, Chris Johns wrote:
The first use of Doorstop is done in the new build system. I will update the
documentation to mention this Doorstop release. I will use it to generate the
fingerprints of the items.
Do we need to capture Doorstop in our future releases? If so how? We have
On 2/12/19 6:41 pm, Sebastian Huber wrote:
> Doorstop is the requirements management tool intended to be used for the
> technical specification of RTEMS.
>
> This weekend, Doorstop 2.0.post2 was released:
>
> https://pypi.org/project/doorstop/2.0.post2/
>
> I contributed 63 change sets to Doorst
Hello,
Doorstop is the requirements management tool intended to be used for the
technical specification of RTEMS.
This weekend, Doorstop 2.0.post2 was released:
https://pypi.org/project/doorstop/2.0.post2/
I contributed 63 change sets to Doorstop in the last five months. This
release conta
