scheduler

Description

This will help users to know the airflow version a field or an endpoint was added.

We could do this by checking the changelogs of previous airflow versions and adding a release date to new fields/endpoints corresponding to that version.

Take a look at the dag_run_id below

![openapi](https://user-images.githubusercontent.com/4122866/138428156-e2690c7b-1c17-453c-9086-e6f6a

Issue from the Dagster Slack

[dagster_shell] defer environ copy to solid run time

This issue was generated from the slack conversation at: https://dagster.slack.com/archives/C01U954MEER/p1623181007055200?thread_ts=1623181007.055200&cid=

Is there a way to make a job re-occur N milliseconds after it finished previous time?

The tests fail sometimes due to millisecond based timing on some of the tests. I over optimized for local testing and it's causing tests to fail in CI occasionally. The CI pipeline is running in docker with limited resources, so not able to handle quite as precise time as my local machine.