2.02~beta3 release

2.02~beta3 release

[Vladimir 'φ-coder/phcoder' Serbinenko]

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

Hello, all. I've just released 2.02~beta3. The goal of this release is
to chase bugs so that we can move to 2.02 release. So from now on if you
think that your patch should be included in 2.02 rather than in 2.03,
please add [2.02] to the beginning of your email subject

The tarball is available at
http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
and signature at
http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig

Signed with following fingerprint:
 E53D 497F 3FA4 2AD8 C9B4  D1E8 35A9 3B74 E82E 4209

It's also available as a signed tag grub-2.02-beta3 in official git
repository.

If you don't have xz support alternatively you may consider files
http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
and signature at
http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig





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

Re: 2.02~beta3 release

[Andrei Borzenkov]

Отправлено с iPhone

> 28 февр. 2016 г., в 17:21, Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> написал(а):
> 
> Hello, all. I've just released 2.02~beta3. The goal of this release is
> to chase bugs so that we can move to 2.02 release. So from now on if you
> think that your patch should be included in 2.02 rather than in 2.03,
> please add [2.02] to the beginning of your email subject
> 
> The tarball is available at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> and signature at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> 
> Signed with following fingerprint:
> E53D 497F 3FA4 2AD8 C9B4  D1E8 35A9 3B74 E82E 4209
> 
> It's also available as a signed tag grub-2.02-beta3 in official git
> repository.
> 
> If you don't have xz support alternatively you may consider files
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> and signature at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> 
> 



You mean gz, right?
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel

Re: 2.02~beta3 release

[Vladimir 'phcoder' Serbinenko]

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

Le dim. 28 févr. 2016 15:32, Andrei Borzenkov <arvidjaar@gmail.com> a
écrit :

>
>
> Отправлено с iPhone
>
> > 28 февр. 2016 г., в 17:21, Vladimir 'φ-coder/phcoder' Serbinenko <
> phcoder@gmail.com> написал(а):
> >
> > Hello, all. I've just released 2.02~beta3. The goal of this release is
> > to chase bugs so that we can move to 2.02 release. So from now on if you
> > think that your patch should be included in 2.02 rather than in 2.03,
> > please add [2.02] to the beginning of your email subject
> >
> > The tarball is available at
> > http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> > and signature at
> > http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> >
> > Signed with following fingerprint:
> > E53D 497F 3FA4 2AD8 C9B4  D1E8 35A9 3B74 E82E 4209
> >
> > It's also available as a signed tag grub-2.02-beta3 in official git
> > repository.
> >
> > If you don't have xz support alternatively you may consider files
> > http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> > and signature at
> > http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> >
> >
>
>
>
> You mean gz, right?
>
Gz and Xz, not twice xz right.

> >
> >
> > _______________________________________________
> > Grub-devel mailing list
> > 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: Type: text/html, Size: 2893 bytes --]

Re: 2.02~beta3 release

[Andrei Borzenkov]

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

You forgot to tag GIT. I think we discussed that release tag should be
signed, not sure if this is achievable.

28.02.2016 17:21, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
> Hello, all. I've just released 2.02~beta3. The goal of this release is
> to chase bugs so that we can move to 2.02 release. So from now on if you
> think that your patch should be included in 2.02 rather than in 2.03,
> please add [2.02] to the beginning of your email subject
> 
> The tarball is available at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> and signature at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> 
> Signed with following fingerprint:
>  E53D 497F 3FA4 2AD8 C9B4  D1E8 35A9 3B74 E82E 4209
> 
> It's also available as a signed tag grub-2.02-beta3 in official git
> repository.
> 
> If you don't have xz support alternatively you may consider files
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> and signature at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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: 198 bytes --]

Re: 2.02~beta3 release

[Andrei Borzenkov]

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

28.02.2016 19:40, Andrei Borzenkov пишет:
> You forgot to tag GIT. I think we discussed that release tag should be
> signed, not sure if this is achievable.

Oh, sorry, was confused that tag name pattern is different from beta2.
We should pick one rule and stick to it (I do not really care which).

> 
> 28.02.2016 17:21, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
>> Hello, all. I've just released 2.02~beta3. The goal of this release is
>> to chase bugs so that we can move to 2.02 release. So from now on if you
>> think that your patch should be included in 2.02 rather than in 2.03,
>> please add [2.02] to the beginning of your email subject
>>
>> The tarball is available at
>> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
>> and signature at
>> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
>>
>> Signed with following fingerprint:
>>  E53D 497F 3FA4 2AD8 C9B4  D1E8 35A9 3B74 E82E 4209
>>
>> It's also available as a signed tag grub-2.02-beta3 in official git
>> repository.
>>
>> If you don't have xz support alternatively you may consider files
>> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
>> and signature at
>> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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: 198 bytes --]

Re: 2.02~beta3 release

[Vladimir 'phcoder' Serbinenko]

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

On Sunday, February 28, 2016, Andrei Borzenkov <arvidjaar@gmail.com> wrote:

> 28.02.2016 19:40, Andrei Borzenkov пишет:
> > You forgot to tag GIT. I think we discussed that release tag should be
> > signed, not sure if this is achievable.
>
> Oh, sorry, was confused that tag name pattern is different from beta2.
> We should pick one rule and stick to it (I do not really care which).
>
> I added signed tag in both formats now. Thank you for reminder.

> >
> > 28.02.2016 17:21, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
> >> Hello, all. I've just released 2.02~beta3. The goal of this release is
> >> to chase bugs so that we can move to 2.02 release. So from now on if you
> >> think that your patch should be included in 2.02 rather than in 2.03,
> >> please add [2.02] to the beginning of your email subject
> >>
> >> The tarball is available at
> >> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> >> and signature at
> >> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> >>
> >> Signed with following fingerprint:
> >>  E53D 497F 3FA4 2AD8 C9B4  D1E8 35A9 3B74 E82E 4209
> >>
> >> It's also available as a signed tag grub-2.02-beta3 in official git
> >> repository.
> >>
> >> If you don't have xz support alternatively you may consider files
> >> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> >> and signature at
> >> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> >>
> >>
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Grub-devel mailing list
> >> Grub-devel@gnu.org <javascript:;>
> >> https://lists.gnu.org/mailman/listinfo/grub-devel
> >>
> >
> >
>
>
>

-- 
Regards
Vladimir 'phcoder' Serbinenko

[-- Attachment #2: Type: text/html, Size: 2876 bytes --]

Re: 2.02~beta3 release

[Vladimir 'phcoder' Serbinenko]

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

On Sunday, February 28, 2016, Vladimir 'φ-coder/phcoder' Serbinenko <
phcoder@gmail.com> wrote:

> Hello, all. I've just released 2.02~beta3. The goal of this release is
> to chase bugs so that we can move to 2.02 release. So from now on if you
> think that your patch should be included in 2.02 rather than in 2.03,
> please add [2.02] to the beginning of your email subject
>
> Forgot to ask: also please ping any existing threads that in your opinion
need to be considered for 2.02 with a short message saying so. This will
make my life much easier. Thank you in advance.


-- 
Regards
Vladimir 'phcoder' Serbinenko

[-- Attachment #2: Type: text/html, Size: 852 bytes --]

Re: 2.02~beta3 release

[Peter Jones]

On Sun, Feb 28, 2016 at 03:21:44PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Hello, all. I've just released 2.02~beta3. The goal of this release is
> to chase bugs so that we can move to 2.02 release. So from now on if you
> think that your patch should be included in 2.02 rather than in 2.03,
> please add [2.02] to the beginning of your email subject
> 
> The tarball is available at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> and signature at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> 
> Signed with following fingerprint:
>  E53D 497F 3FA4 2AD8 C9B4  D1E8 35A9 3B74 E82E 4209
> 
> It's also available as a signed tag grub-2.02-beta3 in official git
> repository.
> 
> If you don't have xz support alternatively you may consider files
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> and signature at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig

Thanks, this is a great step.  What is the timeline we're planning to
follow?

-- 
        Peter

Re: 2.02~beta3 release

[Konrad Rzeszutek Wilk]

On Sun, Feb 28, 2016 at 03:21:44PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Hello, all. I've just released 2.02~beta3. The goal of this release is
> to chase bugs so that we can move to 2.02 release. So from now on if you
> think that your patch should be included in 2.02 rather than in 2.03,
> please add [2.02] to the beginning of your email subject

Woohoo!!! Thank you!

> 
> The tarball is available at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> and signature at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> 
> Signed with following fingerprint:
>  E53D 497F 3FA4 2AD8 C9B4  D1E8 35A9 3B74 E82E 4209
> 
> It's also available as a signed tag grub-2.02-beta3 in official git
> repository.
> 
> If you don't have xz support alternatively you may consider files
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> and signature at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> 
> 
> 
> 



> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel

Re: 2.02~beta3 release

[Andrei Borzenkov]

29.02.2016 11:16, Vladimir 'phcoder' Serbinenko пишет:
> On Sunday, February 28, 2016, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
> 
>> 28.02.2016 19:40, Andrei Borzenkov пишет:
>>> You forgot to tag GIT. I think we discussed that release tag should be
>>> signed, not sure if this is achievable.
>>
>> Oh, sorry, was confused that tag name pattern is different from beta2.
>> We should pick one rule and stick to it (I do not really care which).
>>
>> I added signed tag in both formats now. Thank you for reminder.
> 


Something is strange.

bor@bor-Latitude-E5450:~/src/grub$ git log -n2 grub-2.02-beta3
commit b4fc7bc2fdfbcb726e9094d8b1848b393364de77
Merge: c4748ea 8207874
Author: Vladimir Serbinenko <phcoder@gmail.com>
Date:   Sun Feb 28 15:22:52 2016 +0100

    Merge branch 'master' into next

commit 8207874e5d0d05159fd8c531c87f0f6e4653b8a6
Author: Vladimir Serbinenko <phcoder@gmail.com>
Date:   Sun Feb 28 03:07:41 2016 +0100

    Release 2.02~beta3

bor@bor-Latitude-E5450:~/src/grub$ git log -n2 master
commit d017ea8ede3f76aaf6b6c9dabe3e96af0eebd395
Author: Andrei Borzenkov <arvidjaar@gmail.com>
Date:   Sun Feb 28 21:52:08 2016 +0300

    NEWS update

commit 8207874e5d0d05159fd8c531c87f0f6e4653b8a6
Author: Vladimir Serbinenko <phcoder@gmail.com>
Date:   Sun Feb 28 03:07:41 2016 +0100

    Release 2.02~beta3


I expected tag to point to commit
8207874e5d0d05159fd8c531c87f0f6e4653b8a6 on master.

Re: 2.02~beta3 release

[Vladimir 'phcoder' Serbinenko]

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

My mistake. I'm going to fix it

Le mar. 1 mars 2016 20:10, Andrei Borzenkov <arvidjaar@gmail.com> a écrit :

> 29.02.2016 11:16, Vladimir 'phcoder' Serbinenko пишет:
> > On Sunday, February 28, 2016, Andrei Borzenkov <arvidjaar@gmail.com>
> wrote:
> >
> >> 28.02.2016 19:40, Andrei Borzenkov пишет:
> >>> You forgot to tag GIT. I think we discussed that release tag should be
> >>> signed, not sure if this is achievable.
> >>
> >> Oh, sorry, was confused that tag name pattern is different from beta2.
> >> We should pick one rule and stick to it (I do not really care which).
> >>
> >> I added signed tag in both formats now. Thank you for reminder.
> >
>
>
> Something is strange.
>
> bor@bor-Latitude-E5450:~/src/grub$ git log -n2 grub-2.02-beta3
> commit b4fc7bc2fdfbcb726e9094d8b1848b393364de77
> Merge: c4748ea 8207874
> Author: Vladimir Serbinenko <phcoder@gmail.com>
> Date:   Sun Feb 28 15:22:52 2016 +0100
>
>     Merge branch 'master' into next
>
> commit 8207874e5d0d05159fd8c531c87f0f6e4653b8a6
> Author: Vladimir Serbinenko <phcoder@gmail.com>
> Date:   Sun Feb 28 03:07:41 2016 +0100
>
>     Release 2.02~beta3
>
> bor@bor-Latitude-E5450:~/src/grub$ git log -n2 master
> commit d017ea8ede3f76aaf6b6c9dabe3e96af0eebd395
> Author: Andrei Borzenkov <arvidjaar@gmail.com>
> Date:   Sun Feb 28 21:52:08 2016 +0300
>
>     NEWS update
>
> commit 8207874e5d0d05159fd8c531c87f0f6e4653b8a6
> Author: Vladimir Serbinenko <phcoder@gmail.com>
> Date:   Sun Feb 28 03:07:41 2016 +0100
>
>     Release 2.02~beta3
>
>
> I expected tag to point to commit
> 8207874e5d0d05159fd8c531c87f0f6e4653b8a6 on master.
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>

[-- Attachment #2: Type: text/html, Size: 2743 bytes --]

Re: 2.02~beta3 release

[Vladimir 'phcoder' Serbinenko]

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

Fixed. Thank you for reporting

Le Tue, Mar 1, 2016 à 11:14 AM, Vladimir 'phcoder' Serbinenko <
phcoder@gmail.com> a écrit :

> My mistake. I'm going to fix it
>
> Le mar. 1 mars 2016 20:10, Andrei Borzenkov <arvidjaar@gmail.com> a
> écrit :
>
>> 29.02.2016 11:16, Vladimir 'phcoder' Serbinenko пишет:
>> > On Sunday, February 28, 2016, Andrei Borzenkov <arvidjaar@gmail.com>
>> wrote:
>> >
>> >> 28.02.2016 19:40, Andrei Borzenkov пишет:
>> >>> You forgot to tag GIT. I think we discussed that release tag should be
>> >>> signed, not sure if this is achievable.
>> >>
>> >> Oh, sorry, was confused that tag name pattern is different from beta2.
>> >> We should pick one rule and stick to it (I do not really care which).
>> >>
>> >> I added signed tag in both formats now. Thank you for reminder.
>> >
>>
>>
>> Something is strange.
>>
>> bor@bor-Latitude-E5450:~/src/grub$ git log -n2 grub-2.02-beta3
>> commit b4fc7bc2fdfbcb726e9094d8b1848b393364de77
>> Merge: c4748ea 8207874
>> Author: Vladimir Serbinenko <phcoder@gmail.com>
>> Date:   Sun Feb 28 15:22:52 2016 +0100
>>
>>     Merge branch 'master' into next
>>
>> commit 8207874e5d0d05159fd8c531c87f0f6e4653b8a6
>> Author: Vladimir Serbinenko <phcoder@gmail.com>
>> Date:   Sun Feb 28 03:07:41 2016 +0100
>>
>>     Release 2.02~beta3
>>
>> bor@bor-Latitude-E5450:~/src/grub$ git log -n2 master
>> commit d017ea8ede3f76aaf6b6c9dabe3e96af0eebd395
>> Author: Andrei Borzenkov <arvidjaar@gmail.com>
>> Date:   Sun Feb 28 21:52:08 2016 +0300
>>
>>     NEWS update
>>
>> commit 8207874e5d0d05159fd8c531c87f0f6e4653b8a6
>> Author: Vladimir Serbinenko <phcoder@gmail.com>
>> Date:   Sun Feb 28 03:07:41 2016 +0100
>>
>>     Release 2.02~beta3
>>
>>
>> I expected tag to point to commit
>> 8207874e5d0d05159fd8c531c87f0f6e4653b8a6 on master.
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
>

[-- Attachment #2: Type: text/html, Size: 3134 bytes --]

Re: 2.02~beta3 release

[Vladimir 'phcoder' Serbinenko]

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

>
> onsider files
> > http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> > and signature at
> > http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
>
> Thanks, this is a great step.  What is the timeline we're planning to
> follow?
>
> I started a separate thread to collect pending tasks. I'd like to have
list of tasks in 1 week. If it's not too large I hope to have rc1 one month
from now and release in 2 months

> --
>         Peter
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>

[-- Attachment #2: Type: text/html, Size: 1318 bytes --]

Re: 2.02~beta3 release

[adrian15]

Super Grub2 Disk 2.02s4 which it's based on:

2.02~beta3

is available. More information at:

http://www.supergrubdisk.org/2016/03/11/super-grub2-disk-2-02s4-released/

.

Well, I usually don't make those announcements here but I wanted to let 
you know that I have told my users:

"
If Super Grub2 Disk 2.02s3 let you boot into your OS but Super Grub2 
Disk 2.02s4 does not let you boot into your OS please report it so that 
we can report it back to the grub team which tries to release a Grub 
2.02 stable release.
"

So, yes, hopefully someone will give us some feedback on regressions and 
we can pass it to you so that you can make a better rc1.

Thank you for hard work on Grub.

adrian15

El 28/02/16 a las 15:21, Vladimir 'φ-coder/phcoder' Serbinenko escribió:
> Hello, all. I've just released 2.02~beta3. The goal of this release is
> to chase bugs so that we can move to 2.02 release. So from now on if you
> think that your patch should be included in 2.02 rather than in 2.03,
> please add [2.02] to the beginning of your email subject
>
> The tarball is available at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> and signature at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
>
> Signed with following fingerprint:
>   E53D 497F 3FA4 2AD8 C9B4  D1E8 35A9 3B74 E82E 4209
>
> It's also available as a signed tag grub-2.02-beta3 in official git
> repository.
>
> If you don't have xz support alternatively you may consider files
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
> and signature at
> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>

-- 
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/