[meego-releases] 1.1 Branch created
anas.nashif at intel.com
Wed Sep 29 17:35:16 PDT 2010
On 2010-09-29, at 7:39 PM, Shane Bryan wrote:
> On Wed, Sep 29, 2010 at 10:43:39AM -0700, Chris Ferron wrote:
>> On 09/29/2010 10:31 AM, Shane Bryan wrote:
>>> On Wed, Sep 29, 2010 at 09:07:14AM -0700, Nashif, Anas wrote:
>>>> We also have *:Testing for the branched projects as discussed, but
>>>> those are not populated yet, this is WIP right now.
>>>> This basically means that Trunk is now open for development. Two
>>>> things to note:
>>>> - Some of the submissions currently in Trunk:Testing (those not
>>>> accepted) might be targeting 1.1, so those need to be resubmitted for
>>>> 1.1 now.
>>>> - All changes to 1.1 also have to be submitted against the Trunk where
>>>> it applies
>>> Anas (or Chris), could you clarify the prefered way to SR packages into
>>> 1.1 for handset packages?
>>> Prior to the branch, we would package/test from devel:ux:handset, and
>>> then SR from there into Trunk:Handset (devel:us:handset -> Trunk:Handset)
>>> I assume this remains true for Trunk (aka 1.2) related work.
>>> For 1.1 work, what is your expected flow? I see there is now
>>> MeeGo:1.1:Handset (1.1 branch equivalent to Trunk:Handset) and a new
>>> project called MeeGo:1.1:Handset:Testing
>>> Is the expected workflow now as follows?
>> I have not agreed to this so until otherwise detailed, handset will
>> continue how we have been working.
>>> devel:ux:handset -> MeeGo:1.1:Handset:Testing -> MeeGo:1.1:Handset
>>> If so, how do we distinguish between package updates targeted for Trunk
>>> (1.2, ...) vs those only for the 1.1 branch? I vaguely recall something
>>> about personal "branch" projects as the right source for SR submissions,
>>> but having never used them, would appreciate some clarification.
>> You will need two sandboxes at this point. 1 to stage CCB work for
>> 1.1 and 1 to stage 1.2(trunk) work.
>> I will continue to support you team with the flow we have worked
>> out, regardless.
>> and before you ask, yes the work duplication while under CCB is
>> painful and time consuming. But the time span will be way shorter
>> then 1.0.
> Yes, knew this to be the case. Thanks for the necessary reminder
> though, in case others were still in denial ;)
>> Once the branching is done, I will set you up a 1.1 sandbox., and
>> send your team a note.
> Thanks for the clarification Chris. Any ETA on when the branching
> will be done and a sandbox created? IOW, is it something we can
> expect to have resoloved in time to begin filing SRs (and testing
> the process) for the build this Friday?
Branching is already done for a while, now the :Testing projects are ready as well, now using "project links" which should speed up testing and building of packages, since we build in 2 modes now:
- localdep: Just builds the package and its dependencies
- standard: That is the default behaviour
In general, the preferred way is to branch from the :Testing project and submit from your branch, since we are in code freeze and change control, it is cleaner since a branch always guarantees you are building against the right targets.
> Meego-releases mailing list
> Meego-releases at meego.com
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
More information about the Meego-releases