You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@otava.apache.org by Henrik Ingo <he...@nyrkio.com> on 2025/04/02 22:24:02 UTC
Re: Path towards the first Apache release
Thanks Alex!
I was operating under the assumption that everyone else here knows the
Apache process better than me, so I was hoping someone to start exactly
this email!
I have two additions:
- I suggest we do a zoom or teams release party? In fact, we could
literally do the svn commands together on such a call? I would invite
people who contributed over the years, all the way back to William Brown,
who wrote the first version of the algorithm during his last week as a
Summer intern at MongoDB. (And we never heard from him since but I recently
tracked him down on Linkedin.)
- I have written a paper on the evolution of performance improvements in
Otava from the beginning. I want to publish this partly as a homage to
everyone who improved it over the years. Spoiler:Original implementation
was literally what the e-divisive paper describes: O(n^3) and the next week
William himself improved to O(n^2). Last year I achieved constant time
(when adding a single point). In raw numbers the performance improvement is
about 300 thousand times faster :-) (Depends on amount of data and also
number of change points found.) Main performance improvements came from 4
different developers over 8 years.
- I might and probably should accompany the above with a more casual blog
post telling the history of Otava from MongoDB to Datastax to ASF. (And
other notable users too, of course.)
- I will be presenting at
https://icpe2025.spec.org/tracks-and-submissions/research-presentation-track/
on May 7-9. ICPE is the conference where both MongoDB and Datastax
primarily published papers on Otava / Hunter / Change Point Detection.
henrik
On Mon, Mar 31, 2025 at 1:35 AM Alexander Sorokoumov <
aleksandr.sorokoumov@gmail.com> wrote:
> Hey folks,
>
> I think we are very close to cutting the first Apache release. Yet, there
> are many small steps to do. Personally, I have been procrastinating on them
> as I don't exactly know what to do.
>
> To get over this "fear of the unknown", I have made a painfully detailed
> TODO list that should get us to the first release. The purpose of this
> thread is to a) agree that the steps in this list will indeed get us to
> correctly publishing the first Apache release and b) clarify the unknowns -
> mostly interactions with Apache infrastructure.
>
> I do believe that once we agree on the outstanding steps, we'll be able to
> get it over with within a week or so.
>
> Please find the list below. My unknowns are marked with **Q** and ????. I
> am looking forward to reading your feedback!
>
> TODO towards the first Apache release.
>
> 1. Agree on the release version (0.6.0-incubating? I am using that as a
> placeholder in other steps).
> 2. Update release name in pyproject.toml.
> 3. Update project description and authors in pyproject.toml.
> 4. Verify supported Python versions. Run tests and examples with Python
> 3.8+. Add a paragraph to README claiming that versions where tests passed
> are supported.
> 5. Create source distribution via `poetry build`.
> 6. Sign the artifact `gpg --armor --output dist/<artifact>.asc --detach-sig
> dist/<artifact>`.
> 7. Verify the checksum `sha512sum dist/<artifact> >
> dist/<artifact>.sha512`.
> 8. Test release candidate locally with `pip install`.
> 9. Upload project KEYS file. **Q:** How do we do that?
> 9. Upload Artifacts to Apache Dev Repo. **Q:** How do we do that?
> 10. Call for PMC Vote. Send an email to the this mailing list with the
> subject "VOTE: Release Apache Otava 0.6.0-incubating" with the link to the
> release candidate:
> ```
> The Apache Otava project is pleased to announce that the
> release candidate for version 0.6.0-incubating is ready.
>
> The release candidate artifacts are available at:
> ????
>
> SHA512: <checksum>
> KEYS:https://downloads.apache.org/incubator/otava/KEYS
>
> Please vote on releasing this candidate by replying with:
> [ ] +1 Release this package
> [ ] 0 No opinion
> [ ] -1 Do not release (please provide reason)
>
> This vote will be open for at least 72 hours.
> ```
> 11. Wait for the vote to pass, fix issues if any.
> 12. Call for IPMC Vote. Send an email to general@incubator.apache.org with
> the subject "[VOTE] [RESULT] Release Apache Otava 0.6.0-incubating". The
> content should contain links to the vote result and the artifacts.
> 13. Wait for the vote to pass, fix issues if any.
> 14. Move the RC to the release directory. **Q:** How do we do that?
> 15. Publish Github release/tag.
> 16. Upload the release to PyPI. **Q:** How do we do that?
> 17. Announce the release on the mailing list by sending an email with the
> subject "[ANNOUNCE] Apache Otava 0.6.0-incubating released".
> 18. Make social media noise.
> 19. Bump version in pyproject.toml for the next release.
>
>
> Best,
> Alex
>
Re: Path towards the first Apache release
Posted by Alexander Sorokoumov <al...@gmail.com>.
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 <
aleksandr.sorokoumov@gmail.com> 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 <
> aleksandr.sorokoumov@gmail.com> 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 <jo...@joedrumgoole.com>
>> 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, <he...@nyrkio.com> 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 <
>>> > aleksandr.sorokoumov@gmail.com> 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 <jo...@nyrkio.com> 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 <
>>> > > > aleksandr.sorokoumov@gmail.com> 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 <
>>> > > > > aleksandr.sorokoumov@gmail.com> 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 <
>>> > > > > whatwouldaustindo@gmail.com>
>>> > > > > > 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 <
>>> > > > > >> aleksandr.sorokoumov@gmail.com> 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 <
>>> mck@apache.org
>>> > >
>>> > > > > 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 private@libcloud.apache.org
>>> 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 <
>>> > > > > >> > > aleksandr.sorokoumov@gmail.com> 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 <
>>> > henrik@nyrkio.com
>>> > > >
>>> > > > > >> 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 <
>>> > > henrik@nyrkio.com
>>> > > > >
>>> > > > > >> > wrote:
>>> > > > > >> > > > >
>>> > > > > >> > > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov
>>> <
>>> > > > > >> > > > > > aleksandr.sorokoumov@gmail.com> 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
>>> > henrik@nyrkio.com LinkedIn:
>>> > www.linkedin.com/in/heingo
>>> > +358 40 569 7354 Twitter:
>>> > twitter.com/h_ingo
>>> >
>>>
>>
Re: Path towards the first Apache release
Posted by Alexander Sorokoumov <al...@gmail.com>.
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 <
aleksandr.sorokoumov@gmail.com> 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 <jo...@joedrumgoole.com> 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, <he...@nyrkio.com> 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 <
>> > aleksandr.sorokoumov@gmail.com> 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 <jo...@nyrkio.com> 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 <
>> > > > aleksandr.sorokoumov@gmail.com> 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 <
>> > > > > aleksandr.sorokoumov@gmail.com> 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 <
>> > > > > whatwouldaustindo@gmail.com>
>> > > > > > 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 <
>> > > > > >> aleksandr.sorokoumov@gmail.com> 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 <
>> mck@apache.org
>> > >
>> > > > > 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 private@libcloud.apache.org
>> 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 <
>> > > > > >> > > aleksandr.sorokoumov@gmail.com> 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 <
>> > henrik@nyrkio.com
>> > > >
>> > > > > >> 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 <
>> > > henrik@nyrkio.com
>> > > > >
>> > > > > >> > wrote:
>> > > > > >> > > > >
>> > > > > >> > > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
>> > > > > >> > > > > > aleksandr.sorokoumov@gmail.com> 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
>> > henrik@nyrkio.com LinkedIn:
>> > www.linkedin.com/in/heingo
>> > +358 40 569 7354 Twitter:
>> > twitter.com/h_ingo
>> >
>>
>
Re: Path towards the first Apache release
Posted by Alexander Sorokoumov <al...@gmail.com>.
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 <jo...@joedrumgoole.com> 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, <he...@nyrkio.com> 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 <
> > aleksandr.sorokoumov@gmail.com> 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 <jo...@nyrkio.com> 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 <
> > > > aleksandr.sorokoumov@gmail.com> 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 <
> > > > > aleksandr.sorokoumov@gmail.com> 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 <
> > > > > whatwouldaustindo@gmail.com>
> > > > > > 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 <
> > > > > >> aleksandr.sorokoumov@gmail.com> 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 <
> mck@apache.org
> > >
> > > > > 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 private@libcloud.apache.org
> 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 <
> > > > > >> > > aleksandr.sorokoumov@gmail.com> 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 <
> > henrik@nyrkio.com
> > > >
> > > > > >> 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 <
> > > henrik@nyrkio.com
> > > > >
> > > > > >> > wrote:
> > > > > >> > > > >
> > > > > >> > > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> > > > > >> > > > > > aleksandr.sorokoumov@gmail.com> 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
> > henrik@nyrkio.com LinkedIn:
> > www.linkedin.com/in/heingo
> > +358 40 569 7354 Twitter:
> > twitter.com/h_ingo
> >
>
Re: Path towards the first Apache release
Posted by Joe Drumgoole <jo...@joedrumgoole.com>.
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, <he...@nyrkio.com> 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 <
> aleksandr.sorokoumov@gmail.com> 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 <jo...@nyrkio.com> 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 <
> > > aleksandr.sorokoumov@gmail.com> 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 <
> > > > aleksandr.sorokoumov@gmail.com> 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 <
> > > > whatwouldaustindo@gmail.com>
> > > > > 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 <
> > > > >> aleksandr.sorokoumov@gmail.com> 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 <mck@apache.org
> >
> > > > 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 private@libcloud.apache.org 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 <
> > > > >> > > aleksandr.sorokoumov@gmail.com> 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 <
> henrik@nyrkio.com
> > >
> > > > >> 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 <
> > henrik@nyrkio.com
> > > >
> > > > >> > wrote:
> > > > >> > > > >
> > > > >> > > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> > > > >> > > > > > aleksandr.sorokoumov@gmail.com> 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
> henrik@nyrkio.com LinkedIn:
> www.linkedin.com/in/heingo
> +358 40 569 7354 Twitter:
> twitter.com/h_ingo
>
Re: Path towards the first Apache release
Posted by Henrik Ingo <he...@nyrkio.com>.
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 <
aleksandr.sorokoumov@gmail.com> 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 <jo...@nyrkio.com> 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 <
> > aleksandr.sorokoumov@gmail.com> 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 <
> > > aleksandr.sorokoumov@gmail.com> 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 <
> > > whatwouldaustindo@gmail.com>
> > > > 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 <
> > > >> aleksandr.sorokoumov@gmail.com> 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 <mc...@apache.org>
> > > 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 private@libcloud.apache.org 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 <
> > > >> > > aleksandr.sorokoumov@gmail.com> 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 <henrik@nyrkio.com
> >
> > > >> 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 <
> henrik@nyrkio.com
> > >
> > > >> > wrote:
> > > >> > > > >
> > > >> > > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> > > >> > > > > > aleksandr.sorokoumov@gmail.com> 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
henrik@nyrkio.com LinkedIn:
www.linkedin.com/in/heingo
+358 40 569 7354 Twitter: twitter.com/h_ingo
Re: Path towards the first Apache release
Posted by Alexander Sorokoumov <al...@gmail.com>.
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 <jo...@nyrkio.com> 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 <
> aleksandr.sorokoumov@gmail.com> 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 <
> > aleksandr.sorokoumov@gmail.com> 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 <
> > whatwouldaustindo@gmail.com>
> > > 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 <
> > >> aleksandr.sorokoumov@gmail.com> 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 <mc...@apache.org>
> > 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 private@libcloud.apache.org 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 <
> > >> > > aleksandr.sorokoumov@gmail.com> 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 <he...@nyrkio.com>
> > >> 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 <henrik@nyrkio.com
> >
> > >> > wrote:
> > >> > > > >
> > >> > > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> > >> > > > > > aleksandr.sorokoumov@gmail.com> 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
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> >
>
Re: Path towards the first Apache release
Posted by Joe Drumgoole <jo...@nyrkio.com>.
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 <
aleksandr.sorokoumov@gmail.com> 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 <
> aleksandr.sorokoumov@gmail.com> 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 <
> whatwouldaustindo@gmail.com>
> > 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 <
> >> aleksandr.sorokoumov@gmail.com> 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 <mc...@apache.org>
> 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 private@libcloud.apache.org 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 <
> >> > > aleksandr.sorokoumov@gmail.com> 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 <he...@nyrkio.com>
> >> 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 <he...@nyrkio.com>
> >> > wrote:
> >> > > > >
> >> > > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> >> > > > > > aleksandr.sorokoumov@gmail.com> 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
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: Path towards the first Apache release
Posted by Alexander Sorokoumov <al...@gmail.com>.
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 <
aleksandr.sorokoumov@gmail.com> 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 <wh...@gmail.com>
> 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 <
>> aleksandr.sorokoumov@gmail.com> 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 <mc...@apache.org> 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 private@libcloud.apache.org 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 <
>> > > aleksandr.sorokoumov@gmail.com> 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 <he...@nyrkio.com>
>> 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 <he...@nyrkio.com>
>> > wrote:
>> > > > >
>> > > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
>> > > > > > aleksandr.sorokoumov@gmail.com> 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
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: Path towards the first Apache release
Posted by Alexander Sorokoumov <al...@gmail.com>.
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 <wh...@gmail.com>
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 <
> aleksandr.sorokoumov@gmail.com> 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 <mc...@apache.org> 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 private@libcloud.apache.org 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 <
> > > aleksandr.sorokoumov@gmail.com> 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 <he...@nyrkio.com>
> 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 <he...@nyrkio.com>
> > wrote:
> > > > >
> > > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> > > > > > aleksandr.sorokoumov@gmail.com> 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
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Path towards the first Apache release
Posted by Austin Bennett <wh...@gmail.com>.
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 <
aleksandr.sorokoumov@gmail.com> 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 <mc...@apache.org> 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 private@libcloud.apache.org 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 <
> > aleksandr.sorokoumov@gmail.com> 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 <he...@nyrkio.com> 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 <he...@nyrkio.com>
> wrote:
> > > >
> > > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> > > > > aleksandr.sorokoumov@gmail.com> 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
> > > > >
> > > >
> > >
> >
>
Re: Path towards the first Apache release
Posted by Alexander Sorokoumov <al...@gmail.com>.
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 <mc...@apache.org> 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 private@libcloud.apache.org 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 <
> aleksandr.sorokoumov@gmail.com> 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 <he...@nyrkio.com> 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 <he...@nyrkio.com> wrote:
> > >
> > > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> > > > aleksandr.sorokoumov@gmail.com> 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
> > > >
> > >
> >
>
Re: Path towards the first Apache release
Posted by Mick Semb Wever <mc...@apache.org>.
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 private@libcloud.apache.org 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 <
aleksandr.sorokoumov@gmail.com> 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 <he...@nyrkio.com> 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 <he...@nyrkio.com> wrote:
> >
> > > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> > > aleksandr.sorokoumov@gmail.com> 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
> > >
> >
>
Re: Path towards the first Apache release
Posted by Alexander Sorokoumov <al...@gmail.com>.
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 <he...@nyrkio.com> 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 <he...@nyrkio.com> wrote:
>
> > On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> > aleksandr.sorokoumov@gmail.com> 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
> >
>
Re: Path towards the first Apache release
Posted by Henrik Ingo <he...@nyrkio.com>.
I compiled all of these into https://github.com/apache/otava/issues/51
On Wed, Apr 9, 2025 at 8:55 AM Henrik Ingo <he...@nyrkio.com> wrote:
> On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
> aleksandr.sorokoumov@gmail.com> 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
>
Re: Path towards the first Apache release
Posted by Henrik Ingo <he...@nyrkio.com>.
On Wed, Apr 9, 2025 at 7:28 AM Alexander Sorokoumov <
aleksandr.sorokoumov@gmail.com> 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
Re: Path towards the first Apache release
Posted by Alexander Sorokoumov <al...@gmail.com>.
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?
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).
Best,
Alex
On Wed, Apr 2, 2025 at 4:18 PM Austin Bennett <au...@apache.org> wrote:
> Glad this is coming together! Eager for otava versions to get sorted so
> can adopt.
>
> On Wed, Apr 2, 2025, 3:48 PM Henrik Ingo <he...@nyrkio.com> wrote:
>
> > Thanks Alex!
> >
> > I was operating under the assumption that everyone else here knows the
> > Apache process better than me, so I was hoping someone to start exactly
> > this email!
> >
> > I have two additions:
> >
> > - I suggest we do a zoom or teams release party? In fact, we could
> > literally do the svn commands together on such a call? I would invite
> > people who contributed over the years, all the way back to William Brown,
> > who wrote the first version of the algorithm during his last week as a
> > Summer intern at MongoDB. (And we never heard from him since but I
> recently
> > tracked him down on Linkedin.)
> >
> > - I have written a paper on the evolution of performance improvements in
> > Otava from the beginning. I want to publish this partly as a homage to
> > everyone who improved it over the years. Spoiler:Original implementation
> > was literally what the e-divisive paper describes: O(n^3) and the next
> week
> > William himself improved to O(n^2). Last year I achieved constant time
> > (when adding a single point). In raw numbers the performance improvement
> is
> > about 300 thousand times faster :-) (Depends on amount of data and also
> > number of change points found.) Main performance improvements came from
> 4
> > different developers over 8 years.
> >
> > - I might and probably should accompany the above with a more casual blog
> > post telling the history of Otava from MongoDB to Datastax to ASF. (And
> > other notable users too, of course.)
> >
> > - I will be presenting at
> >
> >
> https://icpe2025.spec.org/tracks-and-submissions/research-presentation-track/
> > on May 7-9. ICPE is the conference where both MongoDB and Datastax
> > primarily published papers on Otava / Hunter / Change Point Detection.
> >
> >
> > henrik
> >
> > On Mon, Mar 31, 2025 at 1:35 AM Alexander Sorokoumov <
> > aleksandr.sorokoumov@gmail.com> wrote:
> >
> > > Hey folks,
> > >
> > > I think we are very close to cutting the first Apache release. Yet,
> there
> > > are many small steps to do. Personally, I have been procrastinating on
> > them
> > > as I don't exactly know what to do.
> > >
> > > To get over this "fear of the unknown", I have made a painfully
> detailed
> > > TODO list that should get us to the first release. The purpose of this
> > > thread is to a) agree that the steps in this list will indeed get us to
> > > correctly publishing the first Apache release and b) clarify the
> > unknowns -
> > > mostly interactions with Apache infrastructure.
> > >
> > > I do believe that once we agree on the outstanding steps, we'll be able
> > to
> > > get it over with within a week or so.
> > >
> > > Please find the list below. My unknowns are marked with **Q** and
> ????. I
> > > am looking forward to reading your feedback!
> > >
> > > TODO towards the first Apache release.
> > >
> > > 1. Agree on the release version (0.6.0-incubating? I am using that as a
> > > placeholder in other steps).
> > > 2. Update release name in pyproject.toml.
> > > 3. Update project description and authors in pyproject.toml.
> > > 4. Verify supported Python versions. Run tests and examples with Python
> > > 3.8+. Add a paragraph to README claiming that versions where tests
> passed
> > > are supported.
> > > 5. Create source distribution via `poetry build`.
> > > 6. Sign the artifact `gpg --armor --output dist/<artifact>.asc
> > --detach-sig
> > > dist/<artifact>`.
> > > 7. Verify the checksum `sha512sum dist/<artifact> >
> > > dist/<artifact>.sha512`.
> > > 8. Test release candidate locally with `pip install`.
> > > 9. Upload project KEYS file. **Q:** How do we do that?
> > > 9. Upload Artifacts to Apache Dev Repo. **Q:** How do we do that?
> > > 10. Call for PMC Vote. Send an email to the this mailing list with the
> > > subject "VOTE: Release Apache Otava 0.6.0-incubating" with the link to
> > the
> > > release candidate:
> > > ```
> > > The Apache Otava project is pleased to announce that the
> > > release candidate for version 0.6.0-incubating is ready.
> > >
> > > The release candidate artifacts are available at:
> > > ????
> > >
> > > SHA512: <checksum>
> > > KEYS:https://downloads.apache.org/incubator/otava/KEYS
> > >
> > > Please vote on releasing this candidate by replying with:
> > > [ ] +1 Release this package
> > > [ ] 0 No opinion
> > > [ ] -1 Do not release (please provide reason)
> > >
> > > This vote will be open for at least 72 hours.
> > > ```
> > > 11. Wait for the vote to pass, fix issues if any.
> > > 12. Call for IPMC Vote. Send an email to general@incubator.apache.org
> > with
> > > the subject "[VOTE] [RESULT] Release Apache Otava 0.6.0-incubating".
> The
> > > content should contain links to the vote result and the artifacts.
> > > 13. Wait for the vote to pass, fix issues if any.
> > > 14. Move the RC to the release directory. **Q:** How do we do that?
> > > 15. Publish Github release/tag.
> > > 16. Upload the release to PyPI. **Q:** How do we do that?
> > > 17. Announce the release on the mailing list by sending an email with
> the
> > > subject "[ANNOUNCE] Apache Otava 0.6.0-incubating released".
> > > 18. Make social media noise.
> > > 19. Bump version in pyproject.toml for the next release.
> > >
> > >
> > > Best,
> > > Alex
> > >
> >
>
Re: Path towards the first Apache release
Posted by Austin Bennett <au...@apache.org>.
Glad this is coming together! Eager for otava versions to get sorted so
can adopt.
On Wed, Apr 2, 2025, 3:48 PM Henrik Ingo <he...@nyrkio.com> wrote:
> Thanks Alex!
>
> I was operating under the assumption that everyone else here knows the
> Apache process better than me, so I was hoping someone to start exactly
> this email!
>
> I have two additions:
>
> - I suggest we do a zoom or teams release party? In fact, we could
> literally do the svn commands together on such a call? I would invite
> people who contributed over the years, all the way back to William Brown,
> who wrote the first version of the algorithm during his last week as a
> Summer intern at MongoDB. (And we never heard from him since but I recently
> tracked him down on Linkedin.)
>
> - I have written a paper on the evolution of performance improvements in
> Otava from the beginning. I want to publish this partly as a homage to
> everyone who improved it over the years. Spoiler:Original implementation
> was literally what the e-divisive paper describes: O(n^3) and the next week
> William himself improved to O(n^2). Last year I achieved constant time
> (when adding a single point). In raw numbers the performance improvement is
> about 300 thousand times faster :-) (Depends on amount of data and also
> number of change points found.) Main performance improvements came from 4
> different developers over 8 years.
>
> - I might and probably should accompany the above with a more casual blog
> post telling the history of Otava from MongoDB to Datastax to ASF. (And
> other notable users too, of course.)
>
> - I will be presenting at
>
> https://icpe2025.spec.org/tracks-and-submissions/research-presentation-track/
> on May 7-9. ICPE is the conference where both MongoDB and Datastax
> primarily published papers on Otava / Hunter / Change Point Detection.
>
>
> henrik
>
> On Mon, Mar 31, 2025 at 1:35 AM Alexander Sorokoumov <
> aleksandr.sorokoumov@gmail.com> wrote:
>
> > Hey folks,
> >
> > I think we are very close to cutting the first Apache release. Yet, there
> > are many small steps to do. Personally, I have been procrastinating on
> them
> > as I don't exactly know what to do.
> >
> > To get over this "fear of the unknown", I have made a painfully detailed
> > TODO list that should get us to the first release. The purpose of this
> > thread is to a) agree that the steps in this list will indeed get us to
> > correctly publishing the first Apache release and b) clarify the
> unknowns -
> > mostly interactions with Apache infrastructure.
> >
> > I do believe that once we agree on the outstanding steps, we'll be able
> to
> > get it over with within a week or so.
> >
> > Please find the list below. My unknowns are marked with **Q** and ????. I
> > am looking forward to reading your feedback!
> >
> > TODO towards the first Apache release.
> >
> > 1. Agree on the release version (0.6.0-incubating? I am using that as a
> > placeholder in other steps).
> > 2. Update release name in pyproject.toml.
> > 3. Update project description and authors in pyproject.toml.
> > 4. Verify supported Python versions. Run tests and examples with Python
> > 3.8+. Add a paragraph to README claiming that versions where tests passed
> > are supported.
> > 5. Create source distribution via `poetry build`.
> > 6. Sign the artifact `gpg --armor --output dist/<artifact>.asc
> --detach-sig
> > dist/<artifact>`.
> > 7. Verify the checksum `sha512sum dist/<artifact> >
> > dist/<artifact>.sha512`.
> > 8. Test release candidate locally with `pip install`.
> > 9. Upload project KEYS file. **Q:** How do we do that?
> > 9. Upload Artifacts to Apache Dev Repo. **Q:** How do we do that?
> > 10. Call for PMC Vote. Send an email to the this mailing list with the
> > subject "VOTE: Release Apache Otava 0.6.0-incubating" with the link to
> the
> > release candidate:
> > ```
> > The Apache Otava project is pleased to announce that the
> > release candidate for version 0.6.0-incubating is ready.
> >
> > The release candidate artifacts are available at:
> > ????
> >
> > SHA512: <checksum>
> > KEYS:https://downloads.apache.org/incubator/otava/KEYS
> >
> > Please vote on releasing this candidate by replying with:
> > [ ] +1 Release this package
> > [ ] 0 No opinion
> > [ ] -1 Do not release (please provide reason)
> >
> > This vote will be open for at least 72 hours.
> > ```
> > 11. Wait for the vote to pass, fix issues if any.
> > 12. Call for IPMC Vote. Send an email to general@incubator.apache.org
> with
> > the subject "[VOTE] [RESULT] Release Apache Otava 0.6.0-incubating". The
> > content should contain links to the vote result and the artifacts.
> > 13. Wait for the vote to pass, fix issues if any.
> > 14. Move the RC to the release directory. **Q:** How do we do that?
> > 15. Publish Github release/tag.
> > 16. Upload the release to PyPI. **Q:** How do we do that?
> > 17. Announce the release on the mailing list by sending an email with the
> > subject "[ANNOUNCE] Apache Otava 0.6.0-incubating released".
> > 18. Make social media noise.
> > 19. Bump version in pyproject.toml for the next release.
> >
> >
> > Best,
> > Alex
> >
>