[
https://issues.apache.org/jira/browse/PHOENIX-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127932#comment-17127932
]
Istvan Toth commented on PHOENIX-5939:
--------------------------------------
*Admin/Owner stuff:*
I've skimmed the docs. There are two roles in PyPI, _maintainer_ and _owner_.
https://pypi.org/help/#collaborator-roles
It seems to me that both need to be actual persons, and not groups, but there
may be multiple _owners_ and _maintainers_.
Releasing packages requires only the lesser _maintainer_ role.
*Versioning:*
As [~elserj] pointed out, the phoenix client versioning could be in theory be
detached from the queryserver versioning.
Example: After queryserver 1.0.0 is released, someone steps up to actually
implement SQLAlchemy ORM, or finds a python security issue. Neither if these
warrant a new (Java) PQS release, but they do warrant a new PhoenixDB release.
Assume that we have already released *PhoenixDB 1.0.0*
We can release the new version as
A) *1.1.0dev0*
B) *1.0.0.1*
C) *1.1 or 1.0.1*
**A) is not optimal, since we'd ask users to switch from a stable version to a
dev version to get the features/fixes.
B) is an imperfect compromise, as it provides neither information about the
level of changes in a new release, nor does it keep the versions completely in
sync.
C) is optimal from a PhoenixDB end user POV, but since it shares a repo with
PQS, it causes confusion in source versioning. We could maybe tag python
releases with a separate python release git tag ?
**The cleanest solution would be splitting PhonenixDB into its own repo, but
it'd cause repo creep, would be quite a lot of work, and make testing somewhat
more complex.
Anyway, deciding on this can wait until after PQS 1.0.0 is released.
Phoenix/PyPI doesn't have the concept of -SNAPSHOT, the corresponding concept
seems to be *dev* releases. These can be distributed from PyPI, and they must
be numbered. So we could release _1.0.0dev0_, and if additional fixes show up
before 1.0.0, release _1.0.0dev1_ _dev2_, etc.
To support the Hue work, and other users (as well as get some experience with
the releasing process), I think that we should release some _dev_ versions
before the final 1.0.0
*Licensing*
**[~elserj] has already provided the necessary information for this, I just
couldn't find the time (or the will) do it yet.
*Next steps*
# We need to figure out who should be the PyPI project owner.
[[email protected]] as PMCC is an obvious choice, with maybe a backup person
for when he's not available.
# Once that's done, we should contact Lukas and ask him to transfer ownership
to the new owner, who can add the other owners and maintainers.
> Publish PhoenixDB to PyPI
> -------------------------
>
> Key: PHOENIX-5939
> URL: https://issues.apache.org/jira/browse/PHOENIX-5939
> Project: Phoenix
> Issue Type: Task
> Components: queryserver
> Affects Versions: queryserver-1.0.0
> Reporter: Istvan Toth
> Priority: Major
>
> The original PhoenixDB driver was published to PyPI.
> The improved version in phoenix-queryserver is only available from there.
> We should start publishing the driver again.
> Some questions to answer:
> * Can we take over the old PyPI project ?
> * Do we want to ?
> * What should be the project/artifact name (if not the old one)
> * Version numbering ?
> * Do we want to publish development versions ?
> * What is the process / who should do the publishing ?
> * Any blockers before we start publishing ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
