RTEMS / RTOS / Release

Go to Issues or Merge Requests


Issues

3 - Update 5 release notes to indicate GDB needs (opened)

Id

3

State

opened

Type

ISSUE

Author

Chris Johns

Assignee(s)

Joel Sherrill

Created

2024-07-19T01:15:40.257Z

Updated

2024-07-19T01:15:40.257Z

Milestone

6.1

Link

https://gitlab.rtems.org/rtems/rtos/rtems-release/-/issues/3

Merges

0

The MR rtems/tools/rtems-source-builder!38 updates GDB to a version that only supports Python 3 and RTEMS 5 releases have allowed Python 2 or 3. Users will need to update their build environment to have Python 3 development libraries for the build to work. The release notes need to state this.

Author: Chris Johns

2024-07-19T01:15:40.407Z

assigned to @joel

1 - Review scripts to see if Gilab project automation is possible (opened)

Id

1

State

opened

Type

ISSUE

Author

Chris Johns

Assignee(s)

Chris Johns

Created

2024-06-13T02:02:03.619Z

Updated

2024-07-19T01:12:08.851Z

Milestone

6.1

Link

https://gitlab.rtems.org/rtems/rtos/rtems-release/-/issues/1

Merges

0

Currently the release scripts have a per version list of RTEMS package for a release. The Gitlab API lets us query and collect the RTEMS projects so this could be automated.

There may be complexity around this related to repos with submodules. If this is handled then creating a python command to return a list of repo URLs the release script could use would remove a painful configuration element when releasing.

Author: Chris Johns

2024-06-13T02:18:27.807Z

assigned to @chris

Author: Chris Johns

2024-06-13T02:02:03.678Z

assigned to @chris

Author: Chris Johns

2024-06-13T02:02:23.717Z

changed the description

Author: Chris Johns

2024-06-13T02:02:40.062Z

changed title from Review scripts to see is Gilab project automat{-at-}ion is possible to Review scripts to see is Gilab project automation is possible

Author: Chris Johns

2024-06-13T02:18:28.065Z

moved from chris/rtems-release#2

Author: Chris Johns

2024-07-19T01:12:08.951Z

changed title from Review scripts to see i{-s-} Gilab project automation is possible to Review scripts to see i{+f+} Gilab project automation is possible

2 - Add config.ini option to release script (opened)

Id

2

State

opened

Type

ISSUE

Author

Chris Johns

Assignee(s)

Chris Johns

Created

2024-06-13T01:57:09.901Z

Updated

2024-06-13T02:19:58.462Z

Milestone

6.1

Link

https://gitlab.rtems.org/rtems/rtos/rtems-release/-/issues/2

Merges

0

The release note generator uses the Gitlab API and this requires an API key. Update the release scripts to:

  1. Require a config.ini file be supplied or

  2. A JSON file of the milestone issues data used by the release generator

Author: Chris Johns

2024-06-13T02:19:52.330Z

assigned to @chris

Author: Chris Johns

2024-06-13T01:57:09.979Z

assigned to @chris

Author: Chris Johns

2024-06-13T02:19:52.598Z

moved from chris/rtems-release#1

Merge Requests

1 - Update the release notes to GitLab

Id

1

State

merged

Merged by

Amar Takhar

Merged at

2024-06-13T02:13:27.924Z

Assignee(s)

Chris Johns

Created

2024-06-13T01:33:46.510Z

Updated

2024-06-13T02:13:28.786Z

Milestone

6.1

Link

https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/1

Commit

b6f5b626aae1b50b6ac5b7ec3e35469ae6d074e6

Update the release notes to GitLab. The generator is Sphinx.

The issue for this work is https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5013

Author: Chris Johns

2024-06-13T01:33:46.701Z

assigned to @chris

Author: Chris Johns

2024-06-13T01:37:45.368Z

added 1 commit

  • 16e848b7 - Update the release notes to GitLab

Compare with previous version

Author: Chris Johns

2024-06-13T01:52:16.549Z

added 1 commit

  • b2ffb9fc - Update the release notes to GitLab

Compare with previous version

Author: Chris Johns

2024-06-13T01:52:53.164Z

added 3 commits

  • acc0505f - 1 commit from branch rtems/rtos:main

  • 540c0e1f - Remove trac files

  • b6f5b626 - Update the release notes to GitLab

Compare with previous version

Author: Amar Takhar

2024-06-13T02:13:24.439Z

approved this merge request

3 - Add merge requests to Release Notes (opened)

Id

3

State

opened

Assignee(s)

Chris Johns

Created

2024-07-28T06:59:29.403Z

Updated

2024-07-29T15:28:03.598Z

Milestone

6.1

Labels

doc

Link

https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/3

Commit

b94f50ba6daea49103e86a7124b6dbc0b233cf56

Add merge requests to the release notes.

Author: Chris Johns

2024-07-28T06:59:29.577Z

assigned to @chris

Author: Chris Johns

2024-07-28T07:00:11.107Z

You can view the HTML with Issues and Merge Requests here https://ftp.rtems.org/pub/rtems/people/chrisj/releases/test/html

Author: Amar Takhar

2024-07-28T23:49:57.343Z

Looks good but the HTML code when people are set to the rich text editor is coming through. I’m guessing it’s delimiting the HTML tags.

Scroll a bit down from here:

Author: Chris Johns

2024-07-28T23:49:57.309Z

This is not nice. The exported data has embedded HTML in it. Escaping the HTML is easy for HTML output but that does not work for PDF output.

Author: Amar Takhar

2024-07-28T23:52:48.766Z

It will have it based on whether the user is using the rich editor or not this is actually the normal way it works. The API probably has a way to know which editor the user used so you can base it off of that.

Author: Chris Johns

2024-07-28T23:54:25.429Z

It does not seem to be so in this case. It is from the rebasing of merge requests.

Author: Amar Takhar

2024-07-28T23:55:19.250Z

What do you mean? There is no way to tell if it’s rich or not? There are python libraries to strip HTML I would just do that then for non-html versions like PDF.

Author: Chris Johns

2024-07-29T02:25:05.235Z

The HTML is in automatically added notes as a result of rebasing the MR. No one entered it.

Author: Amar Takhar

2024-07-29T02:30:44.254Z

Ahh I see what you mean. It must use MarkDown or otherwise for the rich comments. Well that’s easily stripped you can convert it to monospace text using a python library to convert it and keep formatting.

Author: Kinsey Moore

2024-07-29T15:28:03.579Z

Was this change intentional? It seems like something that might have been changed during development for testing purposes.

2 - Update URLs to GitLab (opened)

Id

2

State

opened

Assignee(s)

Amar Takhar

Created

2024-07-27T04:39:11.971Z

Updated

2024-07-27T21:30:54.874Z

Milestone

6.1

Labels

doc

Link

https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/2

Commit

5c46b21d6dfed27c18ab8784ce756e8c34d1c714

Summary

Update URLs to GitLab

I didn’t touch the scripts because some of the logic needs to be changed since we have groups now.

Author: Amar Takhar

2024-07-27T04:39:12.150Z

assigned to @amar

Author: Kinsey Moore

2024-07-27T21:30:54.783Z

approved this merge request