From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
---|---|
To: | |
Subject: | Re: [Pljava-dev] Draft release notes in preparation for 1.5.1-BETA1 |
Date: | 2017-06-20 13:08:00 |
Message-ID: | 87160f24-02f5-60cd-27df-aca8d3de1be8@matrix.gatewaynet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pljava-dev |
On 20/06/2017 15:48, Chapman Flack wrote:
> On 06/20/17 08:32, Achilleas Mantzios wrote:
>
>> I thought the general consensus was to git clone the HEAD :
>> https://github.com/tada/pljava.git , at least that's what I gathered from
>> the old pages.
> There /was/ a long period before the release of 1.5.0 where that was
> the only way to get any of the changes made since the release of 1.4.3
> back in 2011.
>
> The current intent is to stick to a more conventional plan with
> named tagged releases. For the last couple months, it has been
> possible for the impatient to build (most of) the upcoming 1.5.1
> by git cloning and checking out REL1_5_STABLE, which is (as the
> name suggests) less adventurous than building whatever's on the
> head of master, but it is still more adventurous than using a release.
Thanx for the update. So what do you recommend for our case? By the time we move to 10 (might be one year from now), just try to re-install the corresponding latest stable version of pl/java?
>
> -Chap
> _______________________________________________
> Pljava-dev mailing list
> Pljava-dev(at)lists(dot)pgfoundry(dot)org
> http://lists.pgfoundry.org/mailman/listinfo/pljava-dev
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
_______________________________________________
Pljava-dev mailing list
Pljava-dev(at)lists(dot)pgfoundry(dot)org
http://lists.pgfoundry.org/mailman/listinfo/pljava-dev
From | Date | Subject | |
---|---|---|---|
Next Message | Chapman Flack | 2017-06-20 13:35:00 | Re: [Pljava-dev] Draft release notes in preparation for 1.5.1-BETA1 |
Previous Message | Chapman Flack | 2017-06-20 12:48:11 | Re: [Pljava-dev] Draft release notes in preparation for 1.5.1-BETA1 |