[RFC] Create a Release Notes document

[RFC] Create a Release Notes document

[Otavio Salvador]

Hello,


As our community BSP is growing the need for more documentation is
also getting more important so I’d like to propose the creation of a
Release Notes document.


The idea is it to create it colaboratively, so people who wants to
help, can contribute to its creation and be an active part of it. My
proposed strucuture of the document would be the following:


SUMARY

    Index
    Introduction
    BSP scope
        meta-fsl-arm
        meta-fsl-arm-extra
    Supported machines
    Hardware acceleration
         GPU
         VPU/IPU
    Know issues
          …

What your thoguhts about all this? Do you want to be part of it?

Regards,

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [RFC] Create a Release Notes document

[Steven Grunza]

On 4/15/2013 9:16 AM, Otavio Salvador wrote:
> Hello,
>
>
> As our community BSP is growing the need for more documentation is
> also getting more important so I’d like to propose the creation of a
> Release Notes document.
>
>
> The idea is it to create it colaboratively, so people who wants to
> help, can contribute to its creation and be an active part of it. My
> proposed strucuture of the document would be the following:
>
>
> SUMARY
>
>      Index
>      Introduction
>      BSP scope
>          meta-fsl-arm
>          meta-fsl-arm-extra
>      Supported machines
>      Hardware acceleration
>           GPU
>           VPU/IPU
>      Know issues
>            …
>
> What your thoguhts about all this? Do you want to be part of it?
>
> Regards,
>
> --
> Otavio Salvador                             O.S. Systems
> E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
> Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
>
Perhaps it's just my extreme newness to git but I would find a section 
with directions on how to go from a completely empty directory to a 
finished build quite useful.  I always seem to have problems with being 
on the wrong branch and when I reach out for help I get instructions to 
"use the correct branch" but no info on how to switch to the correct 
branch.  Reading the man pages is important but there are sometimes 
things that just can't be figured out from man pages.

RES: [RFC] Create a Release Notes document

[Angolini Daiane-B19406]

________________________________________
De: meta-freescale-bounces@yoctoproject.org [meta-freescale-bounces@yoctoproject.org] em nome de Steven Grunza [steven.grunza@gmail.com]
Enviado: segunda-feira, 15 de abril de 2013 22:03
Para: meta-freescale@yoctoproject.org
Assunto: Re: [meta-freescale] [RFC] Create a Release Notes document

> Perhaps it's just my extreme newness to git but I would find a section
> with directions on how to go from a completely empty directory to a
> finished build quite useful.  I always seem to have problems with being
> on the wrong branch and when I reach out for help I get instructions to
> "use the correct branch" but no info on how to switch to the correct
> branch.  Reading the man pages is important but there are sometimes
> things that just can't be figured out from man pages.

I´m planning to start an Yocto Training on iMX-Community, I hope it can help you. I´m finishing some task before publish it. Are you member of iMX-Community?

The proposed document in this thread is the Release Notes, it describes the release itself, and do not include any how-to or training.

If you´re using repo to download your source code, if you want to migrate from danny to master you can:

$ repo init -b master
$ repo sync


master holds the newest source code, it´s under development, so it´s unstable (we are always finding and fixing bugs)

danny is the latest stable branch. For this branch we only accept bug-fix patches. No new feature, no version upgrade (at least without a very good argument)

I´m happy that you´ve been participating and I don´t care you´re new with git. After few month you will become an expert and I hope you can send patches to mail list as well. So, keep in touch, and keep helping us to get a better project.


Daiane