Time for an xfsprogs "alpha1" release?
With all of the changes for CRC filesystems in xfsprogs git now, I'm wondering if it'd be a good idea to do a "3.2.0-alpha1" sort of release.
I know it's not yet feature complete, but I think there would be value in getting a version-stamped tarball out there for testing - it could filter to rawhide-ish distros, and get a bit more airtime while the remaining bits get worked out.
We'd probably want a nice readme about what's new and what's not yet done, caveats, etc, but I think it'd be worth getting it out there into the hands of willing testers, w/o requiring them to do a build from git.
Thoughts?
Thanks,
-Eric
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 10 lines · Eric Sandeen
With all of the changes for CRC filesystems in xfsprogs git now, I'm wondering if it'd be a good idea to do a "3.2.0-alpha1" sort of release.
I know it's not yet feature complete, but I think there would be value in getting a version-stamped tarball out there for testing - it could filter to rawhide-ish distros, and get a bit more airtime while the remaining bits get worked out.
We'd probably want a nice readme about what's new and what's not yet done, caveats, etc, but I think it'd be worth getting it out there into the hands of willing testers, w/o requiring them to do a build from git.
Thoughts?
Thanks,
-Eric
If it's relevant, openSUSE's factory release is currently in feature freeze for bleeding edge stuff, but it should open back up in a week or two. (After they branch off the next stable release.)
If you don't know factory => openSUSE => SUSE (SLES)
much like rawhide => fedora => redhat
Greg
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 11 lines · Eric Sandeen
With all of the changes for CRC filesystems in xfsprogs git now, I'm wondering if it'd be a good idea to do a "3.2.0-alpha1" sort of release.
I know it's not yet feature complete, but I think there would be value in getting a version-stamped tarball out there for testing - it could filter to rawhide-ish distros, and get a bit more airtime while the remaining bits get worked out.
We'd probably want a nice readme about what's new and what's not yet done, caveats, etc, but I think it'd be worth getting it out there into the hands of willing testers, w/o requiring them to do a build from git.
Thoughts?
Thanks,
-Eric
Good idea, but xfsprogs is in a state that it can't compile:
http://oss.sgi.com/archives/xfs/2013-09/msg00396.html
Patch 31 v3 / 55 is broken. It is missing xfs_sb.c and has an extra xfs_mount.c.
If you want it this week, we could do the corrections or wait for Dave to repost.
--Mark.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 15 lines · Mark Tinguely
Quoted 11 lines · Eric Sandeen
With all of the changes for CRC filesystems in xfsprogs git now, I'm wondering if it'd be a good idea to do a "3.2.0-alpha1" sort of release.
I know it's not yet feature complete, but I think there would be value in getting a version-stamped tarball out there for testing - it could filter to rawhide-ish distros, and get a bit more airtime while the remaining bits get worked out.
We'd probably want a nice readme about what's new and what's not yet done, caveats, etc, but I think it'd be worth getting it out there into the hands of willing testers, w/o requiring them to do a build from git.
Thoughts?
Thanks,
-EricGood idea, but xfsprogs is in a state that it can't compile:
Quoted 7 lines
http://oss.sgi.com/archives/xfs/2013-09/msg00396.htmlPatch 31 v3 / 55 is broken. It is missing
xfs_sb.cand has an extraxfs_mount.c.If you want it this week, we could do the corrections or wait for Dave to repost.
hm? The git tree builds fine here, anyway (modulo some warnings).
so quick, cut an alpha1 before it breaks. ;)
(but if you mean: we should get the latest stuff on the list in first, and fix it so it builds - ok - but there will probably always be more stuff to pull in, so at some point when we have a reasonable amount of it in place, we could cut a test release? There's always "alpha2"...)
-Eric
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 26 lines · Eric Sandeen
Quoted 15 lines · Mark Tinguely
Quoted 11 lines · Eric Sandeen
With all of the changes for CRC filesystems in xfsprogs git now, I'm wondering if it'd be a good idea to do a "3.2.0-alpha1" sort of release.
I know it's not yet feature complete, but I think there would be value in getting a version-stamped tarball out there for testing - it could filter to rawhide-ish distros, and get a bit more airtime while the remaining bits get worked out.
We'd probably want a nice readme about what's new and what's not yet done, caveats, etc, but I think it'd be worth getting it out there into the hands of willing testers, w/o requiring them to do a build from git.
Thoughts?
Thanks,
-EricGood idea, but xfsprogs is in a state that it can't compile:
Quoted 7 lines
http://oss.sgi.com/archives/xfs/2013-09/msg00396.htmlPatch 31 v3 / 55 is broken. It is missing
xfs_sb.cand has an extraxfs_mount.c.If you want it this week, we could do the corrections or wait for Dave to repost.
hm? The git tree builds fine here, anyway (modulo some warnings).
Quoted 8 lines
so quick, cut an alpha1 before it breaks. ;)
(but if you mean: we should get the latest stuff on the list in first, and fix it so it builds - ok - but there will probably always be more stuff to pull in, so at some point when we have a reasonable amount of it in place, we could cut a test release? There's always "alpha2"...)
-Eric
Yep, simple to fix. I manually pulled in xfs_sb.c to make sure 47 v2 / 55 was still okay. I can have a tar tomorrow.
--Mark.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 29 lines · Mark Tinguely
Quoted 28 lines · Eric Sandeen
Quoted 15 lines · Mark Tinguely
Quoted 11 lines · Eric Sandeen
With all of the changes for CRC filesystems in xfsprogs git now, I'm wondering if it'd be a good idea to do a "3.2.0-alpha1" sort of release.
I know it's not yet feature complete, but I think there would be value in getting a version-stamped tarball out there for testing - it could filter to rawhide-ish distros, and get a bit more airtime while the remaining bits get worked out.
We'd probably want a nice readme about what's new and what's not yet done, caveats, etc, but I think it'd be worth getting it out there into the hands of willing testers, w/o requiring them to do a build from git.
Thoughts?
Thanks,
-EricGood idea, but xfsprogs is in a state that it can't compile:
Quoted 7 lines
http://oss.sgi.com/archives/xfs/2013-09/msg00396.htmlPatch 31 v3 / 55 is broken. It is missing
xfs_sb.cand has an extraxfs_mount.c.If you want it this week, we could do the corrections or wait for Dave to repost.
hm? The git tree builds fine here, anyway (modulo some warnings).
so quick, cut an alpha1 before it breaks. ;)
Quoted 8 lines
Quoted 6 lines
(but if you mean: we should get the latest stuff on the list in first, and fix it so it builds - ok - but there will probably always be more stuff to pull in, so at some point when we have a reasonable amount of it in place, we could cut a test release? There's always "alpha2"...)
-Eric
Yep, simple to fix. I manually pulled in
xfs_sb.cto make sure 47 v2 / 55 was still okay. I can have a tar tomorrow.
Well, any released tarball needs to come from a tagged git tree, of course.
So if the new series needs to go in first, and needs fixes before that, we can wait. Or if it's ok as it is now, and just missing some functionality, we could cut it now as alpha1, and cut alpha2 next.... *shrug*. Not a huge rush, just pick a time when the tree is useful to get some wider testing, and cut a pre-release from that point in git.
-Eric
Quoted 1 line
--Mark.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs