Closed MikeOpenHWGroup closed 1 year ago
@MikeOpenHWGroup thanks. I apologize for not being clear. I think it is best if milestone data for each core is grouped directly under it's own folder. For example the cv32e40p milestone data would go https://github.com/openhwgroup/programs/tree/master/Project-Descriptions-and-Plans/CV32E40P/Milestone-data/(all the data) In that way all the gate documents and milestone data for each core is in one spot.
the cv32e40p milestone data would go to
Project-Descriptions-and-Plans/CV32E40P/Milestone-data/
Done!
Updated directory structure.
programs
└── Project-Description-and-Plans
└── CV2E40Pv1
└── Milestone-data
├── README.md
├── templates
└── CV32E40P
├── README.md
├── Reports
│ ├── 2020-11-02
│ ├── 2020-etc....
│ ├── index.html
│ └── Waivers
└── RTL_Freeze_v1.0.0
├── DesignChecklist.md
├── ...other_checklists.md
└── Verification_openissues.md
As discussed in #592 this PR moves moves the
milestones
directory underProject-Description-and-Plans
. It also removes the redundantcv32e40p
directory undermilestones/CV32E40P/Reports
. The new directory structure is shown below: