Can someone please https://github.com/apache/otava/pull/92? I have started working on a new release and it is the only known blocker so far.
Best, Alex On Sun, Sep 14, 2025 at 4:37 PM Alexander Sorokoumov < [email protected]> wrote: > As a status update, I want to do this one last release before passing the > torch to use it for documenting all steps. I also want to add publishing a > Docker image to the process and, if the past is a predictor of the future, > it may require some tweaking. > > Best, > Alex > > On Sat, Sep 6, 2025 at 11:18 AM Alexander Sorokoumov < > [email protected]> wrote: > >> Unfortunately, new config parsing broke PostgreSQL importer - >> https://github.com/apache/otava/issues/88.We should fix it before >> releasing (and invest into e2e tests). >> >> On Wed, Sep 3, 2025 at 4:55 AM Joe Drumgoole <[email protected]> >> wrote: >> >>> Invoke is the perfect tool to encode the release process :-) >>> >>> Have you worked out I am an invoke fan yet? >>> >>> >>> Joe Drumgoole >>> >>> +087 2995547 >>> https://bsky.app/profile/joedrumgoole.com >>> >>> >>> >>> On Wed 3 Sept 2025, 12:42 Henrik Ingo, <[email protected]> wrote: >>> >>> > Releasing often is good. >>> > >>> > Do you feel you want to refine your skills there or maybe invest in >>> more >>> > automation / scripting there and do another release? Otherwise it >>> would be >>> > better for me or Sean to do it, so that we fullfil the incubator goal >>> where >>> > several committers know the release process. (I don't have time for the >>> > next week though.) >>> > >>> > henrik >>> > >>> > On Wed, Sep 3, 2025 at 5:49 AM Alexander Sorokoumov < >>> > [email protected]> wrote: >>> > >>> > > I don't mind making a minor release. What do others think? >>> > > >>> > > Best, >>> > > Alex >>> > > >>> > > On Tue, Sep 2, 2025 at 8:57 AM Joe Drumgoole <[email protected]> wrote: >>> > > >>> > > > Definitely worth a new release to push Sean's changes into a public >>> > > > release. >>> > > > >>> > > > On Sat, Jul 5, 2025 at 12:49 AM Alexander Sorokoumov < >>> > > > [email protected]> wrote: >>> > > > >>> > > > > With the PyPI fix merged in >>> https://github.com/apache/otava/pull/69, >>> > I >>> > > > > propose to cut 0.6.1 release now. What do you think? >>> > > > > >>> > > > > Best, >>> > > > > Alex >>> > > > > >>> > > > > On Thu, Jul 3, 2025 at 3:41 PM Alexander Sorokoumov < >>> > > > > [email protected]> wrote: >>> > > > > >>> > > > > > To my knowledge, the required change is 2 lines of code in >>> > > > project.toml. >>> > > > > > >>> > > > > > On Thu, Jul 3, 2025 at 3:21 PM Austin Bennett < >>> > > > > [email protected]> >>> > > > > > wrote: >>> > > > > > >>> > > > > >> If the code [ esp.] isn't changing vetting/shouldn't be >>> difficult. >>> > > > > Then, >>> > > > > >> you'd wind up having done 2 releases :-p >>> > > > > >> >>> > > > > >> On Thu, Jul 3, 2025 at 3:19 PM Alexander Sorokoumov < >>> > > > > >> [email protected]> wrote: >>> > > > > >> >>> > > > > >> > Hello everyone, >>> > > > > >> > >>> > > > > >> > We've got the first PyPi release >>> > > > > https://pypi.org/project/apache-otava/ >>> > > > > >> ! >>> > > > > >> > Unfortunately, we (I) missed special PyPI requirements to >>> > populate >>> > > > the >>> > > > > >> > project README, so the main project description is missing. >>> > > > > >> > >>> > > > > >> > Shall we fix this and immediately kickstart another release >>> > > (0.6.1?) >>> > > > > >> > that differs from 0.6.0 only by PyPI fix and minor README >>> fixes? >>> > > > > >> > >>> > > > > >> > Best, >>> > > > > >> > Alex >>> > > > > >> > >>> > > > > >> > On Sun, May 4, 2025 at 11:23 PM Mick Semb Wever < >>> [email protected] >>> > > >>> > > > > wrote: >>> > > > > >> > >>> > > > > >> > > I'm no expert here and haven't ever done it before. >>> > > > > >> > > Hoping someone can step in with more precise help. >>> > > > > >> > > >>> > > > > >> > > What I find is >>> > > > > >> > > - >>> https://incubator.apache.org/guides/distribution.html#pypi >>> > > > > >> > > - https://pypi.org/search/?q=apache-&o= >>> > > > > >> > > - >>> > > https://libcloud.readthedocs.io/en/latest/committer_guide.html >>> > > > > >> > > - https://issues.apache.org/jira/browse/INFRA-24678 >>> > > > > >> > > >>> > > > > >> > > >>> > > > > >> > > In the second latest link, I'm not sure of the missing >>> piece >>> > > > behind >>> > > > > >> (how >>> > > > > >> > > did the PMC first get access to the apache-libcloud pypi >>> > > project?) >>> > > > > >> > > > and send an email to [email protected] >>> requesting >>> > > to >>> > > > be >>> > > > > >> > added >>> > > > > >> > > as a maintainer to apache-libcloud package. >>> > > > > >> > > >>> > > > > >> > > The last link discusses the future. Interesting read. >>> I'd >>> > also >>> > > > > look >>> > > > > >> > into >>> > > > > >> > > the airflow project for examples, as they document things >>> > well. >>> > > > > >> > > >>> > > > > >> > > >>> > > > > >> > > >>> > > > > >> > > >>> > > > > >> > > On Mon, 5 May 2025 at 07:13, Alexander Sorokoumov < >>> > > > > >> > > [email protected]> wrote: >>> > > > > >> > > >>> > > > > >> > > > Successful internal vote result - >>> > > > > >> > > > >>> > > > https://lists.apache.org/thread/r6j7nr3ydo6ggpv9fkdfg6xl8btg38yj >>> > > > > >> > > > Incubator vote thread - >>> > > > > >> > > > >>> > > > https://lists.apache.org/thread/4dv29ghmky4h3v938moozwbt96dkfv3o >>> > > > > >> > > > >>> > > > > >> > > > While we are waiting for the incubator vote, does anyone >>> > know >>> > > > how >>> > > > > to >>> > > > > >> > > > release it to PyPI? Is there an official ASF account? If >>> > not, >>> > > > > which >>> > > > > >> > > account >>> > > > > >> > > > should we use? >>> > > > > >> > > > >>> > > > > >> > > > Best, >>> > > > > >> > > > Alex >>> > > > > >> > > > >>> > > > > >> > > > On Wed, Apr 9, 2025 at 8:00 AM Henrik Ingo < >>> > [email protected] >>> > > > >>> > > > > >> wrote: >>> > > > > >> > > > >>> > > > > >> > > > > I compiled all of these into >>> > > > > >> > https://github.com/apache/otava/issues/51 >>> > > > > >> > > > > >>> > > > > >> > > > > On Wed, Apr 9, 2025 at 8:55 AM Henrik Ingo < >>> > > [email protected] >>> > > > > >>> > > > > >> > wrote: >>> > > > > >> > > > > >>> > > > > >> > > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov >>> < >>> > > > > >> > > > > > [email protected]> wrote: >>> > > > > >> > > > > > >>> > > > > >> > > > > >> Thank you for the responses! I absolutely love the >>> idea >>> > > > for a >>> > > > > >> > > release >>> > > > > >> > > > > >> party. Let's do it after step 12 - IPMC Vote? >>> Henrik, >>> > Can >>> > > > you >>> > > > > >> > please >>> > > > > >> > > > > >> organize it? >>> > > > > >> > > > > >> >>> > > > > >> > > > > > >>> > > > > >> > > > > > Yes, that's how I thought about it too. >>> > > > > >> > > > > > >>> > > > > >> > > > > > >>> > > > > >> > > > > > >>> > > > > >> > > > > >> >>> > > > > >> > > > > >> Meanwhile, we are at currently at Step 4 - Verify >>> > > supported >>> > > > > >> Python >>> > > > > >> > > > > >> versions. I am going to finish this step this >>> weekend >>> > > (and >>> > > > > >> open a >>> > > > > >> > > > > >> discussion to switch from poetry and to uv, which >>> makes >>> > > > this >>> > > > > >> and >>> > > > > >> > > other >>> > > > > >> > > > > >> things easier). >>> > > > > >> > > > > >> >>> > > > > >> > > > > > >>> > > > > >> > > > > > My suggestion would be to just try to release with >>> > minimal >>> > > > > >> changes >>> > > > > >> > an >>> > > > > >> > > > > "ASF >>> > > > > >> > > > > > version" of what we have already been using from >>> > > > > datastax-labs. >>> > > > > >> > Then >>> > > > > >> > > > > after >>> > > > > >> > > > > > the inaugural versioin we can change python version, >>> > > tools, >>> > > > > >> > versions >>> > > > > >> > > of >>> > > > > >> > > > > pip >>> > > > > >> > > > > > packages... >>> > > > > >> > > > > > >>> > > > > >> > > > > > Btw I found there's a bot that keeps this list of >>> tasks >>> > we >>> > > > > must >>> > > > > >> > > > complete: >>> > > > > >> > > > > > >>> https://incubator.apache.org/clutch/otava.html#errata >>> > > > > >> > > > > > >>> > > > > >> > > > > > henrik >>> > > > > >> > > > > > >>> > > > > >> > > > > >>> > > > > >> > > > >>> > > > > >> > > >>> > > > > >> > >>> > > > > >> >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >>> > >>> > -- >>> > *nyrkio.com <http://nyrkio.com/>* ~ *git blame for performance* >>> > >>> > Henrik Ingo, CEO >>> > [email protected] LinkedIn: >>> > www.linkedin.com/in/heingo >>> > +358 40 569 7354 Twitter: >>> > twitter.com/h_ingo >>> > >>> >>
