search

sclorg / rpm-list-builder

RPM List Builder helps you to build a list of defined RPM packages including Software Collection from the recipe file
GNU General Public License v2.0
4 stars 8 forks source link

Bumping version 1.1.0 #89

Closed junaruga closed 7 years ago

junaruga commented 7 years ago

After fixing current 4 PRs #74, #80, #82, #88, and updating documents, I think it's time for us to release version 1.1.0.

What we do:

How do you think?

hroncok commented 7 years ago

Register it rather sooner than later, so nobody steals the name.

junaruga commented 7 years ago

@hroncok OK I will register it with package name rpmlb today.

junaruga commented 7 years ago

I tried to register to pypi. It looks previously the operation was register project and upload file. But now it has been changed. the operation to register a project has not been necessary any more. The necessary process is only uploading a dist file.

$ python3 setup.py register -r https://test.pypi.org/legacy/
...
Registering rpmlb to https://test.pypi.org/legacy/
Server response (410): Project pre-registration is no longer required or supported, so continue directly to uploading files.

Ref: https://pypi.org https://mail.python.org/pipermail/distutils-sig/2017-June/030766.html

I tried to upload current source. But uploading was failed because of invalid version number 1.0.1.dev81+gfa889ae.

$ python3 setup.py sdist upload
...
Submitting dist/rpmlb-1.0.1.dev81+gfa889ae.tar.gz to https://upload.pypi.org/legacy/
Upload failed (400): version: Cannot use PEP 440 local versions.
error: Upload failed (400): version: Cannot use PEP 440 local versions.

So, shall we release current source to get the project name rpmlb soon as v1.1.0?

Below are commands to run to upload source file. Do I have a permission to push a tag information to this repository?

$ git tag -a v1.1.0 -m "v1.1.0 release"
$ git push origin v1.1.0
$ python3 setup.py sdist upload
hroncok commented 7 years ago

Oh. Didn't know that. So what about doing a 1.1.0-dev1 as a test that everything works? Don't know if that works with setuptools_scm.

Do I have a permission to push a tag information to this repository?

I guess you do, only master branch is somehow protected (for everybody).

BTW also look at twine.

hroncok commented 7 years ago

In order to reserve the name, I've created v1.1.0-dev81 tag and uploaded sdist and wheel. let me know your PyPI username, so I can add you to the package.

hroncok commented 7 years ago

The tag is not pushed, because it breaks setuptools_scm with:

AssertionError: own dev numbers are unsupported
hroncok commented 7 years ago

Created a 1.1.0 milestone so we know when to release.

junaruga commented 7 years ago

This repository has not been active long time. After minimal PRs, shall we upload rpmlb v1.1.0 to pypi? Then I guess our project is gong to be done in the meantime.

junaruga commented 7 years ago

@hhorak or @khardix I guess that all the task for v1.1.0 is finished. Can you bump version and release rpmlb to PyPI?

junaruga commented 7 years ago

I did git tag by Jan's request.

On latest mater branch.

$ git tag -n
v1.0.0          v1.0.0 release

$ git tag -a 'v1.1.0' -m 'v1.1.0 release'

$ git tag -n
v1.0.0          v1.0.0 release
v1.1.0          v1.1.0 release

$ git push origin v1.1.0
khardix commented 7 years ago

And we are live: https://pypi.python.org/pypi/rpmlb Good work, @junaruga.

junaruga commented 7 years ago

@khardix thanks for the releasing! Congrats, everyone. We did it.