From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: 2.02 Release roadmap
Date: Mon, 25 Nov 2013 19:23:06 +0100 [thread overview]
Message-ID: <5293958A.3090703@gmail.com> (raw)
In-Reply-To: <CAKCeAn--L46t=OSFx3KrOmuckGHrfYHXCHcDr6S+yXfKAX4ENw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
On 25.11.2013 19:14, SevenBits wrote:
> It is too late, then, to submit a patch adding a new command to GRUB?
> I've been meaning to submit it but have been busy... it's already done
> and everything, just want to see if I can get upstream. :)
>
It's not frozen yet (see the date). Then, of course, it depends on how
big and intrusive the code is.
>
> On Mon, Nov 25, 2013 at 12:58 PM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder@gmail.com <mailto:phcoder@gmail.com>> wrote:
>
> Hello, all. It's time to start gearing towards 2.02 release
> - 2.01 number will be skipped in order to follow odd/even convention for
> release/git.
> On 17th December will be the feature freeze, after it only bugfixes and
> documentation will be committed.
> Release will be when we're confifent enough in absence of major bugs.
> Features I expect to go in before freeze:
> - Leif Lindholm's arm64 port: it's pretty complete from what I saw.
> - multiboot2 extension to skip teminating boot services
> - mac HFS+ install
> - yeeloong 3A support (almost done)
> - grub-file
> - truecrypt
> - Andrey's inline inode patch
>
> In case anyone has unreviewed patches please inform me as soon as
> possible (mail could have been lost or I might have forgotten some
> of them)
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org <mailto:Grub-devel@gnu.org>
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2013-11-25 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 17:58 2.02 Release roadmap Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-25 18:14 ` SevenBits
2013-11-25 18:23 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-11-26 18:49 ` Andrey Borzenkov
2013-11-26 19:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-27 11:05 ` Colin Watson
2013-11-29 17:55 ` Andrey Borzenkov
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=5293958A.3090703@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@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 NNTP newsgroup(s).