v2_02_178 annotated tag has been created

v2_02_178 annotated tag has been created

[Marian Csontos]

Gitweb:        https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=97926eae03282419984fe3264dea6108d55df019
Commit:        97926eae03282419984fe3264dea6108d55df019
Parent:        0000000000000000000000000000000000000000
Author:        Marian Csontos <mcsontos@redhat.com>
AuthorDate:    2018-06-13 12:16 +0000
Committer:     Marian Csontos <mcsontos@redhat.com>
CommitterDate: 2018-06-13 12:16 +0000

annotated tag: v2_02_178 has been created
	    at 97926eae03282419984fe3264dea6108d55df019 (tag)
       tagging 06accf13953d0bc3a5ffef918e562bad1d802249 (commit)
      replaces v2_02_178-rc1

Release 2.02.178

Major changes:

Remove support for historical lvm1 and GFS pool formats.
Major changes in label scanning.
Use libaio.

See doc/release-notes/2.02.178 for details.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAABAgAGBQJbIQszAAoJELkRJDHlCQOft38P/3iW0pILWiZudLTPvNmUEQUa
6lY8v8jmWVbWUhvKFYFq3hDTkeS1cz5wem1AfmUJxE+A6Av26ESje5efBPpVCM8d
x4OTh1azEHjD2y42tN+pdsJT40ka56XCxPDYSssbv8DMWXjk322orv7zCAAfM9yH
ly9KF84mcko09vx5cVBrJiJPGNykdYY+fPuAl7nS1GPf2fWg4yeHHv68ghZ3gh6j
To5d2YsflhJIecmUsOI3+MucdPjfxFUjQmTOuaio7UwlXAMNq7wlqdD24zxzkmVg
qk0NrvX0SHjh/RF9VhmjF06TCPJdcINf6odJ1sOMYa9HsXyBBZSqdyCNnYbv+IDD
6cT6DranKVaeVC/TMKKWFiw0eaONQ+wvgPdFKmSjsTbiRhtPEEyGQkmL2MguSfoF
30ilB6codzK7A/aH4Lgj/Kd3aV934Ia1Tk0UlQCsNrDMhU/6e3FeoDBfWhJ/zB+5
JTC7dKcCr8JydZJx85Bsls6ak0HmeGMMMYoOJW40RQrUrI3cq6qFD7qWM5h/tI5d
EjeP1qIMjAIgob8usHPFQNZh9HiFi2Z6O/UB97AyMIgJ4kMl+ZxbCLvcLzDlOcSn
6z/JpJpzPsrLsZpFFFjlzExioYw7bZKsFQye7FU7J2MpeRHKWxP+ciOop6hh4Cak
rhzJRZs2SFt1no/T/cWY
=3FED
-----END PGP SIGNATURE-----

Marian Csontos (1):
      pre-release

v2_02_178 annotated tag has been created

[Gang He]

Hello Marian and List,

Congratulations first. 
As you know, after v2_02_178, LVM in master branch will jump to v3_0_0 with some huge changes.
But, if we find some bugs in the future on v2_02_178, the fix will be submitted to which branch? 
beside master branch, do we have a v2.02_178.x  (or v2.02_179) to maintain LVM v2 for a few years.

Thanks
Gang 


>>> On 2018/6/13 at 20:38, in message
<201806131238.w5DCcUL1026320@lists01.pubmisc.prod.ext.phx2.redhat.com>, Marian
Csontos <mcsontos@sourceware.org> wrote:
> Gitweb:        
> https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=97926eae03282419984fe32 
> 64dea6108d55df019
> Commit:        97926eae03282419984fe3264dea6108d55df019
> Parent:        0000000000000000000000000000000000000000
> Author:        Marian Csontos <mcsontos@redhat.com>
> AuthorDate:    2018-06-13 12:16 +0000
> Committer:     Marian Csontos <mcsontos@redhat.com>
> CommitterDate: 2018-06-13 12:16 +0000
> 
> annotated tag: v2_02_178 has been created
> 	    at 97926eae03282419984fe3264dea6108d55df019 (tag)
>        tagging 06accf13953d0bc3a5ffef918e562bad1d802249 (commit)
>       replaces v2_02_178-rc1
> 
> Release 2.02.178
> 
> Major changes:
> 
> Remove support for historical lvm1 and GFS pool formats.
> Major changes in label scanning.
> Use libaio.
> 
> See doc/release-notes/2.02.178 for details.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
> 
> iQIcBAABAgAGBQJbIQszAAoJELkRJDHlCQOft38P/3iW0pILWiZudLTPvNmUEQUa
> 6lY8v8jmWVbWUhvKFYFq3hDTkeS1cz5wem1AfmUJxE+A6Av26ESje5efBPpVCM8d
> x4OTh1azEHjD2y42tN+pdsJT40ka56XCxPDYSssbv8DMWXjk322orv7zCAAfM9yH
> ly9KF84mcko09vx5cVBrJiJPGNykdYY+fPuAl7nS1GPf2fWg4yeHHv68ghZ3gh6j
> To5d2YsflhJIecmUsOI3+MucdPjfxFUjQmTOuaio7UwlXAMNq7wlqdD24zxzkmVg
> qk0NrvX0SHjh/RF9VhmjF06TCPJdcINf6odJ1sOMYa9HsXyBBZSqdyCNnYbv+IDD
> 6cT6DranKVaeVC/TMKKWFiw0eaONQ+wvgPdFKmSjsTbiRhtPEEyGQkmL2MguSfoF
> 30ilB6codzK7A/aH4Lgj/Kd3aV934Ia1Tk0UlQCsNrDMhU/6e3FeoDBfWhJ/zB+5
> JTC7dKcCr8JydZJx85Bsls6ak0HmeGMMMYoOJW40RQrUrI3cq6qFD7qWM5h/tI5d
> EjeP1qIMjAIgob8usHPFQNZh9HiFi2Z6O/UB97AyMIgJ4kMl+ZxbCLvcLzDlOcSn
> 6z/JpJpzPsrLsZpFFFjlzExioYw7bZKsFQye7FU7J2MpeRHKWxP+ciOop6hh4Cak
> rhzJRZs2SFt1no/T/cWY
> =3FED
> -----END PGP SIGNATURE-----
> 
> Marian Csontos (1):
>       pre-release
> 
> --
> lvm-devel mailing list
> lvm-devel at redhat.com 
> https://www.redhat.com/mailman/listinfo/lvm-devel

v2_02_178 annotated tag has been created

[Marian Csontos]

On 06/14/2018 04:31 AM, Gang He wrote:
> Hello Marian and List,
> 
> Congratulations first.
> As you know, after v2_02_178, LVM in master branch will jump to v3_0_0 with some huge changes.
> But, if we find some bugs in the future on v2_02_178, the fix will be submitted to which branch?
> beside master branch, do we have a v2.02_178.x  (or v2.02_179) to maintain LVM v2 for a few years.

Hi Gang, there is *2018-06-01-stable* branch for 2.02.N development i.e. 
mainly bugfixes.

If needed, there is also *2018-05-17-put-format1-and-pool-back* branch, 
with one patch adding back the LVM1 and GFS pools which applies cleanly 
on top of 2.02.178.

Cheers!

Marian

v2_02_178 annotated tag has been created

[Gang He]

Hello Marian,

This information is very useful for other people, which want to track lvm the bug fixes for v2.02.xxx. 

Thanks a lot, 
Gang

>>> On 2018/6/14 at 15:46, in message
<05d3e93c-0fae-e1f8-c2cd-6e698eb60d02@redhat.com>, Marian Csontos
<mcsontos@redhat.com> wrote:
> On 06/14/2018 04:31 AM, Gang He wrote:
>> Hello Marian and List,
>> 
>> Congratulations first.
>> As you know, after v2_02_178, LVM in master branch will jump to v3_0_0 with 
> some huge changes.
>> But, if we find some bugs in the future on v2_02_178, the fix will be 
> submitted to which branch?
>> beside master branch, do we have a v2.02_178.x  (or v2.02_179) to maintain 
> LVM v2 for a few years.
> 
> Hi Gang, there is *2018-06-01-stable* branch for 2.02.N development i.e. 
> mainly bugfixes.
> 
> If needed, there is also *2018-05-17-put-format1-and-pool-back* branch, 
> with one patch adding back the LVM1 and GFS pools which applies cleanly 
> on top of 2.02.178.
> 
> Cheers!
> 
> Marian