Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] 3.6 SR1 build tag

Hi Martin,

your answer does help, but I still have one question: if I just rename the M-tagged RC4 to be R-tagged, won't it break this build? (Because of signing and internal packages and files that should be renamed too?) Or is this 'rename' a new build, but forcing the build ID to be the same as the previous RC?

On Fri, Aug 6, 2010 at 13:43, Oberhuber, Martin <Martin.Oberhuber@xxxxxxxxxxxxx> wrote:
Hi Daniel,
The Platform team has been doing this in the past, for example:
That is, the official build is declared as Release by renaming it.
Does that help?
Martin Oberhuber, Senior Member of Technical Staff, Wind River
direct +43.662.457915.85  fax +43.662.457915.6

From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Daniel Pastore
Sent: Friday, August 06, 2010 4:30 PM
To: Cross project issues
Subject: [cross-project-issues-dev] 3.6 SR1 build tag

Hi all,

Let me use the approaching 3.6 SR1 moment and ask another newbie question:
should my 3.6 SR1 build be tagged M (as I intend it is for a maintenance release) or R (as it is also a formal release)?


Daniel Pastore

cross-project-issues-dev mailing list


Daniel Pastore

Back to the top