Proposal to Update Project to Latest Chisel
chick opened this issue · comments
I'd like to propose the following.
- Make the current master branch become the release branch
- Make release be the default branch in this repo
- It will, for now, continue to point to its desired version of chisel3
- This would allow us to work on master, buffering existing users
- After the above change master branch
- Point to current 3.2-SNAPSHOT
- Fix all code to be compliant and as warning free as possible with Chisel 3.2
- put all code in main and tests into a
mini
package- This will bring it in line with standard Scala conventions
- Change master to depend on chisel-testers2 instead of chisel3
- This would allow us to develop some testers2 style unit tests
- This would help test out testers2 capabilities
- Provide alternative examples of unit testing facilities under chisel
- This would allow us to develop some testers2 style unit tests
@donggyukim Can you let me know what you think of this proposal.
I am prepared to do the described work and testing.
I am also interested in making sure Treadle can handle riscv-mini and this seems like a good path.
@chick I love this proposal. Can't wait to see tests running on Treadle! There used to be chisel-testers1.0-based tests, and I hope it'll be helpful for porting:
https://github.com/ucb-bar/riscv-mini/tree/6b889ec7ba5d72876f764532220725d49c49b912/src/test/scala
@donggyukim Thanks
As a first step I have created a release
branch. The only change from master was removing
the "-SNAPSHOT" from the version string in build.sbt
.
If this is ok with you I think the next steps should be
- Make
release
be the default branch - Make a release tag for
release
- Add protection rules to the
release
andmaster
branches to require PRs- I think this is optional but protects against accidental changes.
Does this sound ok? If so, I am happy to do them.
Yeah, it sounds good to me.