Skip to content

Commit

Permalink
Release v0.8.1
Browse files Browse the repository at this point in the history
  • Loading branch information
@rockdaboot
rockdaboot committed Aug 14, 2015
1 parent 7b72ac6 commit aa94d57
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 1 deletion.
4 changes: 4 additions & 0 deletions NEWS
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
Copyright (C) 2014 Tim Rühsen

14.08.2015 Release V0.8.1
* Fix documentation
* Add syntax checking of tests_psl.txt

06.08.2015 Release V0.8.0
* Add https://github.com/publicsuffix as git submodule
* Support Debian 'Reproducible Builds'
Expand Down
2 changes: 1 addition & 1 deletion configure.ac
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@

AC_INIT([libpsl], [0.8.0], [tim.ruehsen@gmx.de], [libpsl], [http://github.com/rockdaboot/libpsl])
AC_INIT([libpsl], [0.8.1], [tim.ruehsen@gmx.de], [libpsl], [http://github.com/rockdaboot/libpsl])
AC_PREREQ([2.59])
AM_INIT_AUTOMAKE([1.10 -Wall no-define foreign])

Expand Down

6 comments on commit aa94d57

@cicku
Copy link
Contributor

@cicku cicku commented on aa94d57 Aug 18, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any chance to tag each new release with number only? I see libpsl-0.8.1 instead of 0.8.1 in tags which causes trouble to our tracking system. I don't care if it's intended for Debian, but please change back to normal ways.

Thanks.

@rockdaboot
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I personally do not care much, the tag ( and format) is mainly for package maintainers.
AFAIR, someone asked me to change it from number only to libpsl- :-)
Couldn't find the request so far (it was either Daniel Kahn Gilmor (Debian) or Dagobert Michelsen (Solaris)). I didn't look at many other libraries... what is the common format ? I would like to go with that.

@cicku
Copy link
Contributor

@cicku cicku commented on aa94d57 Aug 19, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Common ways:

v0.8.1

Or

0.8.1

@rockdaboot
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cicku I am going to release 0.9.0. Having a look at curl, c-ares or gnutls (C libraries): they use the tagging convention 'name-x_y_z', e.g. cares-1_0_1. Your tracking should be able to handle that.
Also, one of the closed issues asked me to change from x.y.z to libpsl-x.y.z because x.y.z is bad for packagers :-) So I stay with that convention.

@cicku
Copy link
Contributor

@cicku cicku commented on aa94d57 Sep 16, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because x.y.z is bad for packagers :-) So I stay with that convention.

That's bullshit, no offense.

In the past Github treated these tags and pushed tarball name to libpsl-libpsl-0.9.0, kinda dumb name, now github realizes the issue, and starts promoting release functionality.

I don't have issues now, because releases page contains libpsl-$VER.(tar.gz|zip).

Sorry for the noise 😂

@rockdaboot
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:-) Thanks, I didn't know about this 'interesting' naming on github.

Please sign in to comment.