Interesting, is there any insight on why you decided to go with a closed source platform instead of a FOSS one, like GitLab?
On Fri, Sep 7, 2018 at 12:09 PM Dinesh Prasanth Moluguwan Krishnamoorthy < [email protected]> wrote: > Hello PKI developers, > > First, I would like to thank everyone for your contributions to the PKI > project. As a PKI team, we strive our best to keep the project clean, tidy > and functional. Implementing CI and gerrithub (for code review) were some > of the steps taken to keep the patch submission easy & clean. A bot (hosted > on jenkins) was created to post comments to the patch you submitted on > Gerrithub. > > However, we *decided to decommision Gerrithub and Jenkins as of > 09/21/2018 (Friday) *and move to *Github Pull Requests. * Jenkins will be > shutdown on 09/21/2018 and you'll not be receiving comments (or required > acks) to your submitted patches. > > The primary reasons for the decommission are: > * Easier to track issues and commits since our upstream project is hosted > on Github > * Easier to review changes > * Reliable CI results on single patch with multiple commits > * The extra effort to maintain these infrastructures > > You can read more about gerrit vs github PR here: > http://www.dogtagpki.org/wiki/Gerrit_vs_GitHub_Pull_Request > > It takes a few steps to submit your patch as a PR. The step-by-step > instructions to submit patches via Github Pull Request is available here: > http://www.dogtagpki.org/wiki/GitHub_Pull_Request > > If you have any concerns with this decommission, please feel free to reach > out. > > Regards, > Dinesh > > > _______________________________________________ > Pki-devel mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pki-devel -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 x788 -- This account not approved for unencrypted proprietary information --
_______________________________________________ Pki-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/pki-devel
