Mark Martin wrote: > Assuming you narrow the scope of discussion to: "how do things go > from /contrib to /dev and /release", then the fundamental question I > asked about who does this remains. The original package submitter? > Some entity who is staffed and funded to provide ongoing maintenance > and has a vested interest in seeing things make the > quality+integration assurance leap? Does the leap mean it goes from > .spec file to (determine a consolidation, tweak sources, ARC, RTI?) > Do the original package maintainers wash their hands of the package > once it makes the leap (and stay on as maintainers if it never leaves > /contrib)?
1) Please remove the build process from the discussion. The Source Juicer uses spec files, but so does the Desktop consolidation and maybe other consolidation will. 2) Remember that the contrib repo is a valid end point for user packages. release is another user centric repo. Most contrib reopo packages will not advance to the release repo which is fine. 3) There are many high quality packages in the contrib repo and if a maintainer abandons a package someone else will be asked to pick it up. The main difference between the contrib repo and the release repo is Sun is on the hook to support release packages. With contrib repo packages you only have the maintainer and some maintainers may not be as responsive as others. Cheers, Jim
