Hi everyone, I''ve tagged the current btrfs-progs repo as v3.12. The new idea is that instead of making the poor distros pull from git, I''ll be creating tagged releases at roughly the same pace as Linus cuts kernels. Given the volume of btrfs-progs patches, we should have enough new code and fixes to justify releases at least as often as the kernel. Of course, if there are issues that need immediate attention, I''ll tag a .y release (v3.12.1 for example). If the progs changes slow down, we might skip a version. But tracking kernel version numbers makes it easier for me to line up bug reports, mostly because I already devote a fair number of brain cells to remembering how old each kernel is. Just let me know if there are any questions. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
I''m humbly totally unqualified to comment but that sounds like an excellent idea. Thanks. I can''t say for others but I was put off by the 0.19 forever eternal version which pushed me to investigate GIT... I''m sure that has been putting off many people including distro assemblers. Just for some positive comment: Good progress, thanks. Regards, Martin (OK, that''s the last of the positives for the Christmas present. Back to bugging! ;-) ) On 25/11/13 21:45, Chris Mason wrote:> Hi everyone, > > I''ve tagged the current btrfs-progs repo as v3.12. The new idea is that > instead of making the poor distros pull from git, I''ll be creating > tagged releases at roughly the same pace as Linus cuts kernels. > > Given the volume of btrfs-progs patches, we should have enough new code > and fixes to justify releases at least as often as the kernel. Of > course, if there are issues that need immediate attention, I''ll tag a .y > release (v3.12.1 for example). > > If the progs changes slow down, we might skip a version. But tracking > kernel version numbers makes it easier for me to line up bug reports, > mostly because I already devote a fair number of brain cells to > remembering how old each kernel is. > > Just let me know if there are any questions. > > -chris-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 11/25/13, 3:45 PM, Chris Mason wrote:> Hi everyone, > > I''ve tagged the current btrfs-progs repo as v3.12. The new idea is that > instead of making the poor distros pull from git, I''ll be creating > tagged releases at roughly the same pace as Linus cuts kernels. > > Given the volume of btrfs-progs patches, we should have enough new code > and fixes to justify releases at least as often as the kernel. Of > course, if there are issues that need immediate attention, I''ll tag a .y > release (v3.12.1 for example). > > If the progs changes slow down, we might skip a version. But tracking > kernel version numbers makes it easier for me to line up bug reports, > mostly because I already devote a fair number of brain cells to > remembering how old each kernel is. > > Just let me know if there are any questions.Cool! I''ve built it for Fedora 19, 20, and rawhide, updates should trickle out soon. -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Nov 25, 2013 at 10:45 PM, Chris Mason <chris.mason@fusionio.com> wrote:> Hi everyone, > > I''ve tagged the current btrfs-progs repo as v3.12. The new idea is that > instead of making the poor distros pull from git, I''ll be creating > tagged releases at roughly the same pace as Linus cuts kernels.Great stuff Chris! The new version is now in Arch''s [testing] repository. Cheers, Tom -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html