[fedora-arm] Fedora 16

[omalleys at msu.edu]

Right.

My concerns still are we need to make sure the current patches are  
getting upstream to f16+ and rawhide.

I hate to see time wasted trying to track down already fixed bugs.  
There are other people working on ARM support ie Ubuntu, and upgraded  
versions of the software may actually fix some issues.  (yes there  
still will be issues.)

Given the decision has been made to forgo the F16 release.

Can we get away with taking a snapshot of the F15 base and F15 Updates  
trees, and merge them and call that F15 base?

All the work that was done for F14 is really all in F16. It may not  
appear in F15 base, but may appear in F15 updates. Depending on  
when/if the patches were applied.

Or is this not the case?






Quoting Jonathan Masters <jcm at redhat.com>:

> Plan was to release a good enough F15 but absolutely to do some kind  
> of release (just cap when we will move on to keep momentum - a  
> couple more weeks and we need to be focused on rawhide). It's F16 we  
> are wanting to skip in order to focus on rawhide by the new year.
>
> --
> Sent from my phone - message formatted and/or shortened accordingly.
>
>
> -----Original Message-----
> From: Peter Robinson [pbrobinson at gmail.com]
> Received: Tuesday, 25 Oct 2011, 11:17
> To: Chris Tyler [chris at tylers.info]
> CC: Fedora ARM secondary architecture list [arm at lists.fedoraproject.org]
> Subject: Re: [fedora-arm] Fedora 16
>
>
> On Tue, Oct 25, 2011 at 6:09 PM, Chris Tyler <chris at tylers.info> wrote:
>> On Tue, 2011-10-25 at 17:49 +0100, Peter Robinson wrote:
>>> So what's the status of this? Are we using the F-15 as the external
>>> repo base for building F-17? When is it going to happen? My
>>> understanding is we have enough of both arches built that we can start
>>> this rolling. It would be good to see some public movement on this now
>>> and to get this rolling rather than delaying further.
>>
>> No one's delaying, but there is a sequence to this that we shouldn't
>> short-circuit:
>>
>> * Sync up the armv5tel and armv7hl pre-koji package sets <= We are here
>> * Do final F15 build in Koji
>
> It was my understanding from dgilmore's proposal above that we were
> going to skip F-15 and just go straight to F-17. Ultimately whether we
> do a final F-15 or F-17 it doesn't really matter, the current build
> tool chain for them both is derived from gcc 4.6.1
>
>> * Release F15 (& start F15-updates builds)
>> * Finalize koji changes for rawhide (rpm, rpmbuild, yum, koji, armv7hl
>> rootfs)
>> * Do necessary prebuilds for rawhide (build-previous or other)
>> * Build for rawhide, shadow PA as closely as possible
>> * Branch F17 when PA does
>>
>> At the end of this process we'll be building for at least three releases
>> (F15updates, F17, rawhide) across two archs - 6 builds total.
>
> Why? I thought the above process was with the idea of just using the
> F-15 work that was done as a base to go straight to F-17 and forget
> the rest. Clearly people need to start documenting the exact process
> for all to see.
>
> Peter
> _______________________________________________
> arm mailing list
> arm at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/arm
>



-- 
"The information in this email, and attachment(s) thereto, is strictly  
confidential and may be legally privileged. It is intended solely for  
the named recipient(s), and access to this e-mail, or any  
attachment(s) thereto, by anyone else is unauthorized. Violations  
hereof may result in legal actions. Any attachment(s) to this e-mail  
have been checked for viruses, but please rely on your own  
virus-checker and procedures. If you contact us by e-mail, we will  
store your name and address to facilitate communications in the matter  
concerned. If you do not consent to us storing your name and address  
for above stated purpose, please notify the sender promptly. Also, if  
you are not the intended recipient please inform the sender by  
replying to this transmission, and delete the e-mail, its  
attachment(s), and any copies of it without, disclosing it."