mailing list of musl libc
 help / color / mirror / code / Atom feed
From: ardi <ardillasdelmonte@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Timeline for 1.1.20?
Date: Tue, 17 Jul 2018 09:56:59 +0200	[thread overview]
Message-ID: <CA+fZqCXDFYNTcE7b9Ut47qxnn4g22oB9KBGUJ=xRaX3o0q4QGw@mail.gmail.com> (raw)
In-Reply-To: <20180716172023.GM1392@brightrain.aerifal.cx>

On Mon, Jul 16, 2018 at 7:20 PM, Rich Felker <dalias@libc.org> wrote:
> On Wed, Jul 11, 2018 at 09:17:01AM +0200, ardi wrote:
>> Hi!
>>
>> Is there a timeline for the 1.1.20 release? I'm starting a project,
>> and I'd find it very convenient to know if 1.1.20 will be released
>> this month, or if 1.1.19 is going to be kept as the current release
>> for some months to come.
>
> I don't have a date in mind, but letting it get drawn out for "some
> months" again is definitely not something I want to have happen.
> There's definitely enough time left in this month that a release
> before the end should be possible. Assistance with testing/checks for
> regressions would help a lot.

I'm not the best one for doing testing, as I don't have any previous
code based on musl, and moreover, my way of using it is going to be
non-obvious/marginal, as I'm working in being OS-independent, as I
wrote in the list months ago. There's a possibility that I end up
combining code from newlib and musl, but that's not certain at this
moment (the only certain thing for the moment is that musl has
everything I need, including a complete ELF dynamic linker/loader, and
that newlib follows the approach I want -syscall isolation- but it's
less complete and has no linker/loader). So, I need to dig deeply at
building both libraries, and finding my way during the process.

Said this, I'm starting my efforts through an Alpine Linux VM (for
obvious reasons, as musl is default there, and llvm is also there,
which is the compiler suite I use), so I'll be happy to test in that
VM any 1.1.20 release candidates you prepare, although I assume that
Alpine will be a platform for which you'll have testers already.

Thanks!

ardi


  reply	other threads:[~2018-07-17  7:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11  7:17 ardi
2018-07-16 17:20 ` Rich Felker
2018-07-17  7:56   ` ardi [this message]
2018-07-28 17:22   ` Rob Landley
2018-07-28 17:43     ` Christopher Friedt
2018-07-28 19:55       ` Rich Felker
2018-07-29 11:40         ` Christopher Friedt
2018-07-29 15:49           ` musl "Linux-dependencies" info [was Re: [musl] Timeline for 1.1.20?] Rich Felker
2018-07-29 16:03           ` Timeline for 1.1.20? Rich Felker
2018-07-29 12:50         ` [RFC/RFT] musl: 1.1.20 prelease testing Christian Lamparter

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='CA+fZqCXDFYNTcE7b9Ut47qxnn4g22oB9KBGUJ=xRaX3o0q4QGw@mail.gmail.com' \
    --to=ardillasdelmonte@gmail.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).