Re: Cutting a gnustep-gui release

[Ivan Vučica]

It's not totally clear to me how to make a good use of this.

Let's assume I have an existing .deb obtained via packages.debian.org (or an .so from that .deb), and I have a source tree checked out from GNUstep's Subversion. Let's assume I have no 'package tree' (i.e. one with debian/ directory) at a particular time.

What would you like me to do to prepare the source tree (do I need to obtain the debian/ directory, for example), and what would you like me to execute in order to validate that the ABI didn't break?

Thanks!

On Tue, Dec 20, 2016 at 5:44 PM, Eric Heintzmann <address@hidden> wrote:

Le 16/12/2016 à 17:16, Ivan Vučica a écrit :
>
> On Fri, Dec 16, 2016 at 3:54 PM, Eric Heintzmann
> <address@hidden <mailto:address@hiddenfr>> wrote:
>
>     Debian Stretch will be fully frozen on 2017-02-05.
>     A special release before this date, with all you want to see in
>     the next
>     debian stable distro, would be a good idea.
>
>     (The current status of Stretch is "transition freeze", it means
>     that all
>     ABI/API breakage will be refused by the official Debian  release team)
>
>
> Unless I missed something significant, the API/ABI should be backwards
> compatible. (I'd go through the list of changes before the release.)
>
> Any easy way to test whether Debian will consider API/ABI breakage has
> happened, which we could then add to the release docs?
>

https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-updates

https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi