[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orbit-dev] How to contribute
|
Hi,
thanks. I created some bugs to get started:
367476 org.apache.commons.primitives
367477 com.google.inject
367478 com.google.inject.assistedinject
367479 com.google.inject.multibindings
Expect more to come as soon as the CQs are approved. I'm also looking forward to contact current users of Guava r10 and Jersey 1.8 as they already provide those bundles and we need them too. Maybe we can add them to Orbit together.
Regards,
Johannes Lerch
2011/12/16 Chris Aniszczyk
<caniszczyk@xxxxxxxxx>
2011/12/16 Johannes Lerch <lerch@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>:
> Hi,
>
> we (the Code Recommenders project) have multiple dependencies not available
> on orbit yet. Some are newer versions of bundles already on orbit and some
> are completely new. We recently joined the release train and as far as i
> know the implication of being in the release train is that we should move
> all dependencies to orbit. That's okay for us, but i would like to know how
> we should handle that. First step is to get all CQs accepted i think. But
> how to proceed after that? Should someone of our project become an orbit
> committer or should we contribute in any other way?
updating the bundles. You can then be voted on as a committer. Just
reply with the bug numbers and we can start with a vote.
--
Cheers,
Chris Aniszczyk
http://aniszczyk.org
+1 512 961 6719
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
