I see 4.5.2_1 out in maven central [1]. Any chance we might be able to promote 3.7.0_2 as well?
- Bob [1] http://repo.maven.apache.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.brave-zipkin/ On 9/6/2017 7:19 AM, Bob Paulin wrote: > Hi, > > I would appreciate if 3.7.x could be reintroduced. Thanks for offering > that. I agree brave 4.5.4 would superseded the 4.2.0. However one of > the reasons I offered the patch to 4.2.0 is the most recent camel > (2.19.2) supports brave 4.2.0 in the parent/pom.xml. 4.5.2 is supported > in the master branch of Camel at the moment and I'm not sure the > versions are backwards compatible. I thought I saw the next targeted > release of Service Mix was looking to support 2.19 camel so the 4.2.0 > might be important as well. Thanks again! > > - Bob > > > On 9/6/2017 6:54 AM, Jean-Baptiste Onofré wrote: >> We agreed to maintain bundle major version. For instance 4.5.4 will >> superseded any 4.5.x previous versions. >> However 4.5.x and 3.7.x are independent. >> >> I can reintroduce 3.7.x if needed. >> >> The purpose is to reduce the number of minor bundles versions: it's painful >> to maintain and the git repository is pretty slow with bunch of unused >> folders. >> >> Regards >> JB >> >> On Sep 6, 2017, 13:48, at 13:48, Bob Paulin <[email protected]> wrote: >>> Thanks for the reply. So since 4.2.0_1 was never the most current and >>> 3.7.0_2 is a change to the existing bundle (that is also not the most >>> recent) would those never be released? Just trying to understand how a >>> non service mix project might use those versions. In both situations >>> I'm trying to use zipkin (Thrift) with Karaf and Camel but I'm a bit >>> unsure how to proceed with getting the dependencies (3.7.0_2, 4.2.0_1) >>> if they are not released. Is there another process for releasing those >>> bundles? At the time I submitted the patches 3.7.0_1 was the most >>> current release. >>> >>> >>> - Bob >>> >>> >>> On 9/5/2017 11:14 PM, Jean-Baptiste Onofré wrote: >>>> Hi Bob, >>>> >>>> yes: we release and maintain only the latest version. So, I did >>> bundle >>>> for 4.5.2 and cleanup previous version. >>>> >>>> Jira keeps the history of the "version steps". >>>> >>>> Regards >>>> JB >>>> >>>> On 09/06/2017 03:56 AM, Bob Paulin wrote: >>>>> Hi, >>>>> >>>>> Quick question on the service mix release process. There's JIRA's >>>>> related to updates to the brave-zipkin at version 4.5.2, 4.2.0, and >>>>> 3.7.0. I only see the 4.5.2 in the Staging Repository. Is that >>>>> expected? >>>>> >>>>> - Bob Paulin >>>>> >>>>> >>>>> On 9/5/2017 7:01 AM, Freeman Fang wrote: >>>>>> +1 >>>>>> Thanks! >>>>>> －－－－－－－－－－－－－ >>>>>> Freeman(Yue) Fang >>>>>> >>>>>> Red Hat, Inc. >>>>>> FuseSource is now part of Red Hat >>>>>> >>>>>> >>>>>> >>>>>>> On Sep 5, 2017, at 4:13 PM, Jean-Baptiste Onofré <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> I submit the ServiceMix 2017.08 bundles set to your vote. >>>>>>> >>>>>>> Release Notes: >>>>>>> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311206&version=12341277 >>>>>>> Staging Repository: >>>>>>> >>> https://repository.apache.org/content/repositories/orgapacheservicemix-1203/ >>>>>>> Please vote to approve this release: >>>>>>> >>>>>>> [ ] +1 Approve the release >>>>>>> [ ] -1 Do not approve the release (please provide specific >>> comments) >>>>>>> This vote will be open for 48 hours. >>>>>>> >>>>>>> Regards >>>>>>> JB >>>>>>> -- >>>>>>> Jean-Baptiste Onofré >>>>>>> [email protected] >>>>>>> http://blog.nanthrax.net >>>>>>> Talend - http://www.talend.com >
signature.asc
Description: OpenPGP digital signature
