|Re: [cross-project-issues-dev] 3.6 SR1 build tag|
Hi Daniel,The Platform team has been doing this in the past, for example:M20100729-1115M-3.6.1RC1-201008061115...M-3.6.1RC4-201009051115R-3.6.1-201009051115That is, the official build is declared as Release by renaming it.Does that help?Thanks,--Martin Oberhuber, Senior Member of Technical Staff, Wind Riverdirect +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 tagHi 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)?
cross-project-issues-dev mailing list
Back to the top