Sure, will do. I will keep pushing new issues to the bitbucket tracker and update the WG once we get to something stable CI-wise.
Le mer. 3 mai 2017 à 16:22, Thomas Watteyne <[email protected]> a écrit : > Remy, > This looks great. I propose that we discuss particular issues directly > through the tracker rather than the ML, but would very much appreciate if > you could keep the WG updated with major developments. > Thomas > > On Wed, May 3, 2017 at 4:18 PM, Remy Leone <[email protected]> wrote: > >> No problem. >> I've activated the issue tracking and added a couple of issues: >> https://bitbucket.org/6tisch/td-6tisch/issues?status=new&status=open >> >> Let me know if I should move the issues somewhere else. >> >> Rémy >> >> Le mer. 3 mai 2017 à 16:12, Thomas Watteyne <[email protected]> a >> écrit : >> >>> That sounds great. Having a CI keeping an up-to-date version of the PDF >>> version at all times seems like the best of all worlds. Thanks for doing >>> the conversion exercise! >>> >>> On Wed, May 3, 2017 at 3:21 PM, Remy Leone <[email protected]> wrote: >>> >>>> I would like to use the one that Carsten used. I've sent him an email >>>> asking for this tool but I'm still waiting for the answer. >>>> >>>> >>>> Le mer. 3 mai 2017 à 15:18, Thomas Watteyne <[email protected]> >>>> a écrit : >>>> >>>>> This is great! I assume there are plenty of tools which will turn the >>>>> yml files into e.g. a PDF version of the TD? >>>>> >>>>> On Wed, May 3, 2017 at 3:06 PM, Remy Leone <[email protected]> >>>>> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I've just pushed a first version of the 6TiSCH test description in >>>>>> the following repository: >>>>>> >>>>>> https://bitbucket.org/6tisch/td-6tisch >>>>>> >>>>>> I've used the content present in the test description document >>>>>> provided by ETSI during 6TiSCH plugtest events. >>>>>> >>>>>> Using a git-based workflow to change those test descriptions will I >>>>>> think help a great deal in the implementation of automated conformance >>>>>> and >>>>>> interoperability testing. >>>>>> >>>>>> Feel free to start opening pull requests with new tests or >>>>>> corrections of existing ones for the upcoming plugtest event. >>>>>> >>>>>> I would also appreciate if you could help me to distinguish between >>>>>> obsolete and relevant tests. From what I understood, some tests needs to >>>>>> be >>>>>> updated or removed. >>>>>> Also, it would help to change the reference those tests are based >>>>>> upon (minimal-11, minimal-14, minimal-15). >>>>>> >>>>>> Best regards >>>>>> >>>>>> Rémy >>>>>> >>>>>> _______________________________________________ >>>>>> 6tisch mailing list >>>>>> [email protected] >>>>>> https://www.ietf.org/mailman/listinfo/6tisch >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> _______________________________________ >>>>> >>>>> Thomas Watteyne, PhD >>>>> Research Scientist & Innovator, Inria >>>>> Sr Networking Design Eng, Linear Tech >>>>> Founder & co-lead, UC Berkeley OpenWSN >>>>> Co-chair, IETF 6TiSCH >>>>> >>>>> www.thomaswatteyne.com >>>>> _______________________________________ >>>>> >>>> >>> >>> >>> -- >>> _______________________________________ >>> >>> Thomas Watteyne, PhD >>> Research Scientist & Innovator, Inria >>> Sr Networking Design Eng, Linear Tech >>> Founder & co-lead, UC Berkeley OpenWSN >>> Co-chair, IETF 6TiSCH >>> >>> www.thomaswatteyne.com >>> _______________________________________ >>> >> > > > -- > _______________________________________ > > Thomas Watteyne, PhD > Research Scientist & Innovator, Inria > Sr Networking Design Eng, Linear Tech > Founder & co-lead, UC Berkeley OpenWSN > Co-chair, IETF 6TiSCH > > www.thomaswatteyne.com > _______________________________________ >
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
