Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of rednaxelafx@gmail.com
 designates 209.85.216.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=QM/eWJMi+eKxKyPc2NFyxl5ZjztmlgPjshIh1Dyh6XM+BGbpRUAdbtIIdmBDRfCC2F
         lY2WFdMj9vDH0gblSxMoY8fNf7L6h8tvEm0glNfsU3fN+ZpRKmUwpZlRNCM2cSZ+pnCY
         XU9ppP9nNhyVgj+ZeqmLnpb9vBpkHSG01FhnQ=
MIME-Version: 1.0
In-Reply-To: <4CDC28AE.40108@gmail.com>
References: <AANLkTin1WFSAU9N7=wxDui1iMKTV44L2wjVhV8RvxmDJ@mail.gmail.com>
	<4CDB192C.4020605@kippdata.de>
	<AANLkTiks66nw3DpGcjV+yyvHcLGVdEZJjmv0jJGikvtT@mail.gmail.com>
	<4CDC28AE.40108@gmail.com>
Date: Fri, 12 Nov 2010 08:19:20 +0800
Message-ID: <AANLkTiky+RCo_H-=zM7bqiQgS8BhUMZMFZGBC4kzORpv@mail.gmail.com>
Subject: Re: How should older milestones be maintained?
From: Krystal Mok <rednaxelafx@gmail.com>
To: dev@harmony.apache.org
Content-Type: multipart/alternative; boundary=001636284b98ba19ab0494d00aed

--001636284b98ba19ab0494d00aed
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Nov 12, 2010 at 1:32 AM, Tim Ellison <t.p.ellison@gmail.com> wrote:

> On 11/Nov/2010 02:21, Krystal Mok wrote:
> > Thank you very much. I didn't know enough about the layout of Apache
> > projects' archives. Now it's much clearer to me what's the correct way to
> > fixed outdated dependencies.
>
> It is worth mentioning though Kris that not of Harmony's dependencies
> are available from the apache.org site; indeed not all of the
> dependencies are Apache licensed so it is possible that other sites will
> take down some packages that we depended upon in the past.
>
> In general, we don't commit to keeping the old development milestone
> drivers working for any period of time.  If you need to stay on a
> particular version I'd advise taking a local copy of the dependencies.
>
Thank you. Understood. I was kind of hoping to see a mechanism that people
can contribute patches that get sticked side-by-side with the download links
of the older milestone tarballs, or some kind of "Patches page" to so that
others would know: "there's a patch that would make milestone X build on
YYYY-MM-DD". I understand it's not likely to commit back into the code repo
to keep older milestones up-to-date.

Regards,
Kris Mok

--001636284b98ba19ab0494d00aed--