Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare RELEASE v0.2 (May 2022) #580

Closed
1 of 15 tasks
hyunsik-yoon opened this issue May 10, 2022 · 4 comments
Closed
1 of 15 tasks

Prepare RELEASE v0.2 (May 2022) #580

hyunsik-yoon opened this issue May 10, 2022 · 4 comments

Comments

@hyunsik-yoon
Copy link
Contributor

hyunsik-yoon commented May 10, 2022

Let's list tasks of release 0.2 scheduled at the end of May.

Please revise the list or convert these into Github issues.

@hyunsik-yoon
Copy link
Contributor Author

hyunsik-yoon commented May 10, 2022

Backlog Candidate

Moved to #712 (comment)

Compilation

  • default options for compilation

Value test

  • value test UI
  • input/output data conversion/manipulation

Profiling

  • show target device profile data in UI

OneExplorer

  • define concept more specifically
    • e.g., What user can do? Are we going to provide file system handling, e.g., copy/del/rename?)
  • list OneExplorer's full feature
  • view menu for toggling intermediate files
  • show intermediate files from backend (e.g., tv2w)

onecc support

  • onecc support for backend (e.g., backend memory profiling tool)

toolchain

  • docker toolchain
  • when a new version is release, how are we going to notify users?
    • new version of backend extension which is not published in MS extensions server
    • new bersion of backend toolchain
  • what if user want to use toolchain 1.0.0 which does not have one-infer ?
    • show proper error and propose to use right toolchain version
    • how can we know right toolchain version x for ONE-vscode version y ?
  • what if toolchain ver introduce new param? How do we show toolchain list where old ones do not have new param? Is it OK to download old toolchain?

other

  • onecc cfg verification
    • when user has an existing wrong cfg file, one view may need to show some error icon on the cfg file.
    • when user clicks erroneous cfg file, what should we show in cfg editor? how can we pinpoint erroneous field?

SE

  • UI test
  • Process to deprecate old source files that are not used any more
  • internal SE process preparation

more customer

  • support circle user (user who download ONE-vscode only to try ONE)
  • ONERT users
    • prepare ONERT backend
    • create cfg file on OneExplorer for ONERT -> this will show cfg editor that has UI to invoke PartEditor ([CircleGraph] UI for one-partition #633)
    • Consider how to support 2-depth(?) backend
      • On CircleGraph, by clicking a node, user can select, e.g., CPU, GPU, NPU, etc. This means a concept like, e.g, 2-depth backend (depth 1: ONERT, depth 2: CPU, GPU, NPU, etc) needs to be supproted.

WIP

@hyunsik-yoon
Copy link
Contributor Author

@YongseopKim, it seemed that github automatically assigned you since this issue was originally created in Github project by you. So, I removed the assignee.

@hyunsik-yoon hyunsik-yoon pinned this issue May 10, 2022
@hyunsik-yoon
Copy link
Contributor Author

@Samsung/one-vscode
Please edit the above and add ✔️ or ❌. (✔️: doable in May or ❌: delay)

The following is image we wrote during the meeting, captured right before the crash of web browser. :-)

image

@hyunsik-yoon
Copy link
Contributor Author

This will be merged into June release.

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

No branches or pull requests

2 participants