From: | Sehrope Sarkuni <sehrope(at)jackdb(dot)com> |
---|---|
To: | List <pgsql-jdbc(at)postgresql(dot)org>, Dave Cramer <davecramer(at)gmail(dot)com> |
Subject: | Re: github purchased by micro$oft |
Date: | 2018-06-24 18:18:50 |
Message-ID: | CAH7T-arz9HSZ0WPH_GzbOeOKK5n6ZqHdTYCV7-QS_D7U4mq=wg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
+1 to not proactively changing anything. I really doubt there will be any
negative issues so barring a compelling feature of a new platform seems
like it'd be a bunch of work for no net gain.
What we should do though is have an alternate official git repo mirroring
the primary pgjdbc repo. Everyone's local copy is essentially a backup as
well but this would cover having a central agreed upon master to use as the
base if we ever lost the primary on GitHub.
Looks like there's already an empty pgjdbc.git on the git.postgresql.org
server (says the owner is Dave too!) so that seems the logical destination
for this. Any chance we can set it up to mirror master from the GitHub
repo? We never rewrite history on master so it could be purely additive
mirror that rejects historical rewrites (i.e. can't be corrupted
externally).
Regards,
-- Sehrope Sarkuni
Founder & CEO | JackDB, Inc. | https://www.jackdb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Pieter Zieschang | 2018-06-28 13:27:25 | insert function runs forever if connection is lost, keeping the table locked |
Previous Message | Vladimir Sitnikov | 2018-06-22 12:46:06 | [pgjdbc/pgjdbc] b7fd9f: fix: support query timeouts exceeding 2147483 seco... |