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.

Sign up for GitHub

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

Jump to bottom

Properly Handle Expected use Cases #261

Open
2 tasks
ChristianTackeGSI opened this issue Jun 2, 2020 · 2 comments
Open
2 tasks

Properly Handle Expected use Cases #261

ChristianTackeGSI opened this issue Jun 2, 2020 · 2 comments
Milestone
next

Comments

@ChristianTackeGSI
Copy link
Member

ChristianTackeGSI commented Jun 2, 2020 •
edited
Loading

  • We should document all our expected use cases.
  • We should also make sure they work (maybe add CI jobs for them?).
  • We should make sure, that they're reasonably simple to use.

Major use case categories:

  • normal user install
  • developer build of one package (spack dev-build)

Childs:
@ChristianTackeGSI ChristianTackeGSI added this to the may20 milestone Jul 10, 2020
@ChristianTackeGSI
Copy link
Member Author

Part of the developer use case should have been addressed by #265.

This was referenced Jul 14, 2020
Closed
Open
@ChristianTackeGSI ChristianTackeGSI modified the milestones: nov20, next Nov 19, 2020
@ChristianTackeGSI
Copy link
Member Author

Moved to "next" milestone. Not going to handle spack related stuff NOW.

@dennisklein dennisklein modified the milestones: mar21, next Mar 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
next
Development

No branches or pull requests
5 participants
@dennisklein @fuhlig1 @MohammadAlTurany @kresan @ChristianTackeGSI