Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Final Release Build

I think what Ed means is that some projects need to respin their builds (against the same bits) using a different build type (e.g., "R" instead of "I") and those builds need to be published to a different repository location (release repo instead of milestones repo) before the final release. I assume such projects should be considered exceptions so that they are picked up by a final "on demand" aggregation?


On Thu, Jun 10, 2010 at 11:06 AM, David M Williams <david_williams@xxxxxxxxxx> wrote:

Not sure. And, not sure I know what you mean. Normally when I hear "rename" it just involve zip files and directory names. Do you mean the directory part of the URL in the .build file? In the past, people have just corrected those to final location (after the release, normally) and does not require a respin. This is not ideal, obviously, since we are not literally building from the final URL, but, honestly, we always have the risk that the contents of a URL changes and breaks the build, or makes it non-reproducible.

If I've not answered what you need to know, please ask again.


From: Ed Merks <ed.merks@xxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 06/10/2010 10:54 AM
Subject: [cross-project-issues-dev] Final Release Build
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx


Given that we don't have rename support for our Buckminster builds, how
will be spin and contribute our final release build?

cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

Back to the top