<name>version</name>
          <version>3.0.0+</version>
          <description>
            <![CDATA[
            The version requirement of the dependency, e.g. {@code 3.2.1}. The actual version will be resolved based on the usage context.
            Version requirement can also be specified as a range of versions, e.g. {@code [3.2.0,)}. This is discouraged as it may break <i>predictability</i> of resolved version.

     * {@code SmbFile} refers to a workgroup, server, share, or directory,
     * the name will include a trailing slash '/' so that composing new
     * {@code SmbFile}s will maintain the trailing slash requirement.
     *
     * @return  The last component of the URL associated with this SMB
     *          resource or <code>smb1://</code> if the resource is <code>smb1://</code>
     *          itself.
     */

        }

        // Directories only support read leases
        if (isDir) {
            return Smb2LeaseState.SMB2_LEASE_READ_HANDLE;
        }

        // Determine lease level based on access requirements
        // Check for delete access separately as it may require special handling
        final boolean hasDeleteAccess = (access & DELETE) != 0;
        final boolean hasWriteAccess =

     * read operations in Map. For example, no operation can reveal that the table has grown but the
     * threshold has not yet been updated, so there are no atomicity requirements for this with
     * respect to reads.
     *
     * As a guide, all critical volatile reads and writes to the count field are marked in code
     * comments.
     */

- Introduced scheduling.k8s.io/v1alpha2 Workload and PodGroup API to allow for expressing workload-level scheduling requirements and let kube-scheduler act on those. Removed scheduling.k8s.io/v1alpha1 Workload API. ([#136976](https://github.com/kubernetes/kubernetes/pull/136976), [@tosi3k](https://github.com/tosi3k)) [SIG API Machinery, Apps, Auth, CLI, Cloud Provider, Etcd,...

     * read operations in Map. For example, no operation can reveal that the table has grown but the
     * threshold has not yet been updated, so there are no atomicity requirements for this with
     * respect to reads.
     *
     * As a guide, all critical volatile reads and writes to the count field are marked in code
     * comments.
     */