Hi, If we want we could use the "labels" for tag some issues.
regards, François Papon [email protected] Le 10/09/2018 à 09:11, Jean-Baptiste Onofré a écrit : > Hi, > > So, by karaf-build, you mean both issues targeted on the build tooling > we provide and the build itself. > > My point is: what's the difference if these issues are in the karaf > component ? Is it really helpful for us or our users to have karaf-build > component (used in filter for instance) ? > > Personally, I have filter using fixVersion (to prepare release content), > but I never use component. > > Regards > JB > > On 10/09/2018 07:05, Grzegorz Grzybek wrote: >> pon., 10 wrz 2018 o 06:40 Francois Papon <[email protected]> >> napisał(a): >> >>> Hi Grzegorz, >>> >>> Can you explain why you think it would be nice to have a maven or build >>> component ? >>> >> I was just thinking about distinguishing between runtime and buildtime >> issues. >> Looking at the components[1], I see karaf-tooling has 49 issues - not that >> much comparing to karaf-features or karaf-core. >> So I don't think "build" component is that crucial after all. >> >> regards >> Grzegorz Grzybek >> --- >> [1]: https://issues.apache.org/jira/projects/KARAF/summary/statistics >> >> >>> regards, >>> >>> François Papon >>> [email protected] >>> >>> Le 10/09/2018 à 08:34, Grzegorz Grzybek a écrit : >>>> Hello >>>> >>>> That'd be great to have fewer components. However, maybe it would be good >>>> to have a component like "maven" or "build" too? >>>> >>>> regards >>>> Grzegorz Grzybek >>>> >>>> pon., 10 wrz 2018 o 04:54 Francois Papon <[email protected]> >>>> napisał(a): >>>> >>>>> Hi JB, >>>>> >>>>> +1 ! >>>>> >>>>> Full agree with that :) >>>>> >>>>> regards, >>>>> >>>>> François Papon >>>>> [email protected] >>>>> >>>>> Le 09/09/2018 à 23:03, Jean-Baptiste Onofré a écrit : >>>>>> Hi team, >>>>>> >>>>>> Now, in Jira, we have a bunch of components: karaf-core, karaf-test, >>>>>> cellar-config, ... >>>>>> >>>>>> Most of the time, when an user creates a Jira, he doesn't set the >>>>>> component at all. >>>>>> >>>>>> So, the components should be used by us, but obviously, I don't think >>>>>> the granularity we have today is helpful. >>>>>> >>>>>> I propose the following components: >>>>>> >>>>>> - karaf >>>>>> - cellar >>>>>> - cave >>>>>> - decanter >>>>>> - website >>>>>> >>>>>> That's the core components we manage in the project. >>>>>> >>>>>> On the other hand, we have also old versions in Jira, with unreleased >>>>>> status. >>>>>> >>>>>> I would like to do a cleanup, removing the old versions (not released) >>>>>> on branches. If we have Jira issues on this version, I will remove the >>>>>> fix version (or even close the issue). >>>>>> >>>>>> Thoughts ? >>>>>> >>>>>> Regards >>>>>> JB >>>
