Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,846
    • Issues 1,846
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 86
    • Merge requests 86
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #18906

Closed
Open
Created Apr 01, 2019 by Cory Quammen@cory.quammenMaintainer

ParaViewTestingData-v?.?.?.tar.gz could use better name

We have two data packages produced during releases:

ParaViewTestingData-v5.6.0.tar.gz: contains the content store of ParaView's testing data ParaViewData-v5.6.0.tar.gz: contains the actual test data files named with their original names.

There are probably better names for these two items. I propose

ParaViewTestingContentStore-v5.6.0.tar.gz: for the test content store ParaViewTestingDataFiles-v5.6.0.tar.gz: for the data files that can be loaded directly.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking