Re: release branch for meta-ti?

[Denys Dmytriyenko <denis@denix.org>]

On Sat, Mar 31, 2012 at 04:38:47PM +0100, Richard Purdie wrote:
> On Sat, 2012-03-31 at 10:27 -0400, Philip Balister wrote:
> > On 03/30/2012 06:17 PM, William Mills wrote:
> > > On 03/30/2012 06:09 PM, Koen Kooi wrote:
> > > I have no objection to the branch to ensure the current working
> > > functionality remains working with yocto maintenance releases.
> > > 
> > > However, I don't think we should actively maintain new features on both
> > > branches.
> > > 
> > > So what is the goal of the branch?
> > 
> > People that ship OE based stuff to customers hate basing stuff that goes
> > to customers based on layers that are under active development. We are
> > much happier with layers that are getting fixes for existing problems only.
> 
> I'd echo this. Whilst its nice for developers to just keep iterating on
> continual development, it doesn't actually work for users and having
> some kind of release/stable branch helps a lot.
> 
> This is why the Yocto Project is having releases and those releases are
> being maintained with point releases containing fixes. We don't add new
> features in the release branches.
> 
> I'd strongly encourage this model to various layers. I appreciate its
> not the way OE has worked in the past and it takes a bit of work to
> change developer mindset on this though.

All,

We had few opportunities to further discuss this matter at the Yocto BSP 
Summit and the Yocto Day at the Linux Collab during last week...

The outcome was that we'd like to recommend for all the layers (including 
meta-ti :) ) to apply the same tag at the same time of the Yocto release and, 
if needed, create the corresponding maintenance branch. The current release 
schedule of the Yocto Project is (roughly) every 6 month around April and 
October. We still need to decide on the exact naming convention for those tags 
and branches, which I hope will be discussed and finalized at the yocto 
mailing list in time for the release in the coming weeks.

-- 
Denys