| Summary: | add Spring Data Commons to Orbit | ||
|---|---|---|---|
| Product: | [Tools] Orbit | Reporter: | Angelo ZERR <azerr> |
| Component: | bundles | Assignee: | Orbit Bundles <orbit.bundles-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams, wim.jongman |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Angelo ZERR
Let me clarify the process a little. As mentioned in bug 367064, you need a CQ for third party dependencies, but "a CQ" is not an Orbit bugzilla entry. The CQ system is similar to bugzilla system, but separate. A CQ must be open (first) by a committer in the Nebula project for Nebula to use that third party code. This is done through the Foundation Portal, not directly using a bugzilla-like system. Once that CQ is approved, then another CQ must be open by an Orbit committer (preferably one who is also a Nebula committer) that the third party bundle be put in Orbit. Then once that is approved, a bugzilla here in Oribt could be opened that would say simply "add org.springframework.data.domain to Orbit" and you might reference the Orbit CQ. Once the Orbit CQ is approved, then (someone) could add it to Orbit. Once in Orbit, then new, additional uses of it by other projects can be done by a CQ which says (basically) re-use an Orbit bundle. Rather than mark this bug as "invalid", I'll re-title it to be what it would be after all the CQ work is finished. Hope that helps. Let us know if questions. But, I think the next step is for a Nebula committer to enter the CQ if they desire to have that dependency in Nebula. |