One more thing :)
Apache Beam appears to have an excellent release guide which includes
their process which involves PyPi --
https://beam.apache.org/contribute/release-guide/
Maybe we can copy them?
On 6/15/20 1:08 PM, Josh Elser wrote:
Did a little searching..
* Found a 2011 blog post from sqlalchemy which said (as a project) they
would not post devN releases to pypi
* There's a TestPyPi [1] instead which seems to be for staging work.
Could we play with staging there? And then push to pypi (real) after we
do a normal vote?
I think we can keep our python release super-low friction :)
[1] https://packaging.python.org/guides/using-testpypi/
On 6/15/20 1:02 PM, Josh Elser wrote:
Hey Istvan,
Great of you to drive this work!
I do have one concern about pushing the dev releases to PyPi (I'm
assuming that's what you mean). I understand that in the Python world
a "dev" release indicates that this isn't an "official" release [1].
At the ASF, you're correct that we, developers, are empowered to make
"builds" of our product(s) for the sake of our development. There is a
clear line when that "build" is published in a location to which a
user may find it and begin to use it. There has been at least one
example in recent memory of a project which made "developer only
releases" without proper voting, but published them in a
high-visibility location and (inadvertently or intentionally)
circumvented the ASF release requirements.
My biggest concern is: would a user who ran a `pip install phoenixdb`
after we make a devN release get the last-stable release (0.7) or the
new devN release? If they would get the dev release, does PyPi give us
any flexibility to prevent this from happening? I believe that we
should consider publishing to the "official" location should be
treated as a release if it means that a user could begin to use it
with "low friction".
- Josh
[1] https://www.python.org/dev/peps/pep-0440/#id24
On 6/12/20 7:11 AM, Istvan Toth wrote:
Hi!
Even though we have adopted the PhoenixDB driver in 2018, there
hasn't been
much activity on it, and the version available on PyPI is still the
old 0.7
release by Lukas.
Recently I have worked on it quite a bit, adding fixes and new features,
and adopting the partial SQLAlchemy driver from pyPhoenix, thus enabling
Hue support.
I plan to start releasing the driver publicly on PyPI. Lukas has kindly
shared control of the PyPI phoenixdb project with us, so we are good
to go.
The short-term plan is to release 1.0.0.dev0 and later 1.0.0.devN
releases
from the current HEAD of phoenix-queryserver. As these will be dev
releases, I am not planning to follow a formal release process for
these.
When and how to release 1.0.0 final, and the versioning
scheme/process to
use after that are still not finalized.
Please join the discussion here, or in
https://issues.apache.org/jira/browse/PHOENIX-5939 if you have any
questions or suggestions!
regards
Istvan
