References: <5947FF8B.9040803@anastigmatix.net> <7a9451ce-eed8-ddec-4fff-add3cfb351f9@matrix.gatewaynet.com> <5949120C.2080705@anastigmatix.net> <5949198B.3080304@anastigmatix.net> From: Achilleas Mantzios Message-ID: <87160f24-02f5-60cd-27df-aca8d3de1be8@matrix.gatewaynet.com> Date: Tue, 20 Jun 2017 16:08:00 +0300 MIME-Version: 1.0 In-Reply-To: <5949198B.3080304@anastigmatix.net> Subject: Re: [Pljava-dev] Draft release notes in preparation for 1.5.1-BETA1 Content-Type: text/plain; charset="us-ascii"; Format="flowed" 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@lists.pgfoundry.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@lists.pgfoundry.org http://lists.pgfoundry.org/mailman/listinfo/pljava-dev