Skip to content

Add software development plan elements section - #3211

Closed
anmittag wants to merge 1 commit into
mainfrom
add-sw-dev-plan-needs-table
Closed

Add software development plan elements section#3211
anmittag wants to merge 1 commit into
mainfrom
add-sw-dev-plan-needs-table

Conversation

@anmittag

Copy link
Copy Markdown
Member

Added a section outlining software development plan elements.

Added a section outlining software development plan elements.

Signed-off-by: AndreasMittag <andreas.mittag@etas.com>
@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview for this pull request is available at:
pr-3211: https://eclipse-score.github.io/score/pr-3211/

@anmittag

Copy link
Copy Markdown
Member Author

components, documentation, and automated tests.

Software Development Plan Elements
----------------------------------

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to add the additional coding guidelines to the chapter with the coding guidelines. Same for additional references. I think this would make it more readable than a list at the end of the document with additional information. Appreciate the idea of making it complete!

@anmittag anmittag Aug 26, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@PandaeDo : Adding additional Chapters is fine, but how to ensure all Elements relevant for the Software Development plan is "added". Then I suggest to add the information as you requested AND having a Summary of all relevant SWDevPlan Elements at the end. Agree? Anyhow coding guideleines are already added Line 107ff.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's the main question. It's a responsibility of the maintenance of the plan(s). I think that's an improvement to check against them. So we'll get informed if there are changes. The list will be always updated. Even when you define a document that was defined to realise the plan. So I would agree on update the plan according to additional aspects and add the list at the end.

@anmittag

Copy link
Copy Markdown
Member Author

part of #3224 => can be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants