Milestone: 1.0

[drewbanin]

This issue exists to track features, fixes, and changes required for dbt to hit version 1.0. All of the issues enumerated here should be labeled with the 1.0.0 issue label. When all of the issues attached here have been completed, we can cut a 1.0.0 release of dbt.

Changes

• Reconcile the SourceConfig (Reconcile SourceConfig #2273)
• Add blocks for all resources
  • Model blocks (model blocks #184)
  • Custom data test blocks (Custom data test blocks #2274)
  • Schema test definition blocks (Schema test blocks #1173)
  • Analysis blocks (Analysis blocks #2275)
  • Seed blocks (Seed blocks #2276)
• Rationalize test selection (Rationalize test selection #2203)
• Make materializations return complete/compiled SQL output
• Reconcile paths (Add an alias for source-paths configuration key #1607, Make default test-paths and analysis-paths configs consistent #2659)
• Move plugins out of dbt core and into separate repos (Split up adapters to encourage adapter-specific installation #3361)
  ... + more issues to come ....

[clrcrl]

Suggested additions from when I've been writing docs:

• Rationalize use of tags config / property (e.g. sometimes it's a config, sometimes it's in a schema.yml file which I'm calling a property henceforth): Set configs in schema.yml files #2401
• Make data and schema tests configurable from dbt_project.yml. Lack of support for configs in the dbt_project.yml makes it impossible to "turn off" a test in a package (I think?)
  • Currently you can't configure a data test from dbt_project.yml, though it can be from a {{ config() }} block.
  • You can't do either for a schema test.
• Make return type of custom schema tests and data tests consistent (number 0 versus 0 records)
• Allow data tests to be documented (everything else can, why not these?): [spike] Allow generic data tests to be documented #2578
• Rename different resource paths (test-paths to data-test-paths, source-paths to model-paths) — though it sounds like this paradigm is likely to change with different blocks?: Add an alias for source-paths configuration key #1607, Make default test-paths and analysis-paths configs consistent #2659
• Rename the source snapshot-freshness command to something that is less confusing (snapshot makes it sound like it is related to Snapshots, which it isn't): Parity for source freshness task/command #2987

[jtcohen6]

Closing now that v1.0.0rc1 is out in the world. We got to most of this, not all. If an idea is good enough, I trust it will have its time in the sun post-v1.