henrikingo commented on issue #56:
URL: https://github.com/apache/otava/issues/56#issuecomment-2863926011

   Isn't this a chicken and egg problem? We would need to have a release first 
so that the documentation can point to it.
   
   At this point I would say it is ok for us to just produce a release and not 
announce it. We would like to create a release that is a snapshot of the code 
donated to ASF, with the only changes being the name change, license headers, 
supported python versions, dependencies, etc...  other ASF related changes. 
Until we do that, we have intentionally not been very eager to receive new 
contributors or non-trivial features.
   
   Also, it seems to me we need to produce the source release, so that we can 
upload a PyPI package, to which the documentation can then refer.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to