grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: 2.02 Release roadmap
Date: Tue, 26 Nov 2013 22:49:57 +0400	[thread overview]
Message-ID: <20131126224957.14063c3d@opensuse.site> (raw)
In-Reply-To: <52938FB1.3000108@gmail.com>

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

В Mon, 25 Nov 2013 18:58:09 +0100
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:

> 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)
> 

What is the state of new-autogen branch? That's something I'd
definitely welcome as autogen is not present in all distros which makes
maintaining patches that touch build system rather unpleasant.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-11-26 18:50 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
2013-11-26 18:49 ` Andrey Borzenkov [this message]
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=20131126224957.14063c3d@opensuse.site \
    --to=arvidjaar@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).