<groupId>org.apache.maven.its.mng3843</groupId>
  <artifactId>parent-1</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <developers>
    <developer>
      <name>parent-developer</name>
    </developer>
  </developers>

## Design

Then I spent some time designing the developer "API" I wanted to have as a user (as a developer using FastAPI).

I tested several ideas in the most popular Python editors: PyCharm, VS Code, Jedi based editors.

By the last <a href="https://www.jetbrains.com/research/python-developers-survey-2018/#development-tools" class="external-link" target="_blank">Python Developer Survey</a>, that covers about 80% of the users.

  <groupId>org.apache.maven.its.mng3843.child</groupId>
  <artifactId>child-2</artifactId>
  <version>0.2</version>
  <packaging>jar</packaging>

  <developers>
    <developer>
      <name>child-developer</name>
    </developer>
  </developers>

<project>
    <modelVersion>4.0.0</modelVersion>
    <groupId>test</groupId>
    <artifactId>artifact</artifactId>
    <version>1.0</version>

    <developers>
        <developer>
            <organization/>
            <organizationUrl/>
        </developer>
    </developers>

[Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers,
see <https://min.io/docs/minio/linux/developers/minio-drivers.html> to view MinIO SDKs for supported languages.

OkHttp is **not** source-compatible for Kotlin callers, but upgrading should be automatic thanks to
Kotlin’s powerful deprecation features. Most developers should be able to use IntelliJ’s _Code
Cleanup_ for a safe and fast upgrade.


Backwards-Incompatible Changes
------------------------------

#### OkHttpClient final methods

    <developerConnection>developer-connection</developerConnection>
    <url>repository-url</url>
  </scm>

  <mailingLists>
    <mailingList>
      <name>Maven User List</name>
      <subscribe>subscribe</subscribe>
      <unsubscribe>unsubscribe</unsubscribe>
      <archive>archive</archive>
    </mailingList>
  </mailingLists>

  <developers>
    <developer>
      <name>Jason van Zyl</name>

      <roles>
        <role>Developer</role>
      </roles>
    </developer>
    <developer>
      <id>neildunn</id>
      <name>Neil Dunn</name>
      <roles>
        <role>Developer</role>
      </roles>
    </developer>
    <developer>
      <id>scarytom</id>
      <name>Tom Denley</name>
      <roles>
        <role>Developer</role>
      </roles>
    </developer>
  </developers>

  <modules>

    "license": "Apache-2.0",
    "title": "TensorFlow",
    "upload_type": "software",
    "creators": [
        {
            "name": "TensorFlow Developers"
        }
    ],
    "access_right": "open",

  unit and integration test changes).
    * The release managers may not know of all the features being worked on for an Istio release. Developers must
      make their case as to why their PR should be merged.
* Developers submitting PRs after the code freeze and after the first release candidate must provide justification