On Fri, 2011-12-09 at 11:36 -0500, Philip Balister wrote: > On 12/09/2011 11:20 AM, Richard Purdie wrote: > > On Fri, 2011-12-09 at 15:46 +0000, McClintock Matthew-B29882 wrote: > >> On Fri, Dec 9, 2011 at 5:51 AM, Richard Purdie > >> <richard.pur...@linuxfoundation.org> wrote: > >>> On Thu, 2011-12-08 at 20:01 +0000, McClintock Matthew-B29882 wrote: > >>>> Hi all, > >>>> > >>>> Can we create a meta-oe repo in git.yoctoproject.org? > >>> > >>> This might create a little friction with the OE community. What would be > >>> the reason for the repository? > >>> > >>>> I'd like to also > >>>> create a branh within the repo that tracks a valid version of the repo > >>>> for specific Yocto releases. > >>>> > >>>> (I can add that in my investigation so far - > >>>> f78f3f31c06c669006fcb567c8f503d4dbec68da looks like a good starting > >>>> commit for edison) > >>> > >>> I'd certainly be happy to see such a branch. It might be more > >>> appropriate to call it 2011-1 which corresponds to the OE-Core branch > >>> name that is edison in the poky repo. > >> > >> Well I don't particularly care if we create a repo or not. I just want > >> a place to go for a working meta-oe for all future releases of Yocto. > >> I had to figure this out on my own, but I'm can imagine others will > >> attempt similar things. > > > > I think it should be fine to add an appropriate branch to the meta-oe > > repository itself. > > We should probably have this discussion on the oe list. > > Basically, we should have a way to create a "stable" branch for oe-core > and meta-oe. There also needs to be some "policy" in place for commits. > The primary concern is making sure the development branches get all > needed fixes that go into the branches.
There is a 2011-1 branch in oe-core and there is going to be an update policy of bugfixes but not upgrades or new features for that. Cheers, Richard _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
