New release

[drc38]

@proelke are we able to get a new release to Pypi to include the changes since May please?

[jainmohit2001]

@proelke @mdwcrft, can we expedite this process?

[proelke]

I am working on getting access to do so.

[jainmohit2001]

Hi @proelke, any significant updates here?

[mdwcrft]

Just catching up with this it looks like there's some clean up and testing to do with the latest 1.0.0 release and the 2.0.0-rc releases that were made. We'll talk to the old maintainers to check the status of all this then aim to release 2.0.0

[jainmohit2001]

Any updates guys? Can we plan the TODOs for 2.0.0?

[ajmirsky]

@jainmohit2001 I have some bandwidth this week and next (an beyond) to help with the release and other contributions. There are two pull requests: one for the additional docs and another for matching datatypes with the jsonschema. I went through the issues, and lots were requests for information, which I'll have a moment to respond to later today.

Do you have a recommendation of other tickets or items that you need help with?

[ajmirsky]

@mdwcrft can you enumerate the items that need clean up and testing for the 1.0.0 and the 2.0.0-rc releases. It'd help the community to contribute so we can continue improving on this great project!

[mdwcrft]

Maintainers will be having a call this Friday to assess the state of the releases and document steps to continue, I'll update here afterwards

[jainmohit2001]

I am laying down the tasks that should be completed before we go on to release the latest version.
Feel free to share your inputs here.

• Update Github releases to match with pypi releases
  @proelke @mdwcrft I have created drafts for the following. Please review them and publish them.
  • 1.0.0
  • 2.0.0rc0
  • 2.0.0rc1
  • 2.0.0rc2
• Automate github releases with tags along with pypi releases.
• Setup required docs on GitHub (Docs for the package #671)
• Automate docs releases to https://ocpp.readthedocs.io/en/latest/

[ajmirsky]

@jainmohit2001 The PR #688 should take care of item #2 on the list; it updates the publish-to-pypi.yaml workflow which, when triggered by whomever is releasing through the github ui or cli, will create the tag, release and push to pypi all based on the version in pyproject.toml

[ajmirsky]

@jainmohit2001 @proelke @mdwcrft will any of the pending PRs be evaluated as part of the next release? specifically, many of us are waiting on #680 (and #684 should be included to verify no breaking changes).

[ajmirsky]

@jainmohit2001 can you be more specific on what is remaining for #671 ? with PR #681 , I believe all of the required docs are now complete.

[jainmohit2001]

@jainmohit2001 The PR #688 should take care of item #2 on the list; it updates the publish-to-pypi.yaml workflow which, when triggered by whomever is releasing through the github ui or cli, will create the tag, release and push to pypi all based on the version in pyproject.toml

I'll consult with the admins to understand what kind of release flow should we go with.

[jainmohit2001]

@jainmohit2001 @proelke @mdwcrft will any of the pending PRs be evaluated as part of the next release? specifically, many of us are waiting on #680 (and #684 should be included to verify no breaking changes).

Will definitely include this. I'll go through all the changes once again.

[jainmohit2001]

@jainmohit2001 can you be more specific on what is remaining for #671 ? with PR #681 , I believe all of the required docs are now complete.

Need to update the information about supported versions. Will comment soon in the PR itself.

[mdwcrft]

@jainmohit2001 @proelke @mdwcrft will any of the pending PRs be evaluated as part of the next release? specifically, many of us are waiting on #680 (and #684 should be included to verify no breaking changes).

I'm preparing a 2.0.0 release today which may not include these but I can make another release this week with them once merged

[ajmirsky]

@jainmohit2001 @mdwcrft @proelke while we're all eager for a new release, I think it better to be thorough about what should be included in an official 2.0 release and waiting another day or two to make sure things like unit tests, correct datatypes for ocpp 2.0 actions, etc are very important to include.

[mdwcrft]

I was aiming to release 2.0 today and then 3.0 with the other changes later this/next week but if consensus is that it's fine to wait for 2.0 we can do that

[drc38]

I am laying down the tasks that should be completed before we go on to release the latest version. Feel free to share your inputs here.

• Update Github releases to match with pypi releases
  @proelke @mdwcrft I have created drafts for the following. Please review them and publish them.

  • 1.0.0
  • 2.0.0rc0
  • 2.0.0rc1
  • 2.0.0rc2

• Automate github releases with tags along with pypi releases.

• Setup required docs on GitHub (Docs for the package #671)

• Automate docs releases to https://ocpp.readthedocs.io/en/latest/

Deprecated values in enums.py also need to be removed before the release. See #694

[drc38]

Appreciate views on #506, the exceptions are an edge case and unlikely to occur in reality but it would be useful to have consensus and merge.

[drc38]

Is there a timeline to confirm what's in 2.0.0 and to publish?