[GitHub] [buildstream-plugins] gtristan commented on issue #32: https://apache.github.io/buildstream-plugins/ is pointing to old tag (1.91) instead current 1.95.1

[GitBox <gi...@apache.org>]

gtristan commented on issue #32:
URL: https://github.com/apache/buildstream-plugins/issues/32#issuecomment-1224083536

   Renaming issue which was previously:
   
   > https://apache.github.io/buildstream-plugins/ is pointing to old tag (1.91) instead current 1.95.1
   
   Some context:
   * The https://apache.github.io/buildstream-plugins/ is displaying the correct documentation, which is generated from the latest push to `master`
   * The documentation unfortunately advertises a version, this version is set at: https://github.com/apache/buildstream-plugins/blob/master/doc/source/conf.py#L65
   * Since we only publish one version of the stable plugins, and will anyway need to add `Since x.y` annotations for newly added features in this repository, it seems unnecessary to advertise the version, it is always *"the latest"*
   * It is also unlikely people will remember to update that version in the docs perfectly consistently, so it will be constantly at risk of being an incorrect version
   
   Note that the version which is hardcoded in setup.py: https://github.com/apache/buildstream-plugins/blob/master/setup.py#L43 is also obnoxious to update with every tag and sometimes requires a re-tag at release time, at least in this case we end up remembering to update that hard coded version because we otherwise get an error uploading to `PyPI`.
   
   An alternative would be to use `versioneer`, like BuildStream itself does.
   


-- 
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: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org