From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id A7C92E00596 for ; Mon, 9 Apr 2012 10:59:30 -0700 (PDT) Received: from azsmga002.ch.intel.com ([10.2.17.35]) by azsmga101.ch.intel.com with ESMTP; 09 Apr 2012 10:59:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208,217";a="87004498" Received: from azsmsx601.amr.corp.intel.com ([10.2.121.193]) by AZSMGA002.ch.intel.com with ESMTP; 09 Apr 2012 10:59:27 -0700 Received: from fmsmsx104.amr.corp.intel.com (10.19.9.35) by azsmsx601.amr.corp.intel.com (10.2.121.193) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 9 Apr 2012 10:59:27 -0700 Received: from fmsmsx151.amr.corp.intel.com ([169.254.6.66]) by FMSMSX104.amr.corp.intel.com ([169.254.4.88]) with mapi id 14.01.0355.002; Mon, 9 Apr 2012 10:59:26 -0700 From: "Liu, Song" To: "yocto@yoctoproject.org" Thread-Topic: Yocto Project 1.2 M4 schedule Thread-Index: Ac0Wen6qIyP5rFmCS12Eu3ELJVTn9w== Date: Mon, 9 Apr 2012 17:59:26 +0000 Message-ID: <7E680CB2A76BB8438D08CF13C09FC53A46B05304@FMSMSX151.amr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.139] MIME-Version: 1.0 Cc: "Purdie, Richard" Subject: Yocto Project 1.2 M4 schedule X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 17:59:30 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7E680CB2A76BB8438D08CF13C09FC53A46B05304FMSMSX151amrcor_" --_000_7E680CB2A76BB8438D08CF13C09FC53A46B05304FMSMSX151amrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, This is to restate and clarify the schedule for Yocto Project 1.2 M4 (miles= tone 4). If you are concerned or have patches you would like to merge, plea= se see the following dates: 1. RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT 2. RC3 build: April 11th, 2012, PDT 3. RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT 4. RC4 build: April 18th, 2012, PDT 5. YP 1.2 release: April 27th, 2012, PDT You can also check out the schedule here: https://www.google.com/calendar/e= mbed?height=3D600&wkst=3D1&bgcolor=3D%23FFFFFF&src=3Dmg0m150m30gs891eqqhtfu= 5jgg%40group.calendar.google.com&color=3D%238C500B&src=3Dsc7rov4ck552t2f0pa= v120t7r0%40group.calendar.google.com&color=3D%23528800&src=3Dtheyoctoprojec= t%40gmail.com&color=3D%23182C57&ctz=3DAmerica%2FLos_Angeles Please feel free to let me and Beth know if you have any concerns or questi= ons. Thanks! Song PM, Yocto Project --_000_7E680CB2A76BB8438D08CF13C09FC53A46B05304FMSMSX151amrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

 

This is to restate and clarify the schedule for Yoct= o Project 1.2 M4 (milestone 4). If you are concerned or have patches you wo= uld like to merge, please see the following dates:

 

1.     &= nbsp; RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT

2.     &= nbsp; RC3 build: April 11th, 2012, PDT

3.     &= nbsp; RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT

4.     &= nbsp; RC4 build: April 18th, 2012, PDT

5.     &= nbsp; YP 1.2 release: April 27th, 2012, PDT

 

You can also check out the schedule here: https://www.google.com/calendar/embed?height=3D600&wkst=3D1&bgcolor= =3D%23FFFFFF&src=3Dmg0m150m30gs891eqqhtfu5jgg%40group.calendar.google.c= om&color=3D%238C500B&src=3Dsc7rov4ck552t2f0pav120t7r0%40group.calen= dar.google.com&color=3D%23528800&src=3Dtheyoctoproject%40gmail.com&= amp;color=3D%23182C57&ctz=3DAmerica%2FLos_Angeles

 

Please feel free to let me and Beth know if you have= any concerns or questions.

 

Thanks!

Song

PM, Yocto Project

--_000_7E680CB2A76BB8438D08CF13C09FC53A46B05304FMSMSX151amrcor_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga14.intel.com ([143.182.124.37]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SHJ49-0002vp-IQ for openembedded-core@lists.openembedded.org; Mon, 09 Apr 2012 20:11:49 +0200 Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga102.ch.intel.com with ESMTP; 09 Apr 2012 11:01:26 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="128805517" Received: from azsmsx601.amr.corp.intel.com ([10.2.121.193]) by azsmga001.ch.intel.com with ESMTP; 09 Apr 2012 11:01:26 -0700 Received: from fmsmsx104.amr.corp.intel.com (10.19.9.35) by azsmsx601.amr.corp.intel.com (10.2.121.193) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 9 Apr 2012 11:01:25 -0700 Received: from fmsmsx151.amr.corp.intel.com ([169.254.6.66]) by FMSMSX104.amr.corp.intel.com ([169.254.4.88]) with mapi id 14.01.0355.002; Mon, 9 Apr 2012 11:01:17 -0700 From: "Liu, Song" To: Patches and discussions about the oe-core layer Thread-Topic: Yocto Project 1.2 M4 schedule Thread-Index: Ac0Wen6qIyP5rFmCS12Eu3ELJVTn9wAAAwiw Date: Mon, 9 Apr 2012 18:01:16 +0000 Message-ID: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.139] MIME-Version: 1.0 Cc: "Purdie, Richard" , "Stewart, David C" Subject: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 18:11:49 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, This is to restate and clarify the schedule for Yocto Project 1.2 M4 (miles= tone 4). If you are concerned or have patches you would like to merge, plea= se see the following dates: 1. RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT 2. RC3 build: April 11th, 2012, PDT 3. RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT 4. RC4 build: April 18th, 2012, PDT 5. YP 1.2 release: April 27th, 2012, PDT You can also check out the schedule here: https://www.google.com/calendar/e= mbed?height=3D600&wkst=3D1&bgcolor=3D%23FFFFFF&src=3Dmg0m150m30gs891eqqhtfu= 5jgg%40group.calendar.google.com&color=3D%238C500B&src=3Dsc7rov4ck552t2f0pa= v120t7r0%40group.calendar.google.com&color=3D%23528800&src=3Dtheyoctoprojec= t%40gmail.com&color=3D%23182C57&ctz=3DAmerica%2FLos_Angeles=20 Please feel free to let me and Beth know if you have any concerns or questi= ons. Thanks! Song PM, Yocto Project From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wg0-f43.google.com ([74.125.82.43]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SHlDq-00081H-8L for openembedded-core@lists.openembedded.org; Wed, 11 Apr 2012 02:15:42 +0200 Received: by wgbdr12 with SMTP id dr12so263755wgb.24 for ; Tue, 10 Apr 2012 17:06:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Fir2iXhuMNy9vqxxeSRBwEgFOVchtq54lg6//t0NcFY=; b=PlKN7d4Ju2cFvsjNY6T3YRFjp73JdXm2DS/n08IcDEKmGVGmcCdtDSvL2AQvZ0KNO8 apNpprLA3ZhgFj6oq03x1QJLhhbLinxRJiKF9l7Sa0ejOZ+AXBRJ3sT4o78n3F5XWgDa Pr+nvSWTB0boUhXhTBAUEQSgqf/fdMsU+KhNtiphY1KYBqZxIe14uxI3T1UwSlmNBGuk 2ct69gzAvjA1wLhQiKsxMtUwTYKRmskUjnrIbEF+bXuYxuxPMr16WO4O4Ot+0utDwzXr ihz+Zp1U80JbkSD2d8UH48g76jdaqdIfI6fyxMWEULXc6oQ8mtDp+UO7cfb4egnIcQYU rJLw== Received: by 10.216.139.12 with SMTP id b12mr7615909wej.4.1334102784003; Tue, 10 Apr 2012 17:06:24 -0700 (PDT) Received: from [192.168.1.110] (188-223-88-44.zone14.bethere.co.uk. [188.223.88.44]) by mx.google.com with ESMTPS id gg2sm3203049wib.7.2012.04.10.17.06.22 (version=SSLv3 cipher=OTHER); Tue, 10 Apr 2012 17:06:23 -0700 (PDT) Message-ID: <4F84D58F.8020608@gmail.com> Date: Wed, 11 Apr 2012 01:51:27 +0100 From: Julian Pidancet User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20120402 Thunderbird/10.0.3 MIME-Version: 1.0 To: openembedded-core@lists.openembedded.org References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> In-Reply-To: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 00:15:42 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 04/09/12 19:01, Liu, Song wrote: > Hi all, > > This is to restate and clarify the schedule for Yocto Project 1.2 M4 (milestone 4). If you are concerned or have patches you would like to merge, please see the following dates: > > 1. RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT > 2. RC3 build: April 11th, 2012, PDT > 3. RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT > 4. RC4 build: April 18th, 2012, PDT > 5. YP 1.2 release: April 27th, 2012, PDT > > You can also check out the schedule here: https://www.google.com/calendar/embed?height=600&wkst=1&bgcolor=%23FFFFFF&src=mg0m150m30gs891eqqhtfu5jgg%40group.calendar.google.com&color=%238C500B&src=sc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com&color=%23528800&src=theyoctoproject%40gmail.com&color=%23182C57&ctz=America%2FLos_Angeles > > Please feel free to let me and Beth know if you have any concerns or questions. > > Thanks! > Song > PM, Yocto Project Hi, I don't see any commits tagged for these milestones in git.openembedded.org/openembedded-core at the moment. Will there be a release tag or a release branch created on the git repository when YP 1.2 comes out, to indicate people that there's a "stable" version of oe-core they can use ? -- Julian From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIG3v-0001ZQ-6R for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 11:11:31 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q3C928IM020034; Thu, 12 Apr 2012 10:02:08 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 19488-06; Thu, 12 Apr 2012 10:02:04 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q3C920hF020027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Apr 2012 10:02:01 +0100 Message-ID: <1334221321.31685.24.camel@ted> From: Richard Purdie To: Julian Pidancet Date: Thu, 12 Apr 2012 10:02:01 +0100 In-Reply-To: <4F84D58F.8020608@gmail.com> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Cc: openembedded-core@lists.openembedded.org Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 09:11:31 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Wed, 2012-04-11 at 01:51 +0100, Julian Pidancet wrote: > On 04/09/12 19:01, Liu, Song wrote: > > Hi all, > > > > This is to restate and clarify the schedule for Yocto Project 1.2 M4 (milestone 4). If you are concerned or have patches you would like to merge, please see the following dates: > > > > 1. RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT > > 2. RC3 build: April 11th, 2012, PDT > > 3. RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT > > 4. RC4 build: April 18th, 2012, PDT > > 5. YP 1.2 release: April 27th, 2012, PDT > > > > You can also check out the schedule here: https://www.google.com/calendar/embed?height=600&wkst=1&bgcolor=%23FFFFFF&src=mg0m150m30gs891eqqhtfu5jgg%40group.calendar.google.com&color=%238C500B&src=sc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com&color=%23528800&src=theyoctoproject%40gmail.com&color=%23182C57&ctz=America%2FLos_Angeles > > > > Please feel free to let me and Beth know if you have any concerns or questions. > > > > Thanks! > > Song > > PM, Yocto Project > > Hi, > > I don't see any commits tagged for these milestones in > git.openembedded.org/openembedded-core at the moment. Will there be a > release tag or a release branch created on the git repository when YP > 1.2 comes out, to indicate people that there's a "stable" version of > oe-core they can use ? Yes, there will be a branch created on OE-Core. At this point the actual branch naming/tagging is a little in flux. There was some discussion about this at collaboration summit and the BSP summit but there was no conclusion. I've tried to write an email on the subject and it basically goes around in circles. Ideally we need a scheme which can be used in all the layers which doesn't contain numbers as these may conflict with various layer schemes. The poky release names at least do that. Ideally people also want something sortable with more context such as the year. Doing this without numbers is harder. I'm reluctant to change the numbering/branch scheme at this point in a release as its unfair to release engineering and the documentation maintainers. Its a hard problem... Cheers, Richard From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-we0-f175.google.com ([74.125.82.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIGUj-0001th-9q for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 11:39:13 +0200 Received: by wera1 with SMTP id a1so1131268wer.6 for ; Thu, 12 Apr 2012 02:29:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=Rt4jIAeVQdlhxhdXCJyezGcSCft65tv28dOsuBTF8PU=; b=o81qiVUAEK3uBTkujpC1RzkxFujpfWebk6RfgxjTHdKMPBnmaToWV5diF+2yfMNjWS jJqRHQR5ria31rmKi1dSFfPHf8ltHwniNR8vzN3MakvSAkFIwDqf1D4OOR0aFnMg/5ZX XFk6MtOjO++6QE+2NmjxKPdapn6H0atNcAf2Ww97+ckHTjxhZ1pKk8r8UFv9yQqmNwjJ cl5S8IMrqSVqF4zGXx2LtnHkYF5okMXTsHqSF6+ReLN9+JrGbVxipWKzmWOAYr+SA9k+ K6hvC31vAVu4AKMS6dBPsyd57sCtDjO8OH6Lhu7w4GSSzDTZVPQaFrghvG/I2qG429rM or+Q== Received: by 10.180.88.199 with SMTP id bi7mr4147436wib.12.1334222993356; Thu, 12 Apr 2012 02:29:53 -0700 (PDT) Received: from [172.20.1.36] (ip545070eb.adsl-surfen.hetnet.nl. [84.80.112.235]) by mx.google.com with ESMTPS id n8sm19622122wix.10.2012.04.12.02.29.51 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Apr 2012 02:29:52 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1257) From: Koen Kooi In-Reply-To: <1334221321.31685.24.camel@ted> Date: Thu, 12 Apr 2012 11:29:47 +0200 Message-Id: <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> To: Patches and discussions about the oe-core layer X-Mailer: Apple Mail (2.1257) X-Gm-Message-State: ALoCoQnGrQgwHHXJYH8TSYaK7AHH9SkGRihcWvWl8N9PnZ3vxuwdC/j1z8cOIiAh48RcQYgIYpzj Cc: Julian Pidancet Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 09:39:13 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Op 12 apr. 2012, om 11:02 heeft Richard Purdie het volgende geschreven: > On Wed, 2012-04-11 at 01:51 +0100, Julian Pidancet wrote: >> On 04/09/12 19:01, Liu, Song wrote: >>> Hi all, >>>=20 >>> This is to restate and clarify the schedule for Yocto Project 1.2 M4 = (milestone 4). If you are concerned or have patches you would like to = merge, please see the following dates: >>>=20 >>> 1. RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT >>> 2. RC3 build: April 11th, 2012, PDT >>> 3. RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT >>> 4. RC4 build: April 18th, 2012, PDT >>> 5. YP 1.2 release: April 27th, 2012, PDT >>>=20 >>> You can also check out the schedule here: = https://www.google.com/calendar/embed?height=3D600&wkst=3D1&bgcolor=3D%23F= FFFFF&src=3Dmg0m150m30gs891eqqhtfu5jgg%40group.calendar.google.com&color=3D= %238C500B&src=3Dsc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com&col= or=3D%23528800&src=3Dtheyoctoproject%40gmail.com&color=3D%23182C57&ctz=3DA= merica%2FLos_Angeles=20 >>>=20 >>> Please feel free to let me and Beth know if you have any concerns or = questions. >>>=20 >>> Thanks! >>> Song >>> PM, Yocto Project >>=20 >> Hi, >>=20 >> I don't see any commits tagged for these milestones in >> git.openembedded.org/openembedded-core at the moment. Will there be a >> release tag or a release branch created on the git repository when YP >> 1.2 comes out, to indicate people that there's a "stable" version of >> oe-core they can use ? >=20 > Yes, there will be a branch created on OE-Core.=20 >=20 > At this point the actual branch naming/tagging is a little in flux. > There was some discussion about this at collaboration summit and the = BSP > summit but there was no conclusion. >=20 > I've tried to write an email on the subject and it basically goes = around > in circles. Ideally we need a scheme which can be used in all the = layers > which doesn't contain numbers as these may conflict with various layer > schemes. The poky release names at least do that. Ideally people also > want something sortable with more context such as the year. Doing this > without numbers is harder. I'm still a big fan of using 'yoctoproject-1.2' as substring for tags = and branches. The objections I heard to that didn't make sense to me, = but I see this as a purely technical matter where others see it as = something different :) > I'm reluctant to change the numbering/branch scheme at this point in a > release as its unfair to release engineering and the documentation > maintainers. "it's only software" :p regards, Koen= From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-vb0-f47.google.com ([209.85.212.47]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIL6H-0007VA-Vp for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 16:34:18 +0200 Received: by vbbfr13 with SMTP id fr13so1554340vbb.6 for ; Thu, 12 Apr 2012 07:24:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=TQW31kG6Hdt0uvhcS4ESgrOIOJwn0c9vxv0OLnJLn2Q=; b=TEIBKpgYAYUxKwalfqi8e9zWRNUwTygOZ+sqwOZkXU0853hRL74DtnfAa/ZvnBxCbT mGYPbeAdTw/ecVnt4R+Tqxo1G0cjO4hdPPhGJRLA/FpjKemfpd2NTDHHcd5ZECczkMgJ nm7O8ACyPXpBk7TReBosaZiptLSSqCeUSpJcWwZEt4cc1yEJZfVpgN44Mo0gxCDT0jeg wKTKornZSxUHjdJbad8f9MhpA/YqMH36y+ltts9z2Ps2QTnRxZIT1Tc+F8UnWoCdomjn XL8cqpxpe8tG4HvPaLn6nJV2FBmpnBnJQBl5kvzkwqsnXV2iSIHkWcNvMlaOmq5tPLul Akkg== MIME-Version: 1.0 Received: by 10.52.18.212 with SMTP id y20mr1113156vdd.50.1334240697439; Thu, 12 Apr 2012 07:24:57 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.220.2.195 with HTTP; Thu, 12 Apr 2012 07:24:57 -0700 (PDT) In-Reply-To: <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> Date: Thu, 12 Apr 2012 11:24:57 -0300 X-Google-Sender-Auth: 5nxJYMTQIhUrmWWPC_idvJkR-qw Message-ID: From: Otavio Salvador To: Patches and discussions about the oe-core layer Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 14:34:18 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Apr 12, 2012 at 06:29, Koen Kooi wrote= : > I'm still a big fan of using 'yoctoproject-1.2' as substring for tags and= branches. The objections I heard to that didn't make sense to me, but I se= e this as a purely technical matter where others see it as something differ= ent :) OE-Core branch could be 2012-1. --=20 Otavio Salvador=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0O= .S. Systems E-mail: otavio@ossystems.com.br=A0 http://www.ossystems.com.br Mobile: +55 53 9981-7854=A0 =A0 =A0 =A0=A0 =A0 =A0 =A0http://projetos.ossys= tems.com.br From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-we0-f175.google.com ([74.125.82.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SILKn-0007kH-Uf for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 16:49:18 +0200 Received: by wera1 with SMTP id a1so1316329wer.6 for ; Thu, 12 Apr 2012 07:39:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=pQd6Kz29zVsBY97yGrZDyZg5HEGEg9otOJqE5h3mHjk=; b=o0IeFzj3pKZG0v3gpJZT9lv3tkj14LsJoQApOPQskE8v/gu0fou9dEYXUgfufT+Ptl 75ZCU74isAMFaN3KjfwgDLG2W3haAIkO15u/qmYuUL3HEu/0UF0Hd1czpU7v2NOdv0rP /UsXMUSjx4di8GNepbzESA6OajOlXeznGKcdd6CJx5IoAbroxGWJJGuxtJwOQRBg8xhA 5L5bxzfmfcQjKTB+KvshUahCdg9fO6zI6kB5JnMgtOdIU5/17W9NiMDgehw/Czl8csvs efZczM7W5exL5l3i4I0ZoENGtuEe6PrWwhpsCcqSrc+QGzY8Q51khF2E9TER7oIdkElF d8fQ== Received: by 10.216.132.40 with SMTP id n40mr1654571wei.68.1334241596657; Thu, 12 Apr 2012 07:39:56 -0700 (PDT) Received: from [172.20.1.36] (ip545070eb.adsl-surfen.hetnet.nl. [84.80.112.235]) by mx.google.com with ESMTPS id n8sm22212993wix.10.2012.04.12.07.39.55 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Apr 2012 07:39:55 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1257) From: Koen Kooi In-Reply-To: Date: Thu, 12 Apr 2012 16:39:52 +0200 Message-Id: References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> To: Patches and discussions about the oe-core layer X-Mailer: Apple Mail (2.1257) X-Gm-Message-State: ALoCoQmAQh+4AZNGdRkQn7zF+3j6Cvaz8YULLcsIAD9SzCEHN6nTtEIf/HE4C+YHpOacEk7H1JRY Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 14:49:18 -0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Op 12 apr. 2012, om 16:24 heeft Otavio Salvador het volgende geschreven: > On Thu, Apr 12, 2012 at 06:29, Koen Kooi = wrote: >> I'm still a big fan of using 'yoctoproject-1.2' as substring for tags = and branches. The objections I heard to that didn't make sense to me, = but I see this as a purely technical matter where others see it as = something different :) >=20 > OE-Core branch could be 2012-1. Yes, but experience has shown that PHBs and new yocto users want to see = 'yocto' in the name and go apeshit when it's missing. OTOH people will = hate whatever gets chosen, so let's get this over with and pick a name = and strongly recommend other layers to adopt it as well.=20 We can't do worse than fedora: = http://lists.fedoraproject.org/pipermail/announce/2012-February/003044.htm= l= From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp2-g21.free.fr ([212.27.42.2]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SILWU-0008J0-3L for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 17:01:22 +0200 Received: from eb-e6520 (unknown [82.240.38.71]) by smtp2-g21.free.fr (Postfix) with ESMTP id EDF0F4B013B for ; Thu, 12 Apr 2012 16:51:59 +0200 (CEST) Date: Thu, 12 Apr 2012 16:51:58 +0200 From: Eric =?ISO-8859-1?B?QuluYXJk?= To: openembedded-core@lists.openembedded.org Message-ID: <20120412165158.52c84ded@eb-e6520> In-Reply-To: References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> Organization: =?ISO-8859-1?B?RXVrculh?= Electromatique X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.8; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 15:01:22 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Le Thu, 12 Apr 2012 16:39:52 +0200, Koen Kooi a =E9crit : >=20 > Op 12 apr. 2012, om 16:24 heeft Otavio Salvador het volgende geschreven: >=20 > > On Thu, Apr 12, 2012 at 06:29, Koen Kooi w= rote: > >> I'm still a big fan of using 'yoctoproject-1.2' as substring for tags = and branches. The objections I heard to that didn't make sense to me, but I= see this as a purely technical matter where others see it as something dif= ferent :) > >=20 > > OE-Core branch could be 2012-1. >=20 > Yes, but experience has shown that PHBs and new yocto users want to see '= yocto' in the name and go apeshit when it's missing. OTOH people will hate = whatever gets chosen, so let's get this over with and pick a name and stron= gly recommend other layers to adopt it as well.=20 >=20 FWIW I'm also in favor of a tag yocto-1.2 for the OE-core release which yocto 1.2 is based on. Eric From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from tx2ehsobe005.messaging.microsoft.com ([65.55.88.15] helo=tx2outboundpool.messaging.microsoft.com) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIMMT-0000gN-LV for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 17:55:05 +0200 Received: from mail22-tx2-R.bigfish.com (10.9.14.253) by TX2EHSOBE007.bigfish.com (10.9.40.27) with Microsoft SMTP Server id 14.1.225.23; Thu, 12 Apr 2012 15:45:44 +0000 Received: from mail22-tx2 (localhost [127.0.0.1]) by mail22-tx2-R.bigfish.com (Postfix) with ESMTP id D13D730016E for ; Thu, 12 Apr 2012 15:45:44 +0000 (UTC) X-SpamScore: -9 X-BigFish: VS-9(zz9371Ic89bh1432N98dKzz1202hzz8275ch8275bhz2dh2a8h668h839h8e2h8e3hbe9i) X-Forefront-Antispam-Report: CIP:70.37.183.190; KIP:(null); UIP:(null); IPV:NLI; H:mail.freescale.net; RD:none; EFVD:NLI Received: from mail22-tx2 (localhost.localdomain [127.0.0.1]) by mail22-tx2 (MessageSwitch) id 1334245543691891_27071; Thu, 12 Apr 2012 15:45:43 +0000 (UTC) Received: from TX2EHSMHS015.bigfish.com (unknown [10.9.14.251]) by mail22-tx2.bigfish.com (Postfix) with ESMTP id A4284420084 for ; Thu, 12 Apr 2012 15:45:43 +0000 (UTC) Received: from mail.freescale.net (70.37.183.190) by TX2EHSMHS015.bigfish.com (10.9.99.115) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 12 Apr 2012 15:45:42 +0000 Received: from 039-SN1MPN1-001.039d.mgd.msft.net ([169.254.1.132]) by 039-SN1MMR1-003.039d.mgd.msft.net ([10.84.1.16]) with mapi id 14.01.0355.003; Thu, 12 Apr 2012 10:45:42 -0500 From: McClintock Matthew-B29882 To: Patches and discussions about the oe-core layer Thread-Topic: [OE-core] Yocto Project 1.2 M4 schedule Thread-Index: AQHNGMNQhZ+TZMKgekW4ywXi0lVeyg== Date: Thu, 12 Apr 2012 15:45:41 +0000 Message-ID: References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> <20120412165158.52c84ded@eb-e6520> In-Reply-To: <20120412165158.52c84ded@eb-e6520> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [99.47.177.27] MIME-Version: 1.0 X-OriginatorOrg: freescale.com Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: McClintock Matthew-B29882 , Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 15:55:06 -0000 Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-ID: <85B02EE37112DF4CB6AFCBE44F755369@mgd.freescale.com> Content-Transfer-Encoding: quoted-printable On Thu, Apr 12, 2012 at 9:51 AM, Eric B=E9nard wrote: > Le Thu, 12 Apr 2012 16:39:52 +0200, > Koen Kooi a =E9crit : > >> >> Op 12 apr. 2012, om 16:24 heeft Otavio Salvador het volgende geschreven: >> >> > On Thu, Apr 12, 2012 at 06:29, Koen Kooi = wrote: >> >> I'm still a big fan of using 'yoctoproject-1.2' as substring for tags= and branches. The objections I heard to that didn't make sense to me, but = I see this as a purely technical matter where others see it as something di= fferent :) >> > >> > OE-Core branch could be 2012-1. >> >> Yes, but experience has shown that PHBs and new yocto users want to see = 'yocto' in the name and go apeshit when it's missing. OTOH people will hate= whatever gets chosen, so let's get this over with and pick a name and stro= ngly recommend other layers to adopt it as well. >> > FWIW I'm also in favor of a tag yocto-1.2 for the OE-core release which > yocto 1.2 is based on. This is one of those things were someone just needs to decide or a group of people need to vote. It's not worth debating anymore - you can't make everyone happy. As long as it's tagged though. -M= From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-lb0-f175.google.com ([209.85.217.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SINSq-0002ZQ-4q for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 19:05:44 +0200 Received: by lbky2 with SMTP id y2so1649224lbk.6 for ; Thu, 12 Apr 2012 09:56:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=PbR7KiU2ykmg4chu2MdzS9ohKNFEBrpTJRwNb9QcEio=; b=gYTYHPqgWRqleH2b7vrjl7AyLZWHDVABw7k0xl/yytUP+0AfXWRI9jVr0rK/UPu8gh aQRSauX1LxzMXuTVpGC8Wi6LaXFEUtPZ9teiNiCNiEYnIPS4oMW/AuLnupRnYqMz6Y2N oDKzWtTBx4Ks/Z/OD4SSzovRthwrL4Go81QGGRGb00oxMv8KrK0OoQS/5VV95qvM0n6C Cfuyq62YtnhwJ9C/j4wQ2Ifa1Yc14QPDF9B0olah18Td3jPFXko7btHz74hQV3co3/+N GTh6YhTDnTFS+UHoJSYaPYlYm6haVRkX/6nfxA5M+ZiqQGiS/UyfMiJ65iNfKuuXxfKH WM+w== Received: by 10.152.113.229 with SMTP id jb5mr2787273lab.45.1334249783620; Thu, 12 Apr 2012 09:56:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.129.134 with HTTP; Thu, 12 Apr 2012 09:55:53 -0700 (PDT) In-Reply-To: <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> From: Khem Raj Date: Thu, 12 Apr 2012 09:55:53 -0700 Message-ID: To: Patches and discussions about the oe-core layer Cc: Julian Pidancet Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 17:05:44 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Apr 12, 2012 at 2:29 AM, Koen Kooi wro= te: > > Op 12 apr. 2012, om 11:02 heeft Richard Purdie het volgende geschreven: > >> On Wed, 2012-04-11 at 01:51 +0100, Julian Pidancet wrote: >>> On 04/09/12 19:01, Liu, Song wrote: >>>> Hi all, >>>> >>>> This is to restate and clarify the schedule for Yocto Project 1.2 M4 (= milestone 4). If you are concerned or have patches you would like to merge,= please see the following dates: >>>> >>>> 1. RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT >>>> 2. RC3 build: April 11th, 2012, PDT >>>> 3. RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT >>>> 4. RC4 build: April 18th, 2012, PDT >>>> 5. YP 1.2 release: April 27th, 2012, PDT >>>> >>>> You can also check out the schedule here: https://www.google.com/calen= dar/embed?height=3D600&wkst=3D1&bgcolor=3D%23FFFFFF&src=3Dmg0m150m30gs891eq= qhtfu5jgg%40group.calendar.google.com&color=3D%238C500B&src=3Dsc7rov4ck552t= 2f0pav120t7r0%40group.calendar.google.com&color=3D%23528800&src=3Dtheyoctop= roject%40gmail.com&color=3D%23182C57&ctz=3DAmerica%2FLos_Angeles >>>> >>>> Please feel free to let me and Beth know if you have any concerns or q= uestions. >>>> >>>> Thanks! >>>> Song >>>> PM, Yocto Project >>> >>> Hi, >>> >>> I don't see any commits tagged for these milestones in >>> git.openembedded.org/openembedded-core at the moment. Will there be a >>> release tag or a release branch created on the git repository when YP >>> 1.2 comes out, to indicate people that there's a "stable" version of >>> oe-core they can use ? >> >> Yes, there will be a branch created on OE-Core. >> >> At this point the actual branch naming/tagging is a little in flux. >> There was some discussion about this at collaboration summit and the BSP >> summit but there was no conclusion. >> >> I've tried to write an email on the subject and it basically goes around >> in circles. Ideally we need a scheme which can be used in all the layers >> which doesn't contain numbers as these may conflict with various layer >> schemes. The poky release names at least do that. Ideally people also >> want something sortable with more context such as the year. Doing this >> without numbers is harder. > > I'm still a big fan of using 'yoctoproject-1.2' as substring for tags and= branches. The objections I heard to that didn't make sense to me, but I se= e this as a purely technical matter where others see it as something differ= ent :) > I think that string is fine as long as its just for yocto but I think for OE-Core we are going to do a General release so tagging that with something yocto project will be very confusing unless we plan to do different releases of OE-Core for general availability and yocto project. I dont think we have bandwidth for that. And since poky repository makes a copy of OE-Core metadata it can be tagged in yoctoproject specific tags since OE-Core is at center of all layers I would propose that other layers when tagged contain OE-Core's release tag in their own tags name so something like - >> I'm reluctant to change the numbering/branch scheme at this point in a >> release as its unfair to release engineering and the documentation >> maintainers. Lets keep it as we have it. Its quite generic. > > > "it's only software" :p > > regards, > > Koen > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-vb0-f47.google.com ([209.85.212.47]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SINia-00030g-G4 for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 19:22:00 +0200 Received: by vbbfr13 with SMTP id fr13so1705739vbb.6 for ; Thu, 12 Apr 2012 10:12:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=NjFC85MNiHmIQZSb/5GnnAmmeEmUVvrOkawKmWGCaNk=; b=UbC9oXYjYT0p1vZ2VrNxLB4ypltb4HEkbRuXUcjE1s8Suk8oJhT05KaHLBR1V4sjtj gslHKsKMG3IVKrcaUN2mcl4+aZkv0vRqy+phScWjdmkexHmYUhbv7OU5CPyd2CKcZYXi Hn4SwzvngkL+qmkq9E6ekCbMdbVjrlS+BNADMNfXLe04QKIDldzF9Ovm0WNWX7z0aG2F K71Y+QJH6ufO4MKCjzrZW24XMFk2MLalzXTSflsvtFDCB+HVOyadIa9twPs6uemhmLtE w/Q6KUJlphVy1zcD6BXNI81xH4+i2dykjdizbL+J6Lb8pdavBJ5RmgAs7fqd2NsmIQis Ctzw== MIME-Version: 1.0 Received: by 10.52.31.42 with SMTP id x10mr1353641vdh.33.1334250759725; Thu, 12 Apr 2012 10:12:39 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.220.2.195 with HTTP; Thu, 12 Apr 2012 10:12:39 -0700 (PDT) In-Reply-To: References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> Date: Thu, 12 Apr 2012 14:12:39 -0300 X-Google-Sender-Auth: QrBrdqxzM9XqReHEr19nQk0H_FA Message-ID: From: Otavio Salvador To: Patches and discussions about the oe-core layer Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 17:22:00 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Apr 12, 2012 at 13:55, Khem Raj wrote: >> I'm still a big fan of using 'yoctoproject-1.2' as substring for tags an= d branches. The objections I heard to that didn't make sense to me, but I s= ee this as a purely technical matter where others see it as something diffe= rent :) > > I think that string is fine as long as its just for yocto but I think > for OE-Core we are going to do a General release > so tagging that with something yocto project will be very confusing > unless we plan to do different releases of OE-Core for general > availability > and yocto project. I dont think we have bandwidth for that. And since > poky repository makes a copy of OE-Core metadata it can be tagged in > yoctoproject specific tags > > since OE-Core is at center of all layers I would propose that other > layers when tagged contain OE-Core's release tag in their own tags > name > > so something like - I agree; yocto tag ought to be check in yocto git repository. What we need is to have an OE-Core release at same time. --=20 Otavio Salvador=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0O= .S. Systems E-mail: otavio@ossystems.com.br=A0 http://www.ossystems.com.br Mobile: +55 53 9981-7854=A0 =A0 =A0 =A0=A0 =A0 =A0 =A0http://projetos.ossys= tems.com.br From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-we0-f175.google.com ([74.125.82.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SINsI-0003Ho-OT for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 19:32:02 +0200 Received: by wera1 with SMTP id a1so1429768wer.6 for ; Thu, 12 Apr 2012 10:22:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=oLtngHjo1XbVeJzJRdBc4Q6aQDyGcki1+6NFtpzGSfA=; b=BUhzkiZ+U5Z5qvkb+AcIQSCKyD8FxkfDdI+otRPptUreXjr4EoIcpzaf/9TnzXr54/ doFg7s6+RQi6CkTisb1nc1EFz1kO/9Zo3ssC0hcUuxXWYkkY2cl6/ZYkzwqMZ4YckJHr BSysg6mj/bbLyYv862y2dFQtlWvfah9ouGM5NH+P9avIX6YxuZzCc8ro688wFyVaHOLM bZ+ob34ZwZ0/gfNXsdrIhzb/V/vRxrGvkysKgpd3llqZ04b6IpF49Ho8+wmGEXZCNr4m Hr3ZeZ0Xn/mnBualUseWBvHT+PPQIannjnbnCE3A5FIIZytQ7rmUO7YYpAoBfURtn3k1 Fs6Q== Received: by 10.180.95.197 with SMTP id dm5mr17570985wib.20.1334251362035; Thu, 12 Apr 2012 10:22:42 -0700 (PDT) Received: from [172.20.1.36] (ip545070eb.adsl-surfen.hetnet.nl. [84.80.112.235]) by mx.google.com with ESMTPS id ff9sm53596129wib.2.2012.04.12.10.22.40 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Apr 2012 10:22:40 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1257) From: Koen Kooi In-Reply-To: Date: Thu, 12 Apr 2012 19:22:36 +0200 Message-Id: References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> To: Patches and discussions about the oe-core layer X-Mailer: Apple Mail (2.1257) X-Gm-Message-State: ALoCoQlzWTyBzPaTHrzhlbAOlPvoeVmyIJ5VozmMmor1zYo/4gdgChmWFzbAWocLrDi/mUaUG62Z Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 17:32:02 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Op 12 apr. 2012, om 18:55 heeft Khem Raj het volgende geschreven: > On Thu, Apr 12, 2012 at 2:29 AM, Koen Kooi = wrote: >>=20 >> Op 12 apr. 2012, om 11:02 heeft Richard Purdie het volgende = geschreven: >>=20 >>> On Wed, 2012-04-11 at 01:51 +0100, Julian Pidancet wrote: >>>> On 04/09/12 19:01, Liu, Song wrote: >>>>> Hi all, >>>>>=20 >>>>> This is to restate and clarify the schedule for Yocto Project 1.2 = M4 (milestone 4). If you are concerned or have patches you would like to = merge, please see the following dates: >>>>>=20 >>>>> 1. RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT >>>>> 2. RC3 build: April 11th, 2012, PDT >>>>> 3. RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT >>>>> 4. RC4 build: April 18th, 2012, PDT >>>>> 5. YP 1.2 release: April 27th, 2012, PDT >>>>>=20 >>>>> You can also check out the schedule here: = https://www.google.com/calendar/embed?height=3D600&wkst=3D1&bgcolor=3D%23F= FFFFF&src=3Dmg0m150m30gs891eqqhtfu5jgg%40group.calendar.google.com&color=3D= %238C500B&src=3Dsc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com&col= or=3D%23528800&src=3Dtheyoctoproject%40gmail.com&color=3D%23182C57&ctz=3DA= merica%2FLos_Angeles >>>>>=20 >>>>> Please feel free to let me and Beth know if you have any concerns = or questions. >>>>>=20 >>>>> Thanks! >>>>> Song >>>>> PM, Yocto Project >>>>=20 >>>> Hi, >>>>=20 >>>> I don't see any commits tagged for these milestones in >>>> git.openembedded.org/openembedded-core at the moment. Will there be = a >>>> release tag or a release branch created on the git repository when = YP >>>> 1.2 comes out, to indicate people that there's a "stable" version = of >>>> oe-core they can use ? >>>=20 >>> Yes, there will be a branch created on OE-Core. >>>=20 >>> At this point the actual branch naming/tagging is a little in flux. >>> There was some discussion about this at collaboration summit and the = BSP >>> summit but there was no conclusion. >>>=20 >>> I've tried to write an email on the subject and it basically goes = around >>> in circles. Ideally we need a scheme which can be used in all the = layers >>> which doesn't contain numbers as these may conflict with various = layer >>> schemes. The poky release names at least do that. Ideally people = also >>> want something sortable with more context such as the year. Doing = this >>> without numbers is harder. >>=20 >> I'm still a big fan of using 'yoctoproject-1.2' as substring for tags = and branches. The objections I heard to that didn't make sense to me, = but I see this as a purely technical matter where others see it as = something different :) >>=20 >=20 > I think that string is fine as long as its just for yocto but I think > for OE-Core we are going to do a General release > so tagging that with something yocto project will be very confusing > unless we plan to do different releases of OE-Core for general > availability > and yocto project. I dont think we have bandwidth for that. And since > poky repository makes a copy of OE-Core metadata it can be tagged in > yoctoproject specific tags >=20 > since OE-Core is at center of all layers I would propose that other > layers when tagged contain OE-Core's release tag in their own tags > name >=20 > so something like - You just volunteered to handle all the "Does it work with yocto 1.2?" = questions :)=20 Simply put: people are stupid, they need explicit PHB compliant names in = tags, even if it isn't 100% politically correct to say "yocto" when we = actually mean "oe-core". Unless the yocto 1.2 release note state that it's based on oe-core "foo" = and all layers compatible with "foo" use "foo" in tags/branches.= From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-vx0-f175.google.com ([209.85.220.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIO1J-0003Oc-KV for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 19:41:21 +0200 Received: by vcbfl13 with SMTP id fl13so1753375vcb.6 for ; Thu, 12 Apr 2012 10:32:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=9mau+NeLhTXREmNBhfj4o+WcwyIvcrPvNs8UPjCPJqQ=; b=CAofIxJPm7aqS8tBjzJrxEUsDTSL/C4mPZQFmmZca6wCwdLpL/0WqJ2dHU0S7vfe4u +gGZ+qhziSAqa3ZJPPf2r29XuDKv60IQ0CMK1xMymL0zNFtpulipZhbJkm6a9UhZnrnB qpGxlXWzt4NTd6/zMwqTZ6A8O8FPXjUz25s8idtskVIsP6zH0ohIcEupnGGFTJ6ccyzc GxnDf/bNdf1KiZdoPPKBwaLIB6vAnJi8kr+wjdxkDXnue8sptecJG7h4oAoehqa2Cz+E ArpN62rIocCClA8SeU9PQtORSSlm/aziE6OAAT+QULvdtt9kvnohEUPIyJ/bKVBRD3aV N8kQ== MIME-Version: 1.0 Received: by 10.220.156.72 with SMTP id v8mr1711927vcw.45.1334251920924; Thu, 12 Apr 2012 10:32:00 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.220.2.195 with HTTP; Thu, 12 Apr 2012 10:32:00 -0700 (PDT) In-Reply-To: References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> Date: Thu, 12 Apr 2012 14:32:00 -0300 X-Google-Sender-Auth: CmAuzG4pTwYmqj1F_auaY7MIX08 Message-ID: From: Otavio Salvador To: Patches and discussions about the oe-core layer Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 17:41:21 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Apr 12, 2012 at 14:22, Koen Kooi wrote= : > You just volunteered to handle all the "Does it work with yocto 1.2?" que= stions :) > > Simply put: people are stupid, they need explicit PHB compliant names in = tags, even if it isn't 100% politically correct to say "yocto" when we actu= ally mean "oe-core". > > Unless the yocto 1.2 release note state that it's based on oe-core "foo" = and all layers compatible with "foo" use "foo" in tags/branches. I think layers ought to have tags for both ... -oe-core- -yocto- --=20 Otavio Salvador=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0O= .S. Systems E-mail: otavio@ossystems.com.br=A0 http://www.ossystems.com.br Mobile: +55 53 9981-7854=A0 =A0 =A0 =A0=A0 =A0 =A0 =A0http://projetos.ossys= tems.com.br From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vms173011pub.verizon.net ([206.46.173.11]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIOuI-0005ZZ-Jm for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 20:38:10 +0200 Received: from gandalf.denix.org ([unknown] [71.178.225.66]) by vms173011.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0M2D00FI8PZPD331@vms173011.mailsrvcs.net> for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 13:28:37 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id 579B720099; Thu, 12 Apr 2012 14:28:37 -0400 (EDT) Date: Thu, 12 Apr 2012 14:28:37 -0400 From: Denys Dmytriyenko To: Patches and discussions about the oe-core layer Message-id: <20120412182837.GC13291@denix.org> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> MIME-version: 1.0 In-reply-to: User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 18:38:11 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Thu, Apr 12, 2012 at 04:39:52PM +0200, Koen Kooi wrote: > > We can't do worse than fedora: > http://lists.fedoraproject.org/pipermail/announce/2012-February/003044.html Are you suggesting we adopt a new "Unhealthy snacks" or "Junk food" versioning schema? :) -- Denys From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIP5X-0005hi-F0 for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 20:49:47 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q3CIeSat026599 for ; Thu, 12 Apr 2012 19:40:28 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 26043-02 for ; Thu, 12 Apr 2012 19:40:24 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q3CIeK4W026593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 12 Apr 2012 19:40:22 +0100 Message-ID: <1334256020.7309.45.camel@ted> From: Richard Purdie To: Patches and discussions about the oe-core layer Date: Thu, 12 Apr 2012 19:40:20 +0100 In-Reply-To: References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 18:49:47 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2012-04-12 at 14:32 -0300, Otavio Salvador wrote: > On Thu, Apr 12, 2012 at 14:22, Koen Kooi wrote: > > You just volunteered to handle all the "Does it work with yocto 1.2?" questions :) > > > > Simply put: people are stupid, they need explicit PHB compliant names in tags, even if it isn't 100% politically correct to say "yocto" when we actually mean "oe-core". > > > > Unless the yocto 1.2 release note state that it's based on oe-core "foo" and all layers compatible with "foo" use "foo" in tags/branches. > > I think layers ought to have tags for both ... > > -oe-core- > -yocto- This would be rather sad if it were necessary. The whole point is we're trying to build things which are compatible with each other. If that turns out not to be the case I want to fix it, not encourage it. Cheers, Richard From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-vb0-f47.google.com ([209.85.212.47]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIPiQ-0008Pa-Kc for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 21:29:58 +0200 Received: by vbbfr13 with SMTP id fr13so1809566vbb.6 for ; Thu, 12 Apr 2012 12:20:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=V3Cf2VCsVKNJKguO6ZnSYM/yWptnBA8wEATpc1AU6vA=; b=xqIP9f6bEw8VJcx6YIO/RoxTeYRloi+sl/F/PVzE+VsEtQNsUiuNP6AwAM0uoJ9c7E 7KonOrMFzXwDxvzTaIAYOBjezBooOfr3o3oosxlL6P930P2QNeLdGgTiV9IukGRWlWNU qlEBXeBX/yunjPdrgZLQXOFcuYSJ2i+hNiHrpGhfDgHF7m+i9mvD3ySY5tHEak4OqiHs F9di7kM0hH/5q59Y+GDoNUm5zVK36uyKrSxJk4gJHGMwi7OSwOWO8AHPsh+ebk5fqKx3 0t8JWvNHdm1AzFkNFpyYj9pTW+m/3lFq22jgGI2PJciFfZyjYemTEgIvzAwnVQzVN2aV nSBg== MIME-Version: 1.0 Received: by 10.220.228.200 with SMTP id jf8mr1923956vcb.0.1334258437802; Thu, 12 Apr 2012 12:20:37 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.220.2.195 with HTTP; Thu, 12 Apr 2012 12:20:37 -0700 (PDT) In-Reply-To: <1334256020.7309.45.camel@ted> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> <1334256020.7309.45.camel@ted> Date: Thu, 12 Apr 2012 16:20:37 -0300 X-Google-Sender-Auth: T9VZp1Y6l12R35QLbfuOdFgmC3M Message-ID: From: Otavio Salvador To: Patches and discussions about the oe-core layer Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 19:29:58 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Apr 12, 2012 at 15:40, Richard Purdie wrote: >> I think layers ought to have tags for both ... >> >> -oe-core- >> -yocto- > > This would be rather sad if it were necessary. The whole point is we're > trying to build things which are compatible with each other. If that > turns out not to be the case I want to fix it, not encourage it. They will be compatible but users wouldn't be asking: Does layer X works with OE-Core Y and Yocto W? --=20 Otavio Salvador=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0O= .S. Systems E-mail: otavio@ossystems.com.br=A0 http://www.ossystems.com.br Mobile: +55 53 9981-7854=A0 =A0 =A0 =A0=A0 =A0 =A0 =A0http://projetos.ossys= tems.com.br From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ob0-f175.google.com ([209.85.214.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIPt0-00005J-6M for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 21:40:55 +0200 Received: by obbuo13 with SMTP id uo13so3337831obb.6 for ; Thu, 12 Apr 2012 12:31:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=AUrtV2yxCSamqBqMrlskdPZn50SP1N2eKFYBq7Bgbnk=; b=TWkgeUqR6+Eri6SuSsLe2oulnb4j1Z/dYrXdVc5yPH9aQ5cxlTxgzY4LX0rUhhTJyA 1tMYJBA6gF3+m5xebjrGlO7wEGYsF7kGF8ra9Hbf3bMWndOlSWfJBmUxXtMaqdNwCwEU qrwz3DQvdSPicCadfWwuyQ9X62wTpG+NwG3QhOQHkqkPk1Q0VUCwp4gT46qSqDc688Wq r2PGL0U077cranGAU0UTKtGWlrHttL4YBgAEuGrM+zLLrKyGuAX8EIS2FxczsN66Lc8n fTOM9j/mXESSIBCIxOcQb7MGctgtgCQChzpmPFQVbQM0A/2Yrm5pYhHNXmlefZzdNu+L D8/Q== Received: by 10.182.127.20 with SMTP id nc20mr4562276obb.66.1334259093268; Thu, 12 Apr 2012 12:31:33 -0700 (PDT) MIME-Version: 1.0 Sender: swaplinker@gmail.com Received: by 10.60.168.172 with HTTP; Thu, 12 Apr 2012 12:31:13 -0700 (PDT) In-Reply-To: References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> From: Julian Pidancet Date: Thu, 12 Apr 2012 20:31:13 +0100 X-Google-Sender-Auth: bfBCy_6JEL9EG2MwKNvSjVFoKRQ Message-ID: To: Khem Raj Cc: Patches and discussions about the oe-core layer Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 19:40:55 -0000 Content-Type: text/plain; charset=UTF-8 On Thu, Apr 12, 2012 at 5:55 PM, Khem Raj wrote: > > I think that string is fine as long as its just for yocto but I think > for OE-Core we are going to do a General release > so tagging that with something yocto project will be very confusing > unless we plan to do different releases of OE-Core for general > availability > and yocto project. I dont think we have bandwidth for that. And since > poky repository makes a copy of OE-Core metadata it can be tagged in > yoctoproject specific tags > In case there is an oe-core general availability release separated from the yocto release, when would that happen ? Is there anything planned yet ? -- Julian From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vms173003pub.verizon.net ([206.46.173.3]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIPu3-00008C-3X for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 21:41:59 +0200 Received: from gandalf.denix.org ([unknown] [71.178.225.66]) by vms173003.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0M2D0006ZQ4ZF480@vms173003.mailsrvcs.net> for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 13:31:50 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id BC32C20099; Thu, 12 Apr 2012 14:31:47 -0400 (EDT) Date: Thu, 12 Apr 2012 14:31:47 -0400 From: Denys Dmytriyenko To: Patches and discussions about the oe-core layer Message-id: <20120412183147.GD13291@denix.org> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> MIME-version: 1.0 In-reply-to: User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 19:41:59 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Thu, Apr 12, 2012 at 02:32:00PM -0300, Otavio Salvador wrote: > On Thu, Apr 12, 2012 at 14:22, Koen Kooi wrote: > > You just volunteered to handle all the "Does it work with yocto 1.2?" questions :) > > > > Simply put: people are stupid, they need explicit PHB compliant names in tags, even if it isn't 100% politically correct to say "yocto" when we actually mean "oe-core". > > > > Unless the yocto 1.2 release note state that it's based on oe-core "foo" and all layers compatible with "foo" use "foo" in tags/branches. > > I think layers ought to have tags for both ... > > -oe-core- > -yocto- And -poky- for completeness? Seriously, "yocto"-naming schema is not that bad. For shortness, it can be "yp-1.2" as a suffix to the layer-specific tags... But I'm flexible with other naming schemas, such as "YYYY.MM" or "YYYY.#" -- Denys From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga05.intel.com ([192.55.52.89] helo=fmsmga101.fm.intel.com) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIQ20-0000EP-AA for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 21:50:12 +0200 Received: from mail-lpp01m010-f52.google.com ([209.85.215.52]) by mga01.intel.com with ESMTP/TLS/RC4-SHA; 12 Apr 2012 12:39:38 -0700 Received: by lahi5 with SMTP id i5so1645459lah.25 for ; Thu, 12 Apr 2012 12:39:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=tB2FPz+iQf7ctQWZHmYV+Uh+FC3fzeQjLw9iWQ6Tw+0=; b=I70s1UmRwUaxYdgYQmCNvyMZzDydFCr3j3+8z2VbUh29S/kXMWSix48+SU7+WbiIHU jTBncC0K7pF6Kx9CXwD+XhVtdZmnV6FDfYjBKaYxDM78rXCxbqdrmG+gSnI+RcFnZuuT iad3/lG4R1UWrcz1Wm5RH9wQzoctg2d3YGSImFI/gAG6Vmqz4SCLLag3JRQDCseytBNA sO/fnU0PFuSNs8nJgDUeWjT+b60xNbzO70CR3HpphdpcVQ+VumluamykS/Rx4CSzDDQl qSoBbiIKFP/45xQaowuHovKzZkljXcoXKs0osCawScLcIe1Wn+1sEaGSB2UagZxmGF2/ PMyQ== MIME-Version: 1.0 Received: by 10.152.129.137 with SMTP id nw9mr3259173lab.48.1334259576625; Thu, 12 Apr 2012 12:39:36 -0700 (PDT) Received: by 10.112.102.5 with HTTP; Thu, 12 Apr 2012 12:39:36 -0700 (PDT) In-Reply-To: <20120412183147.GD13291@denix.org> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> <20120412183147.GD13291@denix.org> Date: Thu, 12 Apr 2012 12:39:36 -0700 Message-ID: From: "Flanagan, Elizabeth" To: Patches and discussions about the oe-core layer X-Gm-Message-State: ALoCoQmC52kqlVPFfgh1v8q+10eR7QubF2IzFUZ2gP4IxoJc2tD2QHz/1DRJOoyiDAxh0i9JxTvG Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 19:50:12 -0000 Content-Type: multipart/alternative; boundary=f46d0430878e1a5b1b04bd80847a --f46d0430878e1a5b1b04bd80847a Content-Type: text/plain; charset=ISO-8859-1 On Thu, Apr 12, 2012 at 11:31 AM, Denys Dmytriyenko wrote: > On Thu, Apr 12, 2012 at 02:32:00PM -0300, Otavio Salvador wrote: > > On Thu, Apr 12, 2012 at 14:22, Koen Kooi > wrote: > > > You just volunteered to handle all the "Does it work with yocto 1.2?" > questions :) > > > > > > Simply put: people are stupid, they need explicit PHB compliant names > in tags, even if it isn't 100% politically correct to say "yocto" when we > actually mean "oe-core". > > > > > > Unless the yocto 1.2 release note state that it's based on oe-core > "foo" and all layers compatible with "foo" use "foo" in tags/branches. > > > > I think layers ought to have tags for both ... > > > > -oe-core- > > -yocto- > > And -poky- for completeness? > > Seriously, "yocto"-naming schema is not that bad. For shortness, it can be > "yp-1.2" as a suffix to the layer-specific tags... > > But I'm flexible with other naming schemas, such as "YYYY.MM" or "YYYY.#" > > I'm open to whatever naming scheme people want to decide on with few caveats. That it be painstakingly documented. That it can handle point releases and release candidates. I personally like YYYY.MM schemes, but, in the end, all I care about is that it's flexible, agreed upon and very well documented. -b -- > Denys > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > -- Elizabeth Flanagan Yocto Project Build and Release --f46d0430878e1a5b1b04bd80847a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Thu, Apr 12, 2012 at 11:31 AM, Denys = Dmytriyenko <denis@= denix.org> wrote:
On Thu, Apr 12, 2012 at 02:32:00PM -0300, Otavio Salvador= wrote:
> On Thu, Apr 12, 2012 at 14:22, Koen Kooi <koen@dominion.thruhere.net> wrote:
> > You just volunteered to handle all the "Does it work with yo= cto 1.2?" questions :)
> >
> > Simply put: people are stupid, they need explicit PHB compliant n= ames in tags, even if it isn't 100% politically correct to say "yo= cto" when we actually mean "oe-core".
> >
> > Unless the yocto 1.2 release note state that it's based on oe= -core "foo" and all layers compatible with "foo" use &q= uot;foo" in tags/branches.
>
> I think layers ought to have tags for both ...
>
> <layer>-oe-core-<tag>
> <layer>-yocto-<tag>

And <layer>-poky-<tag> for completeness?

Seriously, "yocto"-naming schema is not that bad. For shortness, = it can be
"yp-1.2" as a suffix to the layer-specific tags...

But I'm flexible with other naming schemas, such as "YYYY.MM" or "YYYY.#"


I'm open to whatever naming scheme people want to decide on= with few caveats. That it be painstakingly documented. That it can handle = point releases and release candidates. I personally like YYYY.MM schemes, but, in the end, all I care about is that it&= #39;s flexible, agreed upon and very well documented.

-b

--
Denys

_______________________________________________
Openembedded-core mailing list
Openembedded-co= re@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinf= o/openembedded-core



--
Elizabeth F= lanagan
Yocto Project
Build and Release
--f46d0430878e1a5b1b04bd80847a-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from starfish.geekisp.com ([216.168.135.166]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIQDd-0000td-HK for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 22:02:13 +0200 Received: (qmail 15561 invoked by uid 1003); 12 Apr 2012 19:46:12 -0000 Received: from unknown (HELO ?192.168.1.110?) (philip@opensdr.com@157.22.28.13) by mail.geekisp.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 12 Apr 2012 19:46:12 -0000 Message-ID: <4F873102.6020603@balister.org> Date: Thu, 12 Apr 2012 12:46:10 -0700 From: Philip Balister User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 MIME-Version: 1.0 To: Patches and discussions about the oe-core layer References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> <1334256020.7309.45.camel@ted> In-Reply-To: <1334256020.7309.45.camel@ted> X-Enigmail-Version: 1.1.2 Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 20:02:13 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 04/12/2012 11:40 AM, Richard Purdie wrote: > On Thu, 2012-04-12 at 14:32 -0300, Otavio Salvador wrote: >> On Thu, Apr 12, 2012 at 14:22, Koen Kooi wrote: >>> You just volunteered to handle all the "Does it work with yocto 1.2?" questions :) >>> >>> Simply put: people are stupid, they need explicit PHB compliant names in tags, even if it isn't 100% politically correct to say "yocto" when we actually mean "oe-core". >>> >>> Unless the yocto 1.2 release note state that it's based on oe-core "foo" and all layers compatible with "foo" use "foo" in tags/branches. >> >> I think layers ought to have tags for both ... >> >> -oe-core- >> -yocto- > > This would be rather sad if it were necessary. The whole point is we're > trying to build things which are compatible with each other. If that > turns out not to be the case I want to fix it, not encourage it. We need a coherent tag name to use across layers. The Yocto Project is the umbrella project, so using the yocto-project in the tag name is a good way to show this coordination among projects to people not familiar with how things are working. (As Koen notes, this makes communication with people whose primary exposure to the Yocto Project is watching youtube videos) I do not want to see table containing Yocto Project release information and they relate to a set of seemingly random tags in other layers. Philip PS: For various reasons, the tag needs to be yocto-project.... not yocto.... From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-we0-f175.google.com ([74.125.82.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIQHi-0000xp-Ab for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 22:06:26 +0200 Received: by wera1 with SMTP id a1so1523651wer.6 for ; Thu, 12 Apr 2012 12:57:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=cLVXfAGbeKCkZxUUQLkgt7iDnGkPMHhFn8VwRzg6D8A=; b=XILk9NsNEz7TdcopAA0T1A9cBBgX0eV6kf7C1kE084fRPtFBQUyFNU5ps7aFEO9NkB Pe+uG69JC5GEFEEWgpC2e5Mqio1lJVbnkXfGGq2s0PRpORDXr+9Gc/L5lhZgAAAFSd5D nKlhWqw4RA2ha9DPQ2xvtJt6q6rK9Z0KJf1pFgvhWLBGVnH5+ockyhkqVH3A40m+3pnv 0nFdk0LvmymLreFFSlgfS+YEp66II+bMMFOO8Ckh9jGS+dZgvGHezdxfYBdPshTqpe+g c+SzHTp9uYhHOj8I/kYKPW0VI4nc48FLRUQN+DsLWs1s7QfjO92qR/Gc/tHsYav1W9JU 4JaQ== Received: by 10.180.107.104 with SMTP id hb8mr8758051wib.8.1334260626027; Thu, 12 Apr 2012 12:57:06 -0700 (PDT) Received: from [172.20.1.36] (ip545070eb.adsl-surfen.hetnet.nl. [84.80.112.235]) by mx.google.com with ESMTPS id ff9sm54515372wib.2.2012.04.12.12.57.04 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Apr 2012 12:57:05 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1257) From: Koen Kooi In-Reply-To: <4F873102.6020603@balister.org> Date: Thu, 12 Apr 2012 21:57:02 +0200 Message-Id: References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> <1334256020.7309.45.camel@ted> <4F873102.6020603@balister.org> To: Patches and discussions about the oe-core layer X-Mailer: Apple Mail (2.1257) X-Gm-Message-State: ALoCoQmxLuNryLB7uVLdI8Zgm2nO+9tIiPCs3BXyngUFT5ufCb5dopA2eMc99l0Opjl6Aep1bhWB Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 20:06:26 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Op 12 apr. 2012, om 21:46 heeft Philip Balister het volgende geschreven: > On 04/12/2012 11:40 AM, Richard Purdie wrote: >> On Thu, 2012-04-12 at 14:32 -0300, Otavio Salvador wrote: >>> On Thu, Apr 12, 2012 at 14:22, Koen Kooi = wrote: >>>> You just volunteered to handle all the "Does it work with yocto = 1.2?" questions :) >>>>=20 >>>> Simply put: people are stupid, they need explicit PHB compliant = names in tags, even if it isn't 100% politically correct to say "yocto" = when we actually mean "oe-core". >>>>=20 >>>> Unless the yocto 1.2 release note state that it's based on oe-core = "foo" and all layers compatible with "foo" use "foo" in tags/branches. >>>=20 >>> I think layers ought to have tags for both ... >>>=20 >>> -oe-core- >>> -yocto- >>=20 >> This would be rather sad if it were necessary. The whole point is = we're >> trying to build things which are compatible with each other. If that >> turns out not to be the case I want to fix it, not encourage it. >=20 > We need a coherent tag name to use across layers. The Yocto Project is > the umbrella project, so using the yocto-project in the tag name is a > good way to show this coordination among projects to people not = familiar > with how things are working. (As Koen notes, this makes communication > with people whose primary exposure to the Yocto Project is watching > youtube videos) >=20 > I do not want to see table containing Yocto Project release = information > and they relate to a set of seemingly random tags in other layers. >=20 > Philip >=20 > PS: For various reasons, the tag needs to be yocto-project.... not = yocto.... "yoctoproject", without the hyphen to be consistent with the domainname = :)= From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vms173005pub.verizon.net ([206.46.173.5]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIQzM-0001VR-17 for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 22:51:32 +0200 Received: from gandalf.denix.org ([unknown] [71.178.225.66]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0M2D00BEHTDBFC34@vms173005.mailsrvcs.net> for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 14:41:35 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id F178520099; Thu, 12 Apr 2012 15:41:34 -0400 (EDT) Date: Thu, 12 Apr 2012 15:41:34 -0400 From: Denys Dmytriyenko To: Patches and discussions about the oe-core layer Message-id: <20120412194134.GE13291@denix.org> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> MIME-version: 1.0 In-reply-to: User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 20:51:32 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Thu, Apr 12, 2012 at 08:31:13PM +0100, Julian Pidancet wrote: > On Thu, Apr 12, 2012 at 5:55 PM, Khem Raj wrote: > > > > I think that string is fine as long as its just for yocto but I think > > for OE-Core we are going to do a General release > > so tagging that with something yocto project will be very confusing > > unless we plan to do different releases of OE-Core for general > > availability > > and yocto project. I dont think we have bandwidth for that. And since > > poky repository makes a copy of OE-Core metadata it can be tagged in > > yoctoproject specific tags > > > > In case there is an oe-core general availability release separated > from the yocto release, when would that happen ? Is there anything > planned yet ? There is a plan to have oe-core tagged at the same time as the Yocto Project release. That's what we've discussed at BSP and Collab Summits. Here we are deciding on the naming for those tags. There are no plans to have separate OE-Core releases - i.e. separate from the corresponding Yocto Project releases. -- Denys From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vms173001pub.verizon.net ([206.46.173.1]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIRTz-0002Kp-Nr for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 23:23:11 +0200 Received: from gandalf.denix.org ([unknown] [71.178.225.66]) by vms173001.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0M2D00K9NXMJLEM0@vms173001.mailsrvcs.net> for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 16:13:36 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id 16F5920099; Thu, 12 Apr 2012 17:13:30 -0400 (EDT) Date: Thu, 12 Apr 2012 17:13:30 -0400 From: Denys Dmytriyenko To: Patches and discussions about the oe-core layer Message-id: <20120412211330.GG13291@denix.org> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> <1334256020.7309.45.camel@ted> <4F873102.6020603@balister.org> MIME-version: 1.0 In-reply-to: User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 21:23:12 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Thu, Apr 12, 2012 at 09:57:02PM +0200, Koen Kooi wrote: > > Op 12 apr. 2012, om 21:46 heeft Philip Balister het volgende geschreven: > > > On 04/12/2012 11:40 AM, Richard Purdie wrote: > >> On Thu, 2012-04-12 at 14:32 -0300, Otavio Salvador wrote: > >>> On Thu, Apr 12, 2012 at 14:22, Koen Kooi wrote: > >>>> You just volunteered to handle all the "Does it work with yocto 1.2?" questions :) > >>>> > >>>> Simply put: people are stupid, they need explicit PHB compliant names in tags, even if it isn't 100% politically correct to say "yocto" when we actually mean "oe-core". > >>>> > >>>> Unless the yocto 1.2 release note state that it's based on oe-core "foo" and all layers compatible with "foo" use "foo" in tags/branches. > >>> > >>> I think layers ought to have tags for both ... > >>> > >>> -oe-core- > >>> -yocto- > >> > >> This would be rather sad if it were necessary. The whole point is we're > >> trying to build things which are compatible with each other. If that > >> turns out not to be the case I want to fix it, not encourage it. > > > > We need a coherent tag name to use across layers. The Yocto Project is > > the umbrella project, so using the yocto-project in the tag name is a > > good way to show this coordination among projects to people not familiar > > with how things are working. (As Koen notes, this makes communication > > with people whose primary exposure to the Yocto Project is watching > > youtube videos) > > > > I do not want to see table containing Yocto Project release information > > and they relate to a set of seemingly random tags in other layers. > > > > Philip > > > > PS: For various reasons, the tag needs to be yocto-project.... not yocto.... > > "yoctoproject", without the hyphen to be consistent with the domainname :) Technically, yocto-project.org is a valid domain name too, as it properly redirects to yoctoproject.org and both are registered by the Linux Foundation. Should we put it to vote? While we still have time before the release, we need to agree on the naming eventually. -- Denys From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-vb0-f47.google.com ([209.85.212.47]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIRWs-0002Oe-Ht for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 23:26:10 +0200 Received: by vbbfr13 with SMTP id fr13so1896845vbb.6 for ; Thu, 12 Apr 2012 14:16:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=dqGGsLXIluGU/xOD1sAv+iNSL5wFvJ0jMXFnWuGRzJU=; b=BfPzrtBB7uhPOaoxd+9mzHMQgVGN5orTNgSJ9d1A/jLR6veANk/1bfMs71LuGDO/Vu OPoRC1DOhUo//CDS0XFG3SwkxSBYxpYTwiPMYSXOBq27zv80YbRw+rLOWGDsGoFjOryu opgEM3c2jZMhDHvWAS0Nghl6oaq/6EXMhgX2MUH5ZXnOGWoZdScYegkQBRTJZz2O45PA HG6kE175Uw/qO+E6J8UQtB3YIvi0RCqXdESwQaCunATJpJxDdKtUp7DJIiFfjdPPZn9r vpQdGBkA6nJ645/iEBalzs07DnJzgrK6XZ+fycPoyo4MIGsjcJ2LvHguOo5iNy0Qv5mN N1ag== MIME-Version: 1.0 Received: by 10.220.150.14 with SMTP id w14mr2030251vcv.59.1334265409508; Thu, 12 Apr 2012 14:16:49 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.220.49.138 with HTTP; Thu, 12 Apr 2012 14:16:49 -0700 (PDT) In-Reply-To: <20120412211330.GG13291@denix.org> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> <1334256020.7309.45.camel@ted> <4F873102.6020603@balister.org> <20120412211330.GG13291@denix.org> Date: Thu, 12 Apr 2012 18:16:49 -0300 X-Google-Sender-Auth: bL83rVui1O2yQazHh_3IJKuD4ks Message-ID: From: Otavio Salvador To: Patches and discussions about the oe-core layer Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 21:26:10 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Apr 12, 2012 at 18:13, Denys Dmytriyenko wrote: > Should we put it to vote? While we still have time before the release, we= need > to agree on the naming eventually. yp-1.2 +1 yocto-project-1.2 +1 --=20 Otavio Salvador=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0O= .S. Systems E-mail: otavio@ossystems.com.br=A0 http://www.ossystems.com.br Mobile: +55 53 9981-7854=A0 =A0 =A0 =A0=A0 =A0 =A0 =A0http://projetos.ossys= tems.com.br From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.pbcl.net ([88.198.119.4] helo=hetzner.pbcl.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIRk1-0002fT-Po for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 23:39:45 +0200 Received: from blundell.swaffham-prior.co.uk ([91.216.112.25] helo=[192.168.114.6]) by hetzner.pbcl.net with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1SIRb1-0004Hf-FR for openembedded-core@lists.openembedded.org; Thu, 12 Apr 2012 23:30:27 +0200 Message-ID: <1334266176.3382.75.camel@x121e.pbcl.net> From: Phil Blundell To: Patches and discussions about the oe-core layer Date: Thu, 12 Apr 2012 22:29:36 +0100 In-Reply-To: <20120412211330.GG13291@denix.org> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> <1334256020.7309.45.camel@ted> <4F873102.6020603@balister.org> <20120412211330.GG13291@denix.org> X-Mailer: Evolution 3.2.2-1 Mime-Version: 1.0 Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 21:39:45 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2012-04-12 at 17:13 -0400, Denys Dmytriyenko wrote: > Should we put it to vote? While we still have time before the release, we need > to agree on the naming eventually. To be honest, it seems to me like a vote would be a waste of time. It's only a name, after all. This is Richard's project and I think he should probably just pick a tag name that he likes and be done with it. p. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-we0-f175.google.com ([74.125.82.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIbaX-000321-WC for openembedded-core@lists.openembedded.org; Fri, 13 Apr 2012 10:10:38 +0200 Received: by wera1 with SMTP id a1so1779937wer.6 for ; Fri, 13 Apr 2012 01:01:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=kBMeaB9zuvVowyc4jyvWibOnCYvmqJhg1MIGIvRSAVQ=; b=XVTe1Yr1JULHsAoAlnq795pxCTNRl1vhiWA+6pH6/uxyvtu0dZEnGfDDWUykEJ795P w6FxUx905agu/DNmwKzIGgTYWkNi06gxWpeJwmj7QNGaAa1tYFkr/T4A4MFustaP+Otu tb1eYKzpl8ju8rtZGscSSL6/9AX103sSBRoWhYyN/ORcLaGDxsBgJRIAcKVbxOZfxSaj Is02S48NGmbaA5tBir4Ku14KY8bWzlgJaSK+wAqBRN5YzQ3Y/aOBWVD3YCIwfa0zNu2l nFeWkfWLTCb1t11QiAQUAdhCNdYxUSgVQ2CeVm/oBktboUMnC3BSf8bU38Uw6SE5cEhk qXBQ== MIME-Version: 1.0 Received: by 10.180.104.230 with SMTP id gh6mr1340602wib.22.1334302394307; Fri, 13 Apr 2012 00:33:14 -0700 (PDT) Received: by 10.227.128.9 with HTTP; Fri, 13 Apr 2012 00:33:13 -0700 (PDT) X-Originating-IP: [93.114.75.57] Received: by 10.227.128.9 with HTTP; Fri, 13 Apr 2012 00:33:13 -0700 (PDT) In-Reply-To: <1334266176.3382.75.camel@x121e.pbcl.net> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> <1334256020.7309.45.camel@ted> <4F873102.6020603@balister.org> <20120412211330.GG13291@denix.org> <1334266176.3382.75.camel@x121e.pbcl.net> Date: Fri, 13 Apr 2012 10:33:13 +0300 Message-ID: From: Andrei Gherzan To: Patches and discussions about the oe-core layer X-Gm-Message-State: ALoCoQmWPlQu54XRFzZp6DArWn3JoNcw84Sfm4wEgh1HkjZ5EUgWYg/ONlW1x6R+YGyN4+y//BXz Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2012 08:10:38 -0000 Content-Type: multipart/alternative; boundary=f46d04428dca3c538604bd8a7cd1 --f46d04428dca3c538604bd8a7cd1 Content-Type: text/plain; charset=ISO-8859-1 On Apr 13, 2012 12:30 AM, "Phil Blundell" wrote: > > On Thu, 2012-04-12 at 17:13 -0400, Denys Dmytriyenko wrote: > > Should we put it to vote? While we still have time before the release, we need > > to agree on the naming eventually. > > To be honest, it seems to me like a vote would be a waste of time. It's > only a name, after all. This is Richard's project and I think he should > probably just pick a tag name that he likes and be done with it. > One vote for this! > p. > > > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core --f46d04428dca3c538604bd8a7cd1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On Apr 13, 2012 12:30 AM, "Phil Blundell" <philb@gnu.org> wrote:
>
> On Thu, 2012-04-12 at 17:13 -0400, Denys Dmytriyenko wrote:
> > Should we put it to vote? While we still have time before the rel= ease, we need
> > to agree on the naming eventually.
>
> To be honest, it seems to me like a vote would be a waste of time. =A0= It's
> only a name, after all. =A0This is Richard's project and I think h= e should
> probably just pick a tag name that he likes and be done with it.
>

One vote for this!

> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedd= ed-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedde= d-core

--f46d04428dca3c538604bd8a7cd1-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wg0-f43.google.com ([74.125.82.43]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SIeLw-0006jU-IV for openembedded-core@lists.openembedded.org; Fri, 13 Apr 2012 13:07:44 +0200 Received: by wgbdr12 with SMTP id dr12so2443160wgb.24 for ; Fri, 13 Apr 2012 03:58:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=X+eoaSoD0X3fZldOMif3YMRpCI4QLk1mdJPqIc+uMyA=; b=oJg5Ut8Zs1x8eBXy5sADV5r8sWmPageNPuBW/v3kc/b7hWGN/VECWhQ0eFM0uwXbRh 1Bpo97GrsljcAC0Q6ZQWbYDm3omR/5KpKG4jH5rvHZmtL9T1M2asv/FPX2SCOZeR7Z6v cZ/PwIPd23iIZZgA1e26Dmrtzy27Ec2bgVIL+w439rbvKnkUxFpqwO56QsFdiksK/Gj5 SRoFRz0Evaa6yop8o7azzHd94XKIMdj07GMbe067kNXVc0pIpW47h6xF28TZLS9esm8/ pUSFeCuPlLHMWPvn5FZUqJ5ZoM1cY3HHnG5zAdUkoR/1Dx1mcNc6DaopweAffuheZGon NsUw== MIME-Version: 1.0 Received: by 10.180.76.240 with SMTP id n16mr2807955wiw.10.1334314703612; Fri, 13 Apr 2012 03:58:23 -0700 (PDT) Received: by 10.223.62.6 with HTTP; Fri, 13 Apr 2012 03:58:23 -0700 (PDT) In-Reply-To: <4F873102.6020603@balister.org> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <4543FDF1-0512-4B36-ABB3-DBB957B86E88@dominion.thruhere.net> <1334256020.7309.45.camel@ted> <4F873102.6020603@balister.org> Date: Fri, 13 Apr 2012 12:58:23 +0200 Message-ID: From: Anders Darander To: Patches and discussions about the oe-core layer Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2012 11:07:44 -0000 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Apr 12, 2012 at 21:46, Philip Balister wrote: > On 04/12/2012 11:40 AM, Richard Purdie wrote: >> On Thu, 2012-04-12 at 14:32 -0300, Otavio Salvador wrote: >>> On Thu, Apr 12, 2012 at 14:22, Koen Kooi wrote: >>>> You just volunteered to handle all the "Does it work with yocto 1.2?" questions :) >>>> >>>> Simply put: people are stupid, they need explicit PHB compliant names in tags, even if it isn't 100% politically correct to say "yocto" when we actually mean "oe-core". >>>> >>>> Unless the yocto 1.2 release note state that it's based on oe-core "foo" and all layers compatible with "foo" use "foo" in tags/branches. >>> >>> I think layers ought to have tags for both ... >>> >>> -oe-core- >>> -yocto- >> >> This would be rather sad if it were necessary. The whole point is we're >> trying to build things which are compatible with each other. If that >> turns out not to be the case I want to fix it, not encourage it. > > We need a coherent tag name to use across layers. The Yocto Project is > the umbrella project, so using the yocto-project in the tag name is a > good way to show this coordination among projects to people not familiar > with how things are working. (As Koen notes, this makes communication > with people whose primary exposure to the Yocto Project is watching > youtube videos) I'm also in favor of a yocto-project-1.2 tag, for the same reason as Koen and Philip mention. That would make it easier communicating with customers and PHB's that has heard of Yocto Project... > I do not want to see table containing Yocto Project release information > and they relate to a set of seemingly random tags in other layers. The risk for this is definitely somewhat higher with a strict YYYY-XX release tag (which also might collide with other projects/layer more easily). Thus, I'm advocating a 'yocto-project'-prefix for the tags in question. /Anders From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wi0-f169.google.com ([209.85.212.169]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SKRL1-0001gZ-6v for openembedded-core@lists.openembedded.org; Wed, 18 Apr 2012 11:38:11 +0200 Received: by wibhm17 with SMTP id hm17so394554wib.0 for ; Wed, 18 Apr 2012 02:28:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=8e8xUD1/meDaTssfJY/JjFipeODGaBWPhZFluBpzb8U=; b=GiT+hpkpPrue5HgwOnNzEcQQ/n/bmbfoFQ+FIWNvwUMqRvHPGSzEM26Rly+v9QWR6c R+dxxlZN9W+H0r3jk/TC7rcowZn2ImHGNS1Qwlx+NodkYl+RB49Mn1m7nfRdzirxeE8b HxwGbRy+bMHFblailXqJcXtpIjnZqXvNN7KrVWNeGc3VRvSL9OK7NHcdQQ2aIzhzpbge haHMe4nfuo0DKMTvYU/oysz/1eE16J941VXsodXQ8kne/gTuvG2eNNUjnB8Ta1Ex9sPI GDvtfniHCM8gacx4nWROzs6r1tGxkpafHRh50PutD/VdBbjZyu/c4nnQGPnbDFjZlK5A 0/pA== Received: by 10.180.81.37 with SMTP id w5mr4430885wix.16.1334741324012; Wed, 18 Apr 2012 02:28:44 -0700 (PDT) Received: from [172.20.0.96] (ip545070eb.adsl-surfen.hetnet.nl. [84.80.112.235]) by mx.google.com with ESMTPS id ea6sm33294734wib.5.2012.04.18.02.28.42 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 Apr 2012 02:28:42 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1257) From: Koen Kooi In-Reply-To: <1334221321.31685.24.camel@ted> Date: Wed, 18 Apr 2012 11:28:41 +0200 Message-Id: <818A5ABA-BD12-43CF-94FC-539A757435DD@dominion.thruhere.net> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> To: Patches and discussions about the oe-core layer X-Mailer: Apple Mail (2.1257) X-Gm-Message-State: ALoCoQms8u46t+FFTq4Ffomps3U74tJU4G4x1aUyufNn5n2tgkUQmkMV8Z6wSfd5LQpBZ/gOrTmA Subject: Re: Yocto Project 1.2 M4 schedule X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2012 09:38:11 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Op 12 apr. 2012, om 11:02 heeft Richard Purdie het volgende geschreven: > On Wed, 2012-04-11 at 01:51 +0100, Julian Pidancet wrote: >> On 04/09/12 19:01, Liu, Song wrote: >>> Hi all, >>>=20 >>> This is to restate and clarify the schedule for Yocto Project 1.2 M4 = (milestone 4). If you are concerned or have patches you would like to = merge, please see the following dates: >>>=20 >>> 1. RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT >>> 2. RC3 build: April 11th, 2012, PDT >>> 3. RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT >>> 4. RC4 build: April 18th, 2012, PDT >>> 5. YP 1.2 release: April 27th, 2012, PDT >>>=20 >>> You can also check out the schedule here: = https://www.google.com/calendar/embed?height=3D600&wkst=3D1&bgcolor=3D%23F= FFFFF&src=3Dmg0m150m30gs891eqqhtfu5jgg%40group.calendar.google.com&color=3D= %238C500B&src=3Dsc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com&col= or=3D%23528800&src=3Dtheyoctoproject%40gmail.com&color=3D%23182C57&ctz=3DA= merica%2FLos_Angeles=20 >>>=20 >>> Please feel free to let me and Beth know if you have any concerns or = questions. >>>=20 >>> Thanks! >>> Song >>> PM, Yocto Project >>=20 >> Hi, >>=20 >> I don't see any commits tagged for these milestones in >> git.openembedded.org/openembedded-core at the moment. Will there be a >> release tag or a release branch created on the git repository when YP >> 1.2 comes out, to indicate people that there's a "stable" version of >> oe-core they can use ? >=20 > Yes, there will be a branch created on OE-Core.=20 >=20 > At this point the actual branch naming/tagging is a little in flux. > There was some discussion about this at collaboration summit and the = BSP > summit but there was no conclusion. >=20 > I've tried to write an email on the subject and it basically goes = around > in circles. Ideally we need a scheme which can be used in all the = layers > which doesn't contain numbers as these may conflict with various layer > schemes. The poky release names at least do that. Ideally people also > want something sortable with more context such as the year. Doing this > without numbers is harder. >=20 > I'm reluctant to change the numbering/branch scheme at this point in a > release as its unfair to release engineering and the documentation > maintainers. Any update on this? I'd like to have the angstrom scripts and = repositories ready before the end of the week and having some form of = agreement on branch/tag naming would be awesome. regards, Koen From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SKS7B-0004mJ-Om for openembedded-core@lists.openembedded.org; Wed, 18 Apr 2012 12:27:57 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q3IAITq5032691; Wed, 18 Apr 2012 11:18:29 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 31095-10; Wed, 18 Apr 2012 11:18:25 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q3IAILYe032684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Apr 2012 11:18:23 +0100 Message-ID: <1334744304.24091.46.camel@ted> From: Richard Purdie To: Koen Kooi Date: Wed, 18 Apr 2012 11:18:24 +0100 In-Reply-To: <818A5ABA-BD12-43CF-94FC-539A757435DD@dominion.thruhere.net> References: <7E680CB2A76BB8438D08CF13C09FC53A46B06325@FMSMSX151.amr.corp.intel.com> <4F84D58F.8020608@gmail.com> <1334221321.31685.24.camel@ted> <818A5ABA-BD12-43CF-94FC-539A757435DD@dominion.thruhere.net> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Cc: Patches and discussions about the oe-core layer Subject: Yocto Project Branch/Release Naming X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2012 10:27:58 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Wed, 2012-04-18 at 11:28 +0200, Koen Kooi wrote: > Op 12 apr. 2012, om 11:02 heeft Richard Purdie het volgende geschreven: > > Yes, there will be a branch created on OE-Core. > > > > At this point the actual branch naming/tagging is a little in flux. > > There was some discussion about this at collaboration summit and the BSP > > summit but there was no conclusion. > > > > I've tried to write an email on the subject and it basically goes around > > in circles. Ideally we need a scheme which can be used in all the layers > > which doesn't contain numbers as these may conflict with various layer > > schemes. The poky release names at least do that. Ideally people also > > want something sortable with more context such as the year. Doing this > > without numbers is harder. > > > > I'm reluctant to change the numbering/branch scheme at this point in a > > release as its unfair to release engineering and the documentation > > maintainers. > > Any update on this? I'd like to have the angstrom scripts and > repositories ready before the end of the week and having some form of > agreement on branch/tag naming would be awesome. I've been giving this a lot of thought. Whilst I didn't say much in this thread, I did read it and am considering everything that was said. The most logical initial choice would be "yocto-project-1.2". I think that real world use of it would cause several problems though. The number in the name creates conflict for a start. If you want to release version X of a BSP/Angstrom/OE-Core/Poky or even bitbake, figuring out the relationship between 1.2 and the local release numbering is hard and confusing. I don't really want to impose a unified numbering system with the Yocto Project, particularly as many components have numbering systems already. I'm already conscious of the "When will there be a Yocto Project 2.0" and I think these numbering schemes are artificial for that reason. Also, Yocto Project is a trademark and I know there are discussions going on at the moment about how/when it should be used and so on. I can't imagine there being a problem in this area but we should really let those discussions conclude which they have not as yet. Finally, I think its unfair to pull the rug out from under release engineering by changing things at this stage of a release. So, I therefore want to continue to use codenames for the release branches and this release will be "denzil". The main downside to these codenames is the lack of sorting which I'm going to categorize as unfortunate. It therefore follows based off my comment above that tags will continue to use the version scheme used by the specific projects. I am going to encourage "denzil" branches in repositories to show compatibility and strongly recommend to the OE TSC that we have a denzil branch in the OE-Core repository instead of 2012-1. Bitbake is the one exception I'd make to the denzil branch naming scheme, not least as its supposed to be backwards compatible and work anywhere so the branch naming applies to metadata and not bitbake. We can tag OE-Core as 2012-1 if so desired although I am starting to dislike that version scheme for its bad handling of point releases (it looks like a date). I guess that is a discussion for the next TSC meeting. So we have a decision, I'm not sure everyone will love this but such is life. Cheers, Richard