public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Arvydas Silanskas <nma.arvydas.silanskas@gmail.com>
To: Shawn Wagner <shawnw.mobile@gmail.com>
Cc: Per Bothner <per@bothner.com>, kawa mailing list <kawa@sourceware.org>
Subject: Re: Time for a new release? 3.1.2?
Date: Tue, 6 Dec 2022 11:07:03 +0200	[thread overview]
Message-ID: <CAPh7weCYBBZhC4nX+vbNJJrQrA4DbBo8LRvHHOVupyxWDxENNA@mail.gmail.com> (raw)
In-Reply-To: <CAMHuZZ1V=irui7k8BGgX2s+wULtKAMX1dKpQuwiA+TtennSeYw@mail.gmail.com>

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

I'd like to bump a question, would we want to add (for the time being
considering only red and tangerine) R7RS-large support? I'm fine with doing
necessary work as far as human resources go, but I want to know that this
is a direction that people agree with.

Shawn, thank you for sharing. Even if it doesn't make it to kawa core,
these libraries will be useful to have in personal projects.

2022-10-27, kt, 07:51 Shawn Wagner <shawnw.mobile@gmail.com> rašė:

> I've ported a lot of SRFIs to Kawa at
> https://gitlab.com/shawn_w/kawalib/-/tree/master though I'm not sure if
> any of them are included in Red or Tangerine.
>
> On Fri, Oct 21, 2022 at 2:02 AM Arvydas Silanskas via Kawa <
> kawa@sourceware.org> wrote:
>
>> The test suite had been fixed. But then one other thing popped into my
>> mind
>> -- how about the R7RS large red and tangerine support? The SRFIs required
>> seem to be very straightforward, not requiring any pervasive compiler
>> hacking but simply defining some simple libraries. I know R7RS large
>> colors
>> down the road will start including various non-portable / more invasive
>> requirements, but we can decide if we want to support those when we get
>> there.
>>
>> 2022-10-03, pr, 14:36 Arvydas Silanskas <nma.arvydas.silanskas@gmail.com>
>> rašė:
>>
>> > I propose to pause a bit; I remembered one thing that irked me quite a
>> > bit, and that is the failing test suite. I think it would be prudent to
>> fix
>> > it first before the release. As part of the hacktober festive theme,
>> I'll
>> > try to sit down and find time to make a pull request on the matter soon.
>> >
>> > Arvydas
>> >
>> > 2022-09-29, kt, 18:18 Arvydas Silanskas <
>> nma.arvydas.silanskas@gmail.com>
>> > rašė:
>> >
>> >> I can go over it on Sunday, if no one else does it by then.
>> >>
>> >> Arvydas
>> >>
>> >> 2022-09-29, kt, 07:38 Per Bothner <per@bothner.com> rašė:
>> >>
>> >>>
>> >>>
>> >>> On 9/28/22 10:53, Duncan Mak via Kawa wrote:
>> >>> > Hello Per,
>> >>> >
>> >>> > It's been over two years since the last release (3.1.1,
>> 2020-01-16), I
>> >>> > count 72 commits made to the master branch since then.
>> >>> >
>> >>> > Would it be a good time to make a 3.1.2 release soon?
>> >>>
>> >>> Might as well call it 3.2.
>> >>>
>> >>> It would be helpful if someone went through the changes
>> >>> (using 'git log' and **/ChangeLog) to summarize what has
>> >>> change in a format suitable for doc/news.texi.
>> >>>
>> >>> Also make a note of where the manual needs to be updated.
>> >>>
>> >>> Minor tweaks and bug fixes don't need to be mentioned.
>> >>>
>> >>> --
>> >>>         --Per Bothner
>> >>> per@bothner.com   http://per.bothner.com/
>> >>>
>> >>
>>
>

  reply	other threads:[~2022-12-06  9:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 17:53 Duncan Mak
2022-09-29  4:38 ` Per Bothner
2022-09-29 15:18   ` Arvydas Silanskas
2022-10-03 11:36     ` Arvydas Silanskas
2022-10-21  9:01       ` Arvydas Silanskas
2022-10-27  4:50         ` Shawn Wagner
2022-12-06  9:07           ` Arvydas Silanskas [this message]
2023-01-05 21:34             ` Per Bothner
2023-01-05 22:02               ` Damien Mattei
2023-01-06 12:16               ` Lassi Kortela
2023-01-08 18:11               ` Sascha Ziemann
2023-01-09  9:03                 ` Lassi Kortela
2023-01-09  9:42                   ` Arvydas Silanskas
2023-01-09 10:51                     ` Lassi Kortela

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

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

  git send-email \
    --in-reply-to=CAPh7weCYBBZhC4nX+vbNJJrQrA4DbBo8LRvHHOVupyxWDxENNA@mail.gmail.com \
    --to=nma.arvydas.silanskas@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.com \
    --cc=shawnw.mobile@gmail.com \
    /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).