| From: | Maciek Sakrejda <msakrejda(at)truviso(dot)com> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | Steven Schlansker <stevenschlansker(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Java 1.4 |
| Date: | 2012-01-24 17:53:37 |
| Message-ID: | CAH_hXRbe94g7J3ye0c09+9S9ERUUNm6bLmMSuawzLno0HjQ_Zg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Tue, Jan 24, 2012 at 6:51 AM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
> It occurs to me that if we move to git then we can keep two branches
> active. One branch would support 1.4 for backpatches and the other
> branch would drop 1.4 support and new features would be developed on
> that line.
I assume you mean that 9.2 would have a "split" release (separate 1.4
support) and all the older active release branches would remain with a
single 1.4-compatible version and have backpatches from the new
1.4-compatible branch? That could work, but for what it's worth, I
think the best way to do this would be to drop 1.4 compatibility
entirely in the mainline development branch (e.g., with 9.2 the first
non-1.4-compatible release; I'd love to talk to anyone planning to
talk to 9.2 from Java 1.4), and keep all the existing release branches
compatible until we drop support.
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hillsdale Blvd., Suite 215
Foster City, CA 94404
(650) 242-3500 Main
www.truviso.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2012-01-24 17:54:50 | Re: Java 1.4 |
| Previous Message | Kris Jurka | 2012-01-24 17:52:41 | Re: Java 1.4 |