-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrew Gaffney wrote: > That's not the issue. The issue is that there should *already* be a > releng liason, but nobody from releng seems to know anything about this > project. >
I dunno . . . does releng really need to be involved, except if these stage4 tarballs were to be included on regular 200X.X media? I simply don't see why this has to be a releng project -- I'm surprised anyone thinks it should be. Give releng a break; they have enough hard work to do. That's my mindset, anyway. Seems to be that any project could roll up a stage4 release for their stuff (LAMP, GNAP type stuff comes to mind immediately) using existing stages, since they've already been validated, else releng wouldn't have released 'em in the first place. The potentially tricky issue I see is the question of support -- supposing one project screws up their canned stage -- who takes the blame? Who takes the QA hit? Probably there should be some central guidelines/plans/docs on the stage4 process, so that it can be adhered to and be beneficial for more than one project. I'm still getting used to this new definition of "stage4" -- on the forums at least, the concept of stage4 has been around for years, though its definition refers to canned backups of one's current system. ;) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFEZzJrsJQqN81j74RAv4IAJ93bRpfuLvJ7vrmquYi+cETE/J+VgCghXZv hIokAc23Y7BZfacMFe70wmI= =hAV2 -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
