| From: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Move pgAdmin git repo to Github? |
| Date: | 2020-05-21 11:30:29 |
| Message-ID: | CAG7mmoyPQrnFM-_L_aTrrAKbLhUYEn1S=A9X6_w=tHNPrsPDNQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Thu, May 21, 2020 at 4:38 PM Dave Page <dpage(at)pgadmin(dot)org> wrote:
> We see a non-trivial amount of automated build failures caused by git
> timeouts and Varnish cache meditation. This is only likely to get worse as
> we've automated so many different build configurations, and the PostgreSQL
> sysadmin team don't really want to get into the business of large-scale
> repository hosting.
>
> I suggest we move our primary repo to Github. Any objections?
>
No objection in moving the repository on Github.
But - are we changing the patch submission process as well?
Will we allow using PR (Pull Request) for patch submission?
-- Thanks,
Ashesh Vashi
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2020-05-21 11:47:44 | pgAdmin 4 commit: Add information to the Redhat README about signing RP |
| Previous Message | Dave Page | 2020-05-21 11:08:03 | Move pgAdmin git repo to Github? |