doc: clean up roadmap#20126
Conversation
maribu
added
Area: doc
| 1. ~~automated unit tests with hardware in the loop (SAMR21 plugged on CI server?)~~ (done, Murdock and Philipp) | ||
| 2. automated network functionality tests (e.g. RPL + UDP/PING tests through border router, multi-hop) in IoTLAB dev sites? | ||
| 3. ~~leverage PiFleet more?~~ done, 1. uses PiFleet | ||
| 4. On-board CI testing in IoT-LAB (as it will provide soon the possibility to add custom nodes) |
There was a problem hiding this comment.
@MrKevinWeiss and @miri: Could you take a look at what is done already here? Don't the automated release test cover this as well?
There was a problem hiding this comment.
If you want my feedback earlier, you need to mention @miri64 ;-). @miri got some very angry replies in the past.
And yes, the release test should cover this.
There was a problem hiding this comment.
@mirigot some very angry replies in the past.
Oopsie 😊
And yes, the release test should cover this.
Thx :-)
maribu
force-pushed
the
roadmap/cleanup
branch
from
e8b7689 to
f554978
Compare
|
Should we already migrate to the “vision” approach discussed during the VMA here? |
maribu
force-pushed
the
roadmap/cleanup
branch
from
f554978 to
f6f9d80
Compare
- drop completed tasks - drop tasks that make no sense anymore (e.g. cleanup up MIPS, as MIPS was dropped or improving xtimer, as it was superseded by ztimer)
maribu
force-pushed
the
roadmap/cleanup
branch
from
f6f9d80 to
e7e50ca
Compare
|
I also like the idea of adding a "Rust Support" area (but same comment as above, maybe this type of restructuring should go in a separate PR). |
I also, but let's have a separate PR for this :-) Maybe @chrysn and @kaspar030 could team up for this? |
|
oops wrong button |
I can relate. That happens to me a lot when I use the smartphone. Somehow the webpage layout keeps jumping and the button location changing while the website is not yet fully loaded. :-/ |
chrysn
left a comment
chrysn
left a comment
There was a problem hiding this comment.
Looks to me like all questions have been addressed -- and LGTM. As extensions are for later PRs, let's get this in.
|
Thx :-) |
7 participants
Contribution description
Testing procedure
Read the markdown and the generated HTML (see link posted by Murdock).
Issues/PRs references
None