Hide Forgot
Currently the community BOM in https://github.com/jboss-integration/jboss-integration-platform-bom is used for both project development and product. Would it be useful to separate this out so there is a product branch that is tagged for the different releases. This would allow development (e.g. moving to EAP 6.1.1) while allowing product to stay on 6.1.0.
@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).