unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: GNU G-Golf 0.8.0-a.2 available for testing!
Date: Mon, 9 Jan 2023 23:26:13 -0300	[thread overview]
Message-ID: <20230109232613.64bfb493@aicha> (raw)

[-- Attachment #1: Type: text/plain, Size: 2531 bytes --]

Hello Guilers,

The second alpha release of the upcoming 0.8.0 release is now available
for testing:

	Tarball and a GPG detached signature [*]:

		http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-a.2.tar.gz
		http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-a.2.tar.gz.sig

	Dependencies and complete installation instructions are given
	in the distributed INSTALL file, or here:

		https://www.gnu.org/software/g-golf/install.html

	The list of noteworthy changes since version 0.8.0-a.1 are
	given in the distributed NEWS file, or here:

			https://www.gnu.org/software/g-golf/news.html

You can help by:

  1. Testing by installing from the tarball, or from the source if you
  prefer, on the distro of your choice.

  2. By running the distributed examples.

Ultimately, one of the best way to test, and participate, is to select
G-Golf to develop the next application of your dream! Here is an
overview of the GNOME platform libraries [1], accessible using G-Golf.
In particular, libadwaita [2] provides a number of widgets that change
their layout based on the available space. This can be used to make
applications adapt their UI between desktop and mobile devices.

Contact [3]

Before you email, or bug report, you could join us on irc, and ping
me there: be patient, I also need to eat, sleep, rest ... but I always
answer, and this my preferred way to quickly interact and fix potential
G-Golf problem(s).

On irc, we chat :), so please do not write code snipsets there unless 2
or 3 lines of code, nor error messages of course - for more then 2 or 3
lines of code, or error messages, always use a tor-friendly paste
service (avoid those that tracks us an require javascript, thanks!)

However, if you prefer:

	G-Golf uses Guile's mailing lists
	Report bugs to bug-g-golf@gnu.org

Thanks!
David

[*] Use a .sig file to verify that the corresponding file (without the
    .sig suffix) is intact.  First, be sure to download both the .sig
    file and the corresponding tarball.  Then, run a command like this:

	gpg --verify g-golf-0.8.0-a.1.tar.gz

    If that command fails because you don't have the required public
    key, then run this command to import it:

	gpg --keyserver keys.gnupg.net --recv-keys A3057AD7

    and rerun the 'gpg --verify' command


[1] https://developer.gnome.org/documentation/introduction/overview/libraries.html
[2] https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/
[3] https://www.gnu.org/software/g-golf/contact.html

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2023-01-10  2:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230109232613.64bfb493@aicha \
    --to=david@altosw.be \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).