Re: [cross-project-issues-dev] Final Release Build

[Anthony Hunter <anthonyh@xxxxxxxxxx>]

Hi Dave,

Your reply seemed to imply we do not usually do this.

I checked last years CVS and I consistently committed new versions of gmf.build and gef.build the week of the release (GA, SR1, SR2) to change the URL of the final repo from milestones to releases. So I suspect everyone will want to do this.

Cheers...
Anthony
--
Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software Development Manager
IBM Rational Software: Aurora / Modeling Tools
Phone: 613-270-4613


David M Williams ---06/10/2010 12:54:55 PM---Well ... let's see ... does it set office furniture on fire? :) Just kidding.

From:	David M Williams <david_williams@xxxxxxxxxx>
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:	06/10/2010 12:54 PM
Subject:	Re: [cross-project-issues-dev] Final Release Build

---

Well ... let's see ... does it set office furniture on fire? :) Just kidding. 

Yes, if just the URL of the final repo changes, and all feature/bundle versions stay the same, I won't complain. 

If some version number change (even if in qualifier only) I'd appreciate understanding why that was ... since that implies different bits. 

Thanks,

From:	Kenn Hussey <kenn.hussey@xxxxxxxxx>
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:	06/10/2010 12:43 PM
Subject:	Re: [cross-project-issues-dev] Final Release Build
Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx

---

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? 

Kenn

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. 

Thanks,

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

---

David,

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

Regards,
Ed
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev