+1 It is clear that maintaining the repository is under the responsibility of the Pulsar PMC and only Pulsar committers are able to commit patches to the repository.
Committers must apply the usual diligence in committing the patches, and enforce the usual rules: at least 2 +1s from committers (or only one +1 if the patch is contributed by a committer) Enrico Il giorno ven 8 nov 2024 alle ore 13:45 Haiting Jiang < jianghait...@apache.org> ha scritto: > +1 > The main difference between this process and the main repo's is that we > don't need the voting procedure in the dev mail list to merge a PR. > It's good for development efficiency and easier for new contributors. > > Thanks, > Haiting > > On 2024/11/07 12:07:03 Jia Zhai wrote: > > +1 > > 👍 It is a good start. > > > > On Wed, Nov 6, 2024 at 10:26 AM lushiji(apache) <lush...@apache.org> > wrote: > > > > > Hello Pulsar Community, > > > The development process of the pulsar-java-contrib project was not > detailed > > > before. I proposed a process to simplify the development process and > > > provide detailed designs and instructions for large proposals to > facilitate > > > better use by users. > > > > > > It can be summarized as follows: > > > 1. for simple changes, you only need to submit a PR for code changes > > > 2. for larger improvement proposal, you need to submit a PR for code > > > changes + a design document (the file is placed in pcip/pcip-xxx.md) > > > > > > The full process can be found at > > > https://github.com/apache/pulsar-java-contrib/pull/10 > > > > > > Please share your thoughts on this proposal along with any concerns or > > > suggestions. > > > > > > Regards > > > > > >
