search

conda-forge / wetterdienst-feedstock

A conda-smithy repository for wetterdienst.
BSD 3-Clause "New" or "Revised" License
3 stars 5 forks source link

Sharing maintenance work - first steps #53

Closed amotl closed 2 years ago

amotl commented 2 years ago

Dear Kai,

thank you very much for adding @gutzbenj and me as maintainers to this repository. As we have not been using Conda before too much, we may need some assistance.

For the matter of making a start, shall I just go ahead, and acknowledge the PR #45, in order to build and release Wetterdienst 0.39.0? I figure that the machinery will recognize my acknowledgement and conclude all further steps?

When all goes well, I will follow up with the same procedure for versions 0.40.0 and 0.41.0 as well? That sounds too easy to be true!?

With kind regards, Andreas.

kmuehlbauer commented 2 years ago

@amotl If you think only the latest version 0.41 is necessary you might just merge that PR, all others will be closed without creating these versions. Otherwise go ahead step by step.

amotl commented 2 years ago

Thank you. I will go ahead step by step. Maybe some people will need the dedicated versions to hunt for regressions of any kind. Good to have the whole history published then.

amotl commented 2 years ago

Hi again,

it looks like it will only work for newly created PRs. On #45, even after acknowledging, I don't see a merge button. Maybe those PRs already open can exclusively be acknowledged by you only?

image

Or our user memberships need more elevated permissions that would allow us to merge (manually)? This element shows a difference between our handles.

image

With kind regards, Andreas.

amotl commented 2 years ago

Oh boy. Is the content of the current CODEOWNERS file sane? It looks like it is lacking newlines.

amotl commented 2 years ago

Hi again,

as reported at https://github.com/conda-forge/wetterdienst-feedstock/pull/52#issuecomment-1201509919 ff., we might still need memberships with write permissions on the repository to be able to conclude the necessary steps like merging PRs.

With kind regards, Andreas.

amotl commented 2 years ago

Apologies. I missed the invitation to the repository delivery by email and GitHub apparently does not display it on the user interface in any meaningful way. I've just merged #45 and will continue doing so with the others, as planned.

Thanks again for your support!

amotl commented 2 years ago

Are there any guesses how long the staging process will take through the machinery to make the package visible on https://anaconda.org/conda-forge/wetterdienst, or where the progress might be able to be inspected publicly?

kmuehlbauer commented 2 years ago

It normally takes up to two hours to trickle through the CDN.

kmuehlbauer commented 2 years ago

@amotl Sorry for being not more in the loop yesterday. I'll elaborate a bit more on the foundations of conda-forge:

I'm having a hard time to understand which are required runtime dependencies of wetterdienst and which are optional. So the requirements run section in meta.yaml would need some expert eyes on it.

[1] - https://conda-forge.org/docs/maintainer/infrastructure.html#admin-web-services [2] - https://conda-forge.org/docs/maintainer/updating_pkgs.html#maintaining-packages [3] - https://conda-forge.org/docs/maintainer/updating_pkgs.html#updating-recipes [4] - https://conda-forge.org/docs/maintainer/updating_pkgs.html#rerendering-feedstocks [5] - https://conda-forge.org/docs/maintainer/pinning_deps.html [6] - https://conda-forge.org/docs/maintainer/conda_forge_yml.html

amotl commented 2 years ago

Dear Kai,

thank you for this extensive list of resources. I think I will be able to handle it after running some actions yesterday, also getting into a slight conversation with the regro-autotick-bot ;].

Thanks again for giving us permissions here, so we can maintain releases on our own behalf. I hope it will save you some time in the future.

For improving the list of runtime requirements, I've just created #57.

With kind regards, Andreas.