breaking change only impacts `tf.image.extract_glimpse` and
    `tf.compat.v2.image.extract_glimpse` API endpoints. The behavior of
    `tf.compat.v1.image.extract_glimpse` does not change. The behavior of
    existing C++ kernel `ExtractGlimpse` does not change either, so saved models
    using `tf.raw_ops.ExtractGlimpse` will not be impacted.

## Known Caveats

*   `tf.lite`

                        attachment semantics can be found in the documentation on the various
                        Route kinds ParentRefs fields). Listener or Route status does not impact
                        successful attachment, i.e. the AttachedRoutes field count MUST be set
                        for Listeners with condition Accepted: false and MUST count successfully

		{"(*Package).SetImports", Method, 5},
		{"(*Package).SetName", Method, 6},
		{"(*Package).String", Method, 5},
		{"(*PkgName).Exported", Method, 5},
		{"(*PkgName).Id", Method, 5},
		{"(*PkgName).Imported", Method, 5},
		{"(*PkgName).Name", Method, 5},
		{"(*PkgName).Parent", Method, 5},
		{"(*PkgName).Pkg", Method, 5},
		{"(*PkgName).Pos", Method, 5},
		{"(*PkgName).String", Method, 5},