readme: project branching explained#1043
Open
peppelinux wants to merge 3 commits intoversione-correntefrom
Open
readme: project branching explained#1043peppelinux wants to merge 3 commits intoversione-correntefrom
peppelinux wants to merge 3 commits intoversione-correntefrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the IT-Wallet documentation to better explain the branching/LTS strategy and to improve README navigability by moving historical release tables into a dedicated release-history file.
Changes:
- Added a “Branching approach” section describing the dual-track strategy (
versione-correnteLTS vseudiwfuture development) and LTS scope. - Simplified the README “Releases” section to focus on the current stable release and link out to historical releases.
- Introduced
RELEASES-HISTORY.mdcontaining historical release tables and links.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| README.md | Adds branching/LTS documentation, updates ToC, and trims “Releases” to the current stable release + link to history. |
| RELEASES-HISTORY.md | New file that centralizes historical release tables and download links previously in the README. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request reorganizes and clarifies the release information and branching strategy for the IT-Wallet documentation. The main improvements are a clearer explanation of the branching approach, a concise summary of LTS support, and the extraction of historical release tables into a new dedicated file. This makes the
README.mdeasier to navigate and keeps release history well organized.Branching and LTS documentation:
README.mddescribing the dual-track branching strategy, detailing the distinction between the LTS (versione-corrente) and future development (eudiw) branches, as well as the transition plan to EUDIW compliance.Release information organization:
README.mdand into a new file,RELEASES-HISTORY.md, which now contains the full release history. TheREADME.mdnow links to this file for previous releases. [1] [2]README.mdtable of contents to include the new "Branching approach" section.Release tables and links:
RELEASES-HISTORY.md: Added tables listing all previous releases, including HTML and PDF links for both English and Italian versions, covering both the 1.x and early stage (pre-1.0.0) releases.