NOT TO BE MERGED - JUST SHOWS DIFFERENCE from 4.0.2 to 4.0.3

[tghosth]

No description provided.

[ike]

This looks really great -- love the heading updates, removing "requirements" from headings, etc.

On that note, are there any links to specific headings that need to be updated based on these changes?

[tghosth]

I think any changes here should already be in bleeding edge, is that correct @elarlang ?

[cmlh]

@tghosth states

I think any changes here should already be in bleeding edge, is that correct @elarlang ?

To compare we could try an interactive rebase onto the bleeding edge/main branch before reviewing the conflicting commits that would occur as a result of an unplanned merge?

[elarlang]

On that note, are there any links to specific headings that need to be updated based on these changes?

I think any changes here should already be in bleeding edge, is that correct @elarlang ?

Changes from bleeding edge were ported to v4.0.3. So there should be no changes which exists in v4.0.3 but not in bleeding edge. (Maybe except one title change by Josh). Is that answer for your concern? or I just can not understand the question...

[elarlang]

And to be clear - the activity itself is not "git merge", it is manually updating content from bleeding edge to v4.0.3.

Each change need to be checked manually - for example, some requirements are moved and have new number in bleeding edge, we can not merge this change to patch release, as it's breaking change. At the same time, moved requirement text is updated, but we can update requirement text for old number for v4.0.3.