Re: RTEMS 5 Release status
On Tue, Apr 28, 2020, 7:28 PM Chris Johns wrote: > Hello, > > We are down to 4 remaining tickets. Many thanks to everyone for all the > hard work getting to this point. It is appreciated. > > The remaining tickets need to be closed or moved before I can branch the > repos. The milestone page is ... > > https://devel.rtems.org/milestone/5.1 > > ... so please have a look and help if you can. > > Release Change Notes > > > Joel has asked for a high level list of changes to be added to the > release information. He would like this to be a community effort. > > We have the detailed release notes created from the Trac tickets for the > release so this is suppose to be something high level. > > Please create or add to a file called rtems-notes-5.txt as markdown in > the releases repo ... > > https://git.rtems.org/rtems-release/ > > Either push the changes or send a patch to this list and I will merge > them. I will add support to place this text in the generated README once > it exists. If there is no file at the time of the release no support > will be added. > The type of high level info should include ports and BSPs added or removed, removed APIs, added APIs, some info on SMP changes, language support improvements, static objects, libdebugger, tracing, dynamic loading, testing improvements, and more. I'm hoping those most involved with the features can add that type of info. Let folks know what all goodness happened. > > Tickets > --- > > New: > > https://devel.rtems.org/ticket/3962 > > I will not be involved in this ticket or driving it and will wait for it > to be closed or moved before we branch. Please help. > I've posted a patch to this. You pointed out some minor issues that I will fix. If someone has something to say, please speak up. Otherwise, I hope to close it tomorrow. > Assigned: > > https://devel.rtems.org/ticket/2962 > > This ticket has no owner. Please review this ticket and help out. I > added to the comments that heapwalk with RTEMS_DEBUG fails. Is this > important? > The goal of this ticket is not a blocker. I would guess that debug enables the fence and that confuses heap walk. Heap walk plus debug is not a blocker. Move the ticket's milestone unless someone fixes it quick IMO. > https://devel.rtems.org/ticket/3813 > > I am working on this and should have it resolved soon. > Good. Two will close naturally. > Reopened: > > https://devel.rtems.org/ticket/3800 > > I do not know the status of this ticket or what should happen. > Sebastian needs to answer if his commit noted on the ticket resolved the issue. If so, it closes. If not, we need to decide if it is a blocker. --joel > > Thanks > Chris > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS 5 Release status
On 29/4/20 6:00 pm, Chris Johns wrote: Also I have currently backed away from a full markdown for the generated README.txt. It was creating some issues that require more work than is needed and it is not critical. It can be revisited as part of the on going support work. After saying I would back away from markdown for now I found the release notes with markdown valuable and so I have found a solution and have created a sample release note HTMl file for review. You can view it here for a short time before I delete the test release to stop search engines finding it and linking to it... https://ftp.rtems.org/pub/rtems/people/chrisj/releases/5/5.0.0/5.0.0-m2004-2/ Having an index.html means the paths to various pieces needed to be added so real links exists. You need pandoc on your machine to create these files when building a release. I will push a change to `rtems-bsp` in rtems.git so it generate the arch/bsp list in markdown so the list at the end can be created. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS 5 Release status
On 30/4/20 1:35 pm, Gedare Bloom wrote: Tickets --- New: https://devel.rtems.org/ticket/3962 I will not be involved in this ticket or driving it and will wait for it to be closed or moved before we branch. Please help. I will take care of this, but I don't see it as a blocker for release. Mostly it advocates for developer guidance so it is rather irrelevant to the release version. It literally says "for submissions" so it is about future-work. Bumping to 6, but thanks to Joel for raising this important concern. Thank you for doing this. I agree it is important and I appreciate your efforts working on this. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS 5 Release status
On Tue, Apr 28, 2020 at 6:28 PM Chris Johns wrote: > > Hello, > > We are down to 4 remaining tickets. Many thanks to everyone for all the > hard work getting to this point. It is appreciated. > > The remaining tickets need to be closed or moved before I can branch the > repos. The milestone page is ... > > https://devel.rtems.org/milestone/5.1 > > ... so please have a look and help if you can. > > Release Change Notes > > > Joel has asked for a high level list of changes to be added to the > release information. He would like this to be a community effort. > > We have the detailed release notes created from the Trac tickets for the > release so this is suppose to be something high level. > > Please create or add to a file called rtems-notes-5.txt as markdown in > the releases repo ... > > https://git.rtems.org/rtems-release/ > > Either push the changes or send a patch to this list and I will merge > them. I will add support to place this text in the generated README once > it exists. If there is no file at the time of the release no support > will be added. > > Tickets > --- > > New: > > https://devel.rtems.org/ticket/3962 > > I will not be involved in this ticket or driving it and will wait for it > to be closed or moved before we branch. Please help. > I will take care of this, but I don't see it as a blocker for release. Mostly it advocates for developer guidance so it is rather irrelevant to the release version. It literally says "for submissions" so it is about future-work. Bumping to 6, but thanks to Joel for raising this important concern. > Assigned: > > https://devel.rtems.org/ticket/2962 > > This ticket has no owner. Please review this ticket and help out. I > added to the comments that heapwalk with RTEMS_DEBUG fails. Is this > important? > > https://devel.rtems.org/ticket/3813 > > I am working on this and should have it resolved soon. > > Reopened: > > https://devel.rtems.org/ticket/3800 > > I do not know the status of this ticket or what should happen. > > Thanks > Chris > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS 5 Release status
On 29/4/20 3:57 pm, Sebastian Huber wrote: On 29/04/2020 02:28, Chris Johns wrote: Release Change Notes Joel has asked for a high level list of changes to be added to the release information. He would like this to be a community effort. We have the detailed release notes created from the Trac tickets for the release so this is suppose to be something high level. Please create or add to a file called rtems-notes-5.txt as markdown in the releases repo ... https://git.rtems.org/rtems-release/ Either push the changes or send a patch to this list and I will merge them. I will add support to place this text in the generated README once it exists. If there is no file at the time of the release no support will be added. I added the file based with some initial content https://git.rtems.org/rtems-release/tree/rtems-notes-5.txt Excellent and thanks. I will work on integrating them into the Release notes and release information (README.txt). Are the TBD areas to be resolved before the release? Also I have currently backed away from a full markdown for the generated README.txt. It was creating some issues that require more work than is needed and it is not critical. It can be revisited as part of the on going support work. on the 4.11 release notes https://devel.rtems.org/wiki/Release/4.11 We should create the notes for RTEMS 6.1 right after the 5.1 release. I have trouble to remember all the things which changed in the RTEMS 5 development cycle. It would be better to update the notes in parallel with the development. I am happy to see this happen. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS 5 Release status
On 29/04/2020 02:28, Chris Johns wrote: Release Change Notes Joel has asked for a high level list of changes to be added to the release information. He would like this to be a community effort. We have the detailed release notes created from the Trac tickets for the release so this is suppose to be something high level. Please create or add to a file called rtems-notes-5.txt as markdown in the releases repo ... https://git.rtems.org/rtems-release/ Either push the changes or send a patch to this list and I will merge them. I will add support to place this text in the generated README once it exists. If there is no file at the time of the release no support will be added. I added the file based with some initial content https://git.rtems.org/rtems-release/tree/rtems-notes-5.txt on the 4.11 release notes https://devel.rtems.org/wiki/Release/4.11 We should create the notes for RTEMS 6.1 right after the 5.1 release. I have trouble to remember all the things which changed in the RTEMS 5 development cycle. It would be better to update the notes in parallel with the development. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
RTEMS 5 Release status
Hello, We are down to 4 remaining tickets. Many thanks to everyone for all the hard work getting to this point. It is appreciated. The remaining tickets need to be closed or moved before I can branch the repos. The milestone page is ... https://devel.rtems.org/milestone/5.1 ... so please have a look and help if you can. Release Change Notes Joel has asked for a high level list of changes to be added to the release information. He would like this to be a community effort. We have the detailed release notes created from the Trac tickets for the release so this is suppose to be something high level. Please create or add to a file called rtems-notes-5.txt as markdown in the releases repo ... https://git.rtems.org/rtems-release/ Either push the changes or send a patch to this list and I will merge them. I will add support to place this text in the generated README once it exists. If there is no file at the time of the release no support will be added. Tickets --- New: https://devel.rtems.org/ticket/3962 I will not be involved in this ticket or driving it and will wait for it to be closed or moved before we branch. Please help. Assigned: https://devel.rtems.org/ticket/2962 This ticket has no owner. Please review this ticket and help out. I added to the comments that heapwalk with RTEMS_DEBUG fails. Is this important? https://devel.rtems.org/ticket/3813 I am working on this and should have it resolved soon. Reopened: https://devel.rtems.org/ticket/3800 I do not know the status of this ticket or what should happen. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS 5 release status
On 02/04/2020 11:10, Chris Johns wrote: > On 2020-04-02 20:02, Christian Mauderer wrote: >> Hello Chris, >> >> I don't think that littlevgl is such an essential or stable package yet. > > Sure. > >> Currently I know of exactly one project using this repository and that's >> only because I added it. > > I have used it successfully however not on RTEMS. It is great to use. > > Chris Yes, you pointed me toward it last year. It's a nice library. I meant that I know exactly one project using the rtems-littlevgl repository. In this project I'll most likely not use a release version but track the master instead. So I don't think that it's necessary to put effort into including rtems-littlevgl into this release. Best regards Christian -- embedded brains GmbH Herr Christian Mauderer Dornierstr. 4 D-82178 Puchheim Germany email: christian.maude...@embedded-brains.de Phone: +49-89-18 94 741 - 18 Fax: +49-89-18 94 741 - 08 PGP: Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS 5 release status
On 2020-04-02 20:02, Christian Mauderer wrote: Hello Chris, I don't think that littlevgl is such an essential or stable package yet. Sure. Currently I know of exactly one project using this repository and that's only because I added it. I have used it successfully however not on RTEMS. It is great to use. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS 5 release status
Hello Chris, I don't think that littlevgl is such an essential or stable package yet. Currently I know of exactly one project using this repository and that's only because I added it. Best regards Christian On 02/04/2020 11:00, Chris Johns wrote: > Hi, > > All OK and thanks for letting us know. > > I am not sure littlevgl is in the release. Maybe it should be? > > I am picking up packages via the RSB. > > Chris > > On 2020-04-02 19:03, Christian Mauderer wrote: >> Hello Chris, >> >> sorry, I missed that mail this morning. I pushed a small patch to >> rtems-littlevgl that fixes a build problem with python3. >> >> I hope I didn't make problems with that. >> >> Best regards >> >> Christian >> >> On 02/04/2020 01:31, Chris Johns wrote: >>> Hello, >>> >>> Please read if you have commit access. >>> >>> I am cleaning up a few issues like the release README.txt to match >>> moving all the released source in to `sources`, then updating the >>> documentation to reference this and then I will create a 5.0.0-m2004 >>> snapshot. >>> >>> After this I will be looking to make a branch so please wait for an ack >>> from Joel, Gedare or myself for any pushes to any repo. We are in a >>> slushy state to fix tickets. >>> >>> The sooner we clear the tickets from 5.1 the sooner I can create the >>> branch in the repos and the repos can be open again. >>> >>> You help is needed and welcomed. >>> >>> Thanks >>> Chris >>> >>> ___ >>> devel mailing list >>> devel@rtems.org >>> http://lists.rtems.org/mailman/listinfo/devel >> -- embedded brains GmbH Herr Christian Mauderer Dornierstr. 4 D-82178 Puchheim Germany email: christian.maude...@embedded-brains.de Phone: +49-89-18 94 741 - 18 Fax: +49-89-18 94 741 - 08 PGP: Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS 5 release status
Hi, All OK and thanks for letting us know. I am not sure littlevgl is in the release. Maybe it should be? I am picking up packages via the RSB. Chris On 2020-04-02 19:03, Christian Mauderer wrote: Hello Chris, sorry, I missed that mail this morning. I pushed a small patch to rtems-littlevgl that fixes a build problem with python3. I hope I didn't make problems with that. Best regards Christian On 02/04/2020 01:31, Chris Johns wrote: Hello, Please read if you have commit access. I am cleaning up a few issues like the release README.txt to match moving all the released source in to `sources`, then updating the documentation to reference this and then I will create a 5.0.0-m2004 snapshot. After this I will be looking to make a branch so please wait for an ack from Joel, Gedare or myself for any pushes to any repo. We are in a slushy state to fix tickets. The sooner we clear the tickets from 5.1 the sooner I can create the branch in the repos and the repos can be open again. You help is needed and welcomed. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS 5 release status
Hello Chris, sorry, I missed that mail this morning. I pushed a small patch to rtems-littlevgl that fixes a build problem with python3. I hope I didn't make problems with that. Best regards Christian On 02/04/2020 01:31, Chris Johns wrote: > Hello, > > Please read if you have commit access. > > I am cleaning up a few issues like the release README.txt to match > moving all the released source in to `sources`, then updating the > documentation to reference this and then I will create a 5.0.0-m2004 > snapshot. > > After this I will be looking to make a branch so please wait for an ack > from Joel, Gedare or myself for any pushes to any repo. We are in a > slushy state to fix tickets. > > The sooner we clear the tickets from 5.1 the sooner I can create the > branch in the repos and the repos can be open again. > > You help is needed and welcomed. > > Thanks > Chris > > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel -- embedded brains GmbH Herr Christian Mauderer Dornierstr. 4 D-82178 Puchheim Germany email: christian.maude...@embedded-brains.de Phone: +49-89-18 94 741 - 18 Fax: +49-89-18 94 741 - 08 PGP: Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
RTEMS 5 release status
Hello, Please read if you have commit access. I am cleaning up a few issues like the release README.txt to match moving all the released source in to `sources`, then updating the documentation to reference this and then I will create a 5.0.0-m2004 snapshot. After this I will be looking to make a branch so please wait for an ack from Joel, Gedare or myself for any pushes to any repo. We are in a slushy state to fix tickets. The sooner we clear the tickets from 5.1 the sooner I can create the branch in the repos and the repos can be open again. You help is needed and welcomed. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
