| Summary: | Community BOM project/product | ||
|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Nick Cross <ncross> |
| Component: | Build and Assembly | Assignee: | Geoffrey De Smet <gdesmet> |
| Status: | CLOSED NOTABUG | QA Contact: | Lukáš Petrovický <lpetrovi> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0.0 | CC: | etirelli, gdesmet, ncross, rzhang |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-04 10:24:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Nick Cross
2013-09-11 09:20:21 UTC
@Edson: once you set this up, the "product branch sync" will need sync for these 2 repo's too, just like to does for droolsjbpm/drools and jboss-integration/drools etc. Geoffrey, we need to discuss this as I am not sure a simple branch is enough here? If the goal is to have separate community and product BOMs, don't we need a completely separate "bom" with a different GAV? @Edson not entirely, just like we don't need a different groupId-artifactId for the productized drools bits. We do need a different version, and just like the productized drools bits, we 'll use the suffix "-redhat-0" etc. This issue can be close. We can follow the process as it is (creating tag timely for product ER release). |