Re: Toaster meeting notes (Dec 18th)

Re: Toaster meeting notes (Dec 18th)

[Damian, Alexandru]

[-- Attachment #1: Type: text/plain, Size: 7461 bytes --]

Hi David,

I got some comments below, I hope I got your questions right.

Cheers,
Alex


On Thu, Dec 19, 2013 at 9:28 AM, Reyna, David <david.reyna@windriver.com>wrote:

>  ------------------------------
>
>   Hi Alex,
>
>
>
> You had us originally pull against master, but your notes indicate that
> your updates are it not in master yet. How would we pull this
> intermediate content into our cloned installations? Do we indicate a
> specific branch? I am new to your process so I am trying not to guess :=) I
> very much want to replicate what you demonstrated before the break so that
> I can continue working on it, because we have of course little time after
> we return to make the M2 dates.
>

In your poky directory do:

# git remote add contrib http://git.yoctoproject.org/git/poky-contrib
# git checkout contrib/toaster/master -b toaster-master

This will get your local toaster-master branch in sync with the current
updates that are not in the master.
To start working on a new feature do:

# git checkout toaster-master -b new_feature_01012014

Commit all changes to this branch, and push it to contrib:

# git push contrib new_feature_01012014:dreyna/new_feature_01012014

And let us know that you pushed on the toaster@yoctoproject.org mailing
list (CCed in this email).



>
> Also, when you generally do a pull of the latest Toaster code, do you find
> that you need to rebuild your projects also? In other words, is there a way
> to just update the Toaster code with affecting the rest of the Poky
> installation, such that projects can be persistent?
>
>
> You can switch at any time between different branches of what you have on
your disk. Toaster is designed to not retrigger or interfere with what's
already built, i.e. will not affect the signatures or recipes or trigger
rebuilds.


>  I noticed that even though I had a built project, nothing came up in the
> toaster web view. I assume that this is because we had pulled the older
> code. Just in case, could you point me to were in the code the database
> picks up the available projects, in case I need to debug this while you are
> away on vacation?
>
>
> Toaster will only record builds that happen after you started it, i.e.
after launching "source toaster start". Any build ran without Toaster
running will not be recorded. Toaster doesn't search and integrate for
projects built prior to having it running.



>   Thanks!
>
> David
>


Hope this helps :)

Alex

>
>
> *From:* Damian, Alexandru [mailto:alexandru.damian@intel.com]
> *Sent:* Wednesday, December 18, 2013 3:11 PM
> *To:* Barros Pena, Belen
> *Cc:* Reyna, David; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul;
> Eggleton, Paul; Voicu, Cristiana
> *Subject:* Re: Toaster meeting notes (Dec 18th)
>
>
>
> Hi,
>
>
>
> I have pushed a new version of poky-contrib/toaster-master with:
>
> - the UI now lives in toastergui/ application, instead of advui/
>
> - the complete filters set-up for Builds landing page are now working,
>
> - new comments.
>
>
>
> This version will suffer a revision in the next couple of days to prepare
> it for integration into origin/master,
>
> but any work on top of it should be easily rebase-able after the revision.
>
>
>
> Cheers,
>
> Alex
>
>
>
> On Wed, Dec 18, 2013 at 7:27 PM, Barros Pena, Belen <
> belen.barros.pena@intel.com> wrote:
>
> Just a few notes from the meeting. If I have forgotten anything, please
> let em know.
>
> About the development and patch submission process
>
> * Alex will send around (through the Toaster mailing list) an stable base
> of toaster/master that can be used for development  (Paul would like to see
> development on top of master as soon as it is possible / manageable)
> * This base can then be forked for individual development work
> * Individual development branches can be pushed to the poky-contrib
> repository (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/),
> where they are public and can be seeing by the whole team
> * For the moment, we can use the Toaster mailing list to request review /
> comments of work in progress
> * Work in progress will then be merged to toaster/master, and a single
> pull request is sent out to the bitbake-devel mailing list to be merged to
> origin/master
> * Please remember to cc the Toaster mailing list on any emails we exchange
>
> What everybody needs:
>
> * Push access to poky-contrib (please contact Michael Halstead at
> michael@yoctoproject.org)
> * Open an account in the Yocto Project Bugzilla instance (
> https://bugzilla.yoctoproject.org/createaccount.cgi)
>
> Suggested front-end development tools: 2 Firefox extensions
>
> * Firebug (https://getfirebug.com/)
> * HtmlValidator (http://users.skynet.be/mgueury/mozilla/)
>
> Bugzilla features:
>
> These are the 3 features we identified as good next steps.
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4283
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4328
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4299
>
> I will set the status of all front-end Bugzilla features to "accepted".
> Once you have identified a feature you would like to work on, you can
> change the assignee to yourselves and change the status to "In progress
> implementation". If you have any questions about a feature, reach to Alex
> and Belén (via IRC or the Toaster mailing list).
>
> Our next meeting should be on January 8th.
>
> Have a great break!
>
> Belén
>
>
> From: david.reyna@windriver.com<mailto:david.reyna@windriver.com>
> When: 17:00 - 18:00 18 December 2013
> Subject: WebEx: toaster meeting
> Location: 1-800-730-2996x7494529#
>
>
> WebEx for the Toaster meeting.
>
>
>
>
> DAVID REYNA invites you to an online meeting using WebEx.
>
> Meeting Number: 591 835 399
> Meeting Password: This meeting does not require a password.
>
> -------------------------------------------------------
> To join this meeting (Now from mobile devices!)
> -------------------------------------------------------
> 1. Go to https://windriver.webex.com/windriver/j.php?J=591835399
> 2. If requested, enter your name and email address.
> 3. If a password is required, enter the meeting password: This meeting
> does not require a password.
> 4. Click "Join".
> 5. Follow the instructions that appear on your screen.
>
>
>
> -------------------------------------------------------
> Teleconference information
> -------------------------------------------------------
> Provide your phone number when you join the meeting to receive a call
> back. Alternatively, you can call:
> Conference dial-in number: 1-8007302996  (US)
> Access Code: 749 452 9
>
> http://www.webex.com
>
>
>
> IMPORTANT NOTICE: This WebEx service includes a feature that allows audio
> and any documents and other materials exchanged or viewed during the
> session to be recorded. By joining this session, you automatically consent
> to such recordings. If you do not consent to the recording, discuss your
> concerns with the meeting host prior to the start of the recording or do
> not join the session. Please note that any such recordings may be subject
> to discovery in the event of litigation.
>
>
>
>
>
> --
>
> Alex Damian
>
> Yocto Project
>
> SSG / OTC
>



-- 
Alex Damian
Yocto Project
SSG / OTC

[-- Attachment #2: Type: text/html, Size: 14471 bytes --]

Re: Toaster meeting notes (Dec 18th)

[Reyna, David]

[-- Attachment #1: Type: text/plain, Size: 8329 bytes --]

Hi Alex,

This is what I get:

  ~/toaster_1_6/poky$ git remote add contrib http://git.yoctoproject.org/git/poky-contrib
  ~/toaster_1_6/poky$ git checkout contrib/toaster/master -b toaster-master
  fatal: Cannot update paths and switch to branch 'toaster-master' at the same time.
  Did you intend to checkout 'contrib/toaster/master' which can not be resolved as commit?
  ~/toaster_1_6/poky

> Toaster will only record builds that happen after you started it, i.e. after launching "source toaster start".

Hmm. With my unregistered project, if I do a clean (on at least one package) and a rebuild, will I get the whole project, only the parts that updated, or do I have to create and build the entire project from scratch?

- David

From: Damian, Alexandru [mailto:alexandru.damian@intel.com]
Sent: Thursday, December 19, 2013 3:55 AM
To: Reyna, David; toaster@yoctoproject.org
Cc: Barros Pena, Belen; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul; Eggleton, Paul; Voicu, Cristiana
Subject: Re: Toaster meeting notes (Dec 18th)

Hi David,

I got some comments below, I hope I got your questions right.

Cheers,
Alex

On Thu, Dec 19, 2013 at 9:28 AM, Reyna, David <david.reyna@windriver.com<mailto:david.reyna@windriver.com>> wrote:
________________________________

Hi Alex,

You had us originally pull against master, but your notes indicate that your updates are it not in master yet. How would we pull this intermediate content into our cloned installations? Do we indicate a specific branch? I am new to your process so I am trying not to guess :=) I very much want to replicate what you demonstrated before the break so that I can continue working on it, because we have of course little time after we return to make the M2 dates.

In your poky directory do:

# git remote add contrib http://git.yoctoproject.org/git/poky-contrib
# git checkout contrib/toaster/master -b toaster-master

This will get your local toaster-master branch in sync with the current updates that are not in the master.
To start working on a new feature do:

# git checkout toaster-master -b new_feature_01012014

Commit all changes to this branch, and push it to contrib:

# git push contrib new_feature_01012014:dreyna/new_feature_01012014

And let us know that you pushed on the toaster@yoctoproject.org<mailto:toaster@yoctoproject.org> mailing list (CCed in this email).




Also, when you generally do a pull of the latest Toaster code, do you find that you need to rebuild your projects also? In other words, is there a way to just update the Toaster code with affecting the rest of the Poky installation, such that projects can be persistent?


You can switch at any time between different branches of what you have on your disk. Toaster is designed to not retrigger or interfere with what's already built, i.e. will not affect the signatures or recipes or trigger rebuilds.


I noticed that even though I had a built project, nothing came up in the toaster web view. I assume that this is because we had pulled the older code. Just in case, could you point me to were in the code the database picks up the available projects, in case I need to debug this while you are away on vacation?


Toaster will only record builds that happen after you started it, i.e. after launching "source toaster start". Any build ran without Toaster running will not be recorded. Toaster doesn't search and integrate for projects built prior to having it running.


Thanks!
David


Hope this helps :)

Alex

From: Damian, Alexandru [mailto:alexandru.damian@intel.com<mailto:alexandru.damian@intel.com>]
Sent: Wednesday, December 18, 2013 3:11 PM
To: Barros Pena, Belen
Cc: Reyna, David; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul; Eggleton, Paul; Voicu, Cristiana
Subject: Re: Toaster meeting notes (Dec 18th)

Hi,

I have pushed a new version of poky-contrib/toaster-master with:
- the UI now lives in toastergui/ application, instead of advui/
- the complete filters set-up for Builds landing page are now working,
- new comments.

This version will suffer a revision in the next couple of days to prepare it for integration into origin/master,
but any work on top of it should be easily rebase-able after the revision.

Cheers,
Alex

On Wed, Dec 18, 2013 at 7:27 PM, Barros Pena, Belen <belen.barros.pena@intel.com<mailto:belen.barros.pena@intel.com>> wrote:
Just a few notes from the meeting. If I have forgotten anything, please let em know.

About the development and patch submission process

* Alex will send around (through the Toaster mailing list) an stable base of toaster/master that can be used for development  (Paul would like to see development on top of master as soon as it is possible / manageable)
* This base can then be forked for individual development work
* Individual development branches can be pushed to the poky-contrib repository (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/), where they are public and can be seeing by the whole team
* For the moment, we can use the Toaster mailing list to request review / comments of work in progress
* Work in progress will then be merged to toaster/master, and a single pull request is sent out to the bitbake-devel mailing list to be merged to origin/master
* Please remember to cc the Toaster mailing list on any emails we exchange

What everybody needs:

* Push access to poky-contrib (please contact Michael Halstead at michael@yoctoproject.org<mailto:michael@yoctoproject.org>)
* Open an account in the Yocto Project Bugzilla instance (https://bugzilla.yoctoproject.org/createaccount.cgi)

Suggested front-end development tools: 2 Firefox extensions

* Firebug (https://getfirebug.com/)
* HtmlValidator (http://users.skynet.be/mgueury/mozilla/)

Bugzilla features:

These are the 3 features we identified as good next steps.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4283
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4328
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4299

I will set the status of all front-end Bugzilla features to "accepted". Once you have identified a feature you would like to work on, you can change the assignee to yourselves and change the status to "In progress implementation". If you have any questions about a feature, reach to Alex and Belén (via IRC or the Toaster mailing list).

Our next meeting should be on January 8th.

Have a great break!

Belén


From: david.reyna@windriver.com<mailto:david.reyna@windriver.com><mailto:david.reyna@windriver.com<mailto:david.reyna@windriver.com>>
When: 17:00 - 18:00 18 December 2013
Subject: WebEx: toaster meeting
Location: 1-800-730-2996x7494529#


WebEx for the Toaster meeting.




DAVID REYNA invites you to an online meeting using WebEx.

Meeting Number: 591 835 399
Meeting Password: This meeting does not require a password.

-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://windriver.webex.com/windriver/j.php?J=591835399
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: This meeting does not require a password.
4. Click "Join".
5. Follow the instructions that appear on your screen.



-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Provide your phone number when you join the meeting to receive a call back. Alternatively, you can call:
Conference dial-in number: 1-8007302996  (US)
Access Code: 749 452 9

http://www.webex.com



IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.



--
Alex Damian
Yocto Project
SSG / OTC



--
Alex Damian
Yocto Project
SSG / OTC

[-- Attachment #2: Type: text/html, Size: 23164 bytes --]

Re: Toaster meeting notes (Dec 18th)

[Lerner, Dave]

[-- Attachment #1: Type: text/plain, Size: 8764 bytes --]

Hi David, Alex

I get the same complaint that David gets.

- Dave

________________________________
From: toaster-bounces@yoctoproject.org [toaster-bounces@yoctoproject.org] on behalf of Reyna, David [david.reyna@windriver.com]
Sent: Thursday, December 19, 2013 6:09 AM
To: Damian, Alexandru; toaster@yoctoproject.org
Cc: Bansal, Atul; Zhang, Jessica; Eggleton, Paul
Subject: Re: [Toaster] Toaster meeting notes (Dec 18th)

Hi Alex,

This is what I get:

  ~/toaster_1_6/poky$ git remote add contrib http://git.yoctoproject.org/git/poky-contrib
  ~/toaster_1_6/poky$ git checkout contrib/toaster/master -b toaster-master
  fatal: Cannot update paths and switch to branch 'toaster-master' at the same time.
  Did you intend to checkout 'contrib/toaster/master' which can not be resolved as commit?
  ~/toaster_1_6/poky

> Toaster will only record builds that happen after you started it, i.e. after launching "source toaster start".

Hmm. With my unregistered project, if I do a clean (on at least one package) and a rebuild, will I get the whole project, only the parts that updated, or do I have to create and build the entire project from scratch?

- David

From: Damian, Alexandru [mailto:alexandru.damian@intel.com]
Sent: Thursday, December 19, 2013 3:55 AM
To: Reyna, David; toaster@yoctoproject.org
Cc: Barros Pena, Belen; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul; Eggleton, Paul; Voicu, Cristiana
Subject: Re: Toaster meeting notes (Dec 18th)

Hi David,

I got some comments below, I hope I got your questions right.

Cheers,
Alex

On Thu, Dec 19, 2013 at 9:28 AM, Reyna, David <david.reyna@windriver.com<mailto:david.reyna@windriver.com>> wrote:
________________________________

Hi Alex,

You had us originally pull against master, but your notes indicate that your updates are it not in master yet. How would we pull this intermediate content into our cloned installations? Do we indicate a specific branch? I am new to your process so I am trying not to guess :=) I very much want to replicate what you demonstrated before the break so that I can continue working on it, because we have of course little time after we return to make the M2 dates.

In your poky directory do:

# git remote add contrib http://git.yoctoproject.org/git/poky-contrib
# git checkout contrib/toaster/master -b toaster-master

This will get your local toaster-master branch in sync with the current updates that are not in the master.
To start working on a new feature do:

# git checkout toaster-master -b new_feature_01012014

Commit all changes to this branch, and push it to contrib:

# git push contrib new_feature_01012014:dreyna/new_feature_01012014

And let us know that you pushed on the toaster@yoctoproject.org<mailto:toaster@yoctoproject.org> mailing list (CCed in this email).




Also, when you generally do a pull of the latest Toaster code, do you find that you need to rebuild your projects also? In other words, is there a way to just update the Toaster code with affecting the rest of the Poky installation, such that projects can be persistent?


You can switch at any time between different branches of what you have on your disk. Toaster is designed to not retrigger or interfere with what's already built, i.e. will not affect the signatures or recipes or trigger rebuilds.


I noticed that even though I had a built project, nothing came up in the toaster web view. I assume that this is because we had pulled the older code. Just in case, could you point me to were in the code the database picks up the available projects, in case I need to debug this while you are away on vacation?


Toaster will only record builds that happen after you started it, i.e. after launching "source toaster start". Any build ran without Toaster running will not be recorded. Toaster doesn't search and integrate for projects built prior to having it running.


Thanks!
David


Hope this helps :)

Alex

From: Damian, Alexandru [mailto:alexandru.damian@intel.com<mailto:alexandru.damian@intel.com>]
Sent: Wednesday, December 18, 2013 3:11 PM
To: Barros Pena, Belen
Cc: Reyna, David; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul; Eggleton, Paul; Voicu, Cristiana
Subject: Re: Toaster meeting notes (Dec 18th)

Hi,

I have pushed a new version of poky-contrib/toaster-master with:
- the UI now lives in toastergui/ application, instead of advui/
- the complete filters set-up for Builds landing page are now working,
- new comments.

This version will suffer a revision in the next couple of days to prepare it for integration into origin/master,
but any work on top of it should be easily rebase-able after the revision.

Cheers,
Alex

On Wed, Dec 18, 2013 at 7:27 PM, Barros Pena, Belen <belen.barros.pena@intel.com<mailto:belen.barros.pena@intel.com>> wrote:
Just a few notes from the meeting. If I have forgotten anything, please let em know.

About the development and patch submission process

* Alex will send around (through the Toaster mailing list) an stable base of toaster/master that can be used for development  (Paul would like to see development on top of master as soon as it is possible / manageable)
* This base can then be forked for individual development work
* Individual development branches can be pushed to the poky-contrib repository (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/), where they are public and can be seeing by the whole team
* For the moment, we can use the Toaster mailing list to request review / comments of work in progress
* Work in progress will then be merged to toaster/master, and a single pull request is sent out to the bitbake-devel mailing list to be merged to origin/master
* Please remember to cc the Toaster mailing list on any emails we exchange

What everybody needs:

* Push access to poky-contrib (please contact Michael Halstead at michael@yoctoproject.org<mailto:michael@yoctoproject.org>)
* Open an account in the Yocto Project Bugzilla instance (https://bugzilla.yoctoproject.org/createaccount.cgi)

Suggested front-end development tools: 2 Firefox extensions

* Firebug (https://getfirebug.com/)
* HtmlValidator (http://users.skynet.be/mgueury/mozilla/)

Bugzilla features:

These are the 3 features we identified as good next steps.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4283
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4328
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4299

I will set the status of all front-end Bugzilla features to "accepted". Once you have identified a feature you would like to work on, you can change the assignee to yourselves and change the status to "In progress implementation". If you have any questions about a feature, reach to Alex and Belén (via IRC or the Toaster mailing list).

Our next meeting should be on January 8th.

Have a great break!

Belén


From: david.reyna@windriver.com<mailto:david.reyna@windriver.com><mailto:david.reyna@windriver.com<mailto:david.reyna@windriver.com>>
When: 17:00 - 18:00 18 December 2013
Subject: WebEx: toaster meeting
Location: 1-800-730-2996x7494529#


WebEx for the Toaster meeting.




DAVID REYNA invites you to an online meeting using WebEx.

Meeting Number: 591 835 399
Meeting Password: This meeting does not require a password.

-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://windriver.webex.com/windriver/j.php?J=591835399
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: This meeting does not require a password.
4. Click "Join".
5. Follow the instructions that appear on your screen.



-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Provide your phone number when you join the meeting to receive a call back. Alternatively, you can call:
Conference dial-in number: 1-8007302996  (US)
Access Code: 749 452 9

http://www.webex.com



IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.



--
Alex Damian
Yocto Project
SSG / OTC



--
Alex Damian
Yocto Project
SSG / OTC

[-- Attachment #2: Type: text/html, Size: 20461 bytes --]

Re: Toaster meeting notes (Dec 18th)

[Paul Eggleton]

Hi folks,

I think you need to do the following before the git checkout:

  git fetch contrib

Cheers,
Paul

On Friday 20 December 2013 13:16:05 Lerner, Dave wrote:
> Hi David, Alex
> 
> I get the same complaint that David gets.
> 
> - Dave
> 
> ________________________________
> From: toaster-bounces@yoctoproject.org [toaster-bounces@yoctoproject.org] on
> behalf of Reyna, David [david.reyna@windriver.com] Sent: Thursday, December
> 19, 2013 6:09 AM
> To: Damian, Alexandru; toaster@yoctoproject.org
> Cc: Bansal, Atul; Zhang, Jessica; Eggleton, Paul
> Subject: Re: [Toaster] Toaster meeting notes (Dec 18th)
> 
> Hi Alex,
> 
> This is what I get:
> 
>   ~/toaster_1_6/poky$ git remote add contrib
> http://git.yoctoproject.org/git/poky-contrib ~/toaster_1_6/poky$ git
> checkout contrib/toaster/master -b toaster-master fatal: Cannot update
> paths and switch to branch 'toaster-master' at the same time. Did you
> intend to checkout 'contrib/toaster/master' which can not be resolved as
> commit? ~/toaster_1_6/poky
> 
> > Toaster will only record builds that happen after you started it, i.e.
> > after launching "source toaster start".
> Hmm. With my unregistered project, if I do a clean (on at least one package)
> and a rebuild, will I get the whole project, only the parts that updated,
> or do I have to create and build the entire project from scratch?
> 
> - David
> 
> From: Damian, Alexandru [mailto:alexandru.damian@intel.com]
> Sent: Thursday, December 19, 2013 3:55 AM
> To: Reyna, David; toaster@yoctoproject.org
> Cc: Barros Pena, Belen; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul;
> Eggleton, Paul; Voicu, Cristiana Subject: Re: Toaster meeting notes (Dec
> 18th)
> 
> Hi David,
> 
> I got some comments below, I hope I got your questions right.
> 
> Cheers,
> Alex
> 
> On Thu, Dec 19, 2013 at 9:28 AM, Reyna, David
> <david.reyna@windriver.com<mailto:david.reyna@windriver.com>> wrote:
> ________________________________
> 
> Hi Alex,
> 
> You had us originally pull against master, but your notes indicate that your
> updates are it not in master yet. How would we pull this intermediate
> content into our cloned installations? Do we indicate a specific branch? I
> am new to your process so I am trying not to guess :=) I very much want to
> replicate what you demonstrated before the break so that I can continue
> working on it, because we have of course little time after we return to
> make the M2 dates.
> 
> In your poky directory do:
> 
> # git remote add contrib http://git.yoctoproject.org/git/poky-contrib
> # git checkout contrib/toaster/master -b toaster-master
> 
> This will get your local toaster-master branch in sync with the current
> updates that are not in the master. To start working on a new feature do:
> 
> # git checkout toaster-master -b new_feature_01012014
> 
> Commit all changes to this branch, and push it to contrib:
> 
> # git push contrib new_feature_01012014:dreyna/new_feature_01012014
> 
> And let us know that you pushed on the
> toaster@yoctoproject.org<mailto:toaster@yoctoproject.org> mailing list
> (CCed in this email).
> 
> 
> 
> 
> Also, when you generally do a pull of the latest Toaster code, do you find
> that you need to rebuild your projects also? In other words, is there a way
> to just update the Toaster code with affecting the rest of the Poky
> installation, such that projects can be persistent?
> 
> 
> You can switch at any time between different branches of what you have on
> your disk. Toaster is designed to not retrigger or interfere with what's
> already built, i.e. will not affect the signatures or recipes or trigger
> rebuilds.
> 
> 
> I noticed that even though I had a built project, nothing came up in the
> toaster web view. I assume that this is because we had pulled the older
> code. Just in case, could you point me to were in the code the database
> picks up the available projects, in case I need to debug this while you are
> away on vacation?
> 
> 
> Toaster will only record builds that happen after you started it, i.e. after
> launching "source toaster start". Any build ran without Toaster running
> will not be recorded. Toaster doesn't search and integrate for projects
> built prior to having it running.
> 
> 
> Thanks!
> David
> 
> 
> Hope this helps :)
> 
> Alex
> 
> From: Damian, Alexandru
> [mailto:alexandru.damian@intel.com<mailto:alexandru.damian@intel.com>]
> Sent: Wednesday, December 18, 2013 3:11 PM
> To: Barros Pena, Belen
> Cc: Reyna, David; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul; Eggleton,
> Paul; Voicu, Cristiana Subject: Re: Toaster meeting notes (Dec 18th)
> 
> Hi,
> 
> I have pushed a new version of poky-contrib/toaster-master with:
> - the UI now lives in toastergui/ application, instead of advui/
> - the complete filters set-up for Builds landing page are now working,
> - new comments.
> 
> This version will suffer a revision in the next couple of days to prepare it
> for integration into origin/master, but any work on top of it should be
> easily rebase-able after the revision.
> 
> Cheers,
> Alex
> 
> On Wed, Dec 18, 2013 at 7:27 PM, Barros Pena, Belen
> <belen.barros.pena@intel.com<mailto:belen.barros.pena@intel.com>> wrote:
> Just a few notes from the meeting. If I have forgotten anything, please let
> em know.
> 
> About the development and patch submission process
> 
> * Alex will send around (through the Toaster mailing list) an stable base of
> toaster/master that can be used for development  (Paul would like to see
> development on top of master as soon as it is possible / manageable) * This
> base can then be forked for individual development work
> * Individual development branches can be pushed to the poky-contrib
> repository (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/), where
> they are public and can be seeing by the whole team * For the moment, we
> can use the Toaster mailing list to request review / comments of work in
> progress * Work in progress will then be merged to toaster/master, and a
> single pull request is sent out to the bitbake-devel mailing list to be
> merged to origin/master * Please remember to cc the Toaster mailing list on
> any emails we exchange
> 
> What everybody needs:
> 
> * Push access to poky-contrib (please contact Michael Halstead at
> michael@yoctoproject.org<mailto:michael@yoctoproject.org>) * Open an
> account in the Yocto Project Bugzilla instance
> (https://bugzilla.yoctoproject.org/createaccount.cgi)
> 
> Suggested front-end development tools: 2 Firefox extensions
> 
> * Firebug (https://getfirebug.com/)
> * HtmlValidator (http://users.skynet.be/mgueury/mozilla/)
> 
> Bugzilla features:
> 
> These are the 3 features we identified as good next steps.
> 
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4283
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4328
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4299
> 
> I will set the status of all front-end Bugzilla features to "accepted". Once
> you have identified a feature you would like to work on, you can change the
> assignee to yourselves and change the status to "In progress
> implementation". If you have any questions about a feature, reach to Alex
> and Belén (via IRC or the Toaster mailing list).
> 
> Our next meeting should be on January 8th.
> 
> Have a great break!
> 
> Belén
> 
> 
> From:
> david.reyna@windriver.com<mailto:david.reyna@windriver.com><mailto:david.re
> yna@windriver.com<mailto:david.reyna@windriver.com>> When: 17:00 - 18:00 18
> December 2013
> Subject: WebEx: toaster meeting
> Location: 1-800-730-2996x7494529#
> 
> 
> WebEx for the Toaster meeting.
> 
> 
> 
> 
> DAVID REYNA invites you to an online meeting using WebEx.
> 
> Meeting Number: 591 835 399
> Meeting Password: This meeting does not require a password.
> 
> -------------------------------------------------------
> To join this meeting (Now from mobile devices!)
> -------------------------------------------------------
> 1. Go to https://windriver.webex.com/windriver/j.php?J=591835399
> 2. If requested, enter your name and email address.
> 3. If a password is required, enter the meeting password: This meeting does
> not require a password. 4. Click "Join".
> 5. Follow the instructions that appear on your screen.
> 
> 
> 
> -------------------------------------------------------
> Teleconference information
> -------------------------------------------------------
> Provide your phone number when you join the meeting to receive a call back.
> Alternatively, you can call: Conference dial-in number: 1-8007302996  (US)
> Access Code: 749 452 9
> 
> http://www.webex.com
> 
> 
> 
> IMPORTANT NOTICE: This WebEx service includes a feature that allows audio
> and any documents and other materials exchanged or viewed during the
> session to be recorded. By joining this session, you automatically consent
> to such recordings. If you do not consent to the recording, discuss your
> concerns with the meeting host prior to the start of the recording or do
> not join the session. Please note that any such recordings may be subject
> to discovery in the event of litigation.
> 
> 
> 
> --
> Alex Damian
> Yocto Project
> SSG / OTC
> 
> 
> 
> --
> Alex Damian
> Yocto Project
> SSG / OTC
---------------------------------------------------------------------
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.

Re: Toaster meeting notes (Dec 18th)

[Damian, Alexandru]

[-- Attachment #1: Type: text/plain, Size: 10726 bytes --]

Thank you Paul, I've been trying to realize what's going on, and I didn't
get it :(

Alex


On Fri, Dec 20, 2013 at 1:43 PM, Paul Eggleton <paul.eggleton@intel.com>wrote:

> Hi folks,
>
> I think you need to do the following before the git checkout:
>
>   git fetch contrib
>
> Cheers,
> Paul
>
> On Friday 20 December 2013 13:16:05 Lerner, Dave wrote:
> > Hi David, Alex
> >
> > I get the same complaint that David gets.
> >
> > - Dave
> >
> > ________________________________
> > From: toaster-bounces@yoctoproject.org [toaster-bounces@yoctoproject.org]
> on
> > behalf of Reyna, David [david.reyna@windriver.com] Sent: Thursday,
> December
> > 19, 2013 6:09 AM
> > To: Damian, Alexandru; toaster@yoctoproject.org
> > Cc: Bansal, Atul; Zhang, Jessica; Eggleton, Paul
> > Subject: Re: [Toaster] Toaster meeting notes (Dec 18th)
> >
> > Hi Alex,
> >
> > This is what I get:
> >
> >   ~/toaster_1_6/poky$ git remote add contrib
> > http://git.yoctoproject.org/git/poky-contrib ~/toaster_1_6/poky$ git
> > checkout contrib/toaster/master -b toaster-master fatal: Cannot update
> > paths and switch to branch 'toaster-master' at the same time. Did you
> > intend to checkout 'contrib/toaster/master' which can not be resolved as
> > commit? ~/toaster_1_6/poky
> >
> > > Toaster will only record builds that happen after you started it, i.e.
> > > after launching "source toaster start".
> > Hmm. With my unregistered project, if I do a clean (on at least one
> package)
> > and a rebuild, will I get the whole project, only the parts that updated,
> > or do I have to create and build the entire project from scratch?
> >
> > - David
> >
> > From: Damian, Alexandru [mailto:alexandru.damian@intel.com]
> > Sent: Thursday, December 19, 2013 3:55 AM
> > To: Reyna, David; toaster@yoctoproject.org
> > Cc: Barros Pena, Belen; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul;
> > Eggleton, Paul; Voicu, Cristiana Subject: Re: Toaster meeting notes (Dec
> > 18th)
> >
> > Hi David,
> >
> > I got some comments below, I hope I got your questions right.
> >
> > Cheers,
> > Alex
> >
> > On Thu, Dec 19, 2013 at 9:28 AM, Reyna, David
> > <david.reyna@windriver.com<mailto:david.reyna@windriver.com>> wrote:
> > ________________________________
> >
> > Hi Alex,
> >
> > You had us originally pull against master, but your notes indicate that
> your
> > updates are it not in master yet. How would we pull this intermediate
> > content into our cloned installations? Do we indicate a specific branch?
> I
> > am new to your process so I am trying not to guess :=) I very much want
> to
> > replicate what you demonstrated before the break so that I can continue
> > working on it, because we have of course little time after we return to
> > make the M2 dates.
> >
> > In your poky directory do:
> >
> > # git remote add contrib http://git.yoctoproject.org/git/poky-contrib
> > # git checkout contrib/toaster/master -b toaster-master
> >
> > This will get your local toaster-master branch in sync with the current
> > updates that are not in the master. To start working on a new feature do:
> >
> > # git checkout toaster-master -b new_feature_01012014
> >
> > Commit all changes to this branch, and push it to contrib:
> >
> > # git push contrib new_feature_01012014:dreyna/new_feature_01012014
> >
> > And let us know that you pushed on the
> > toaster@yoctoproject.org<mailto:toaster@yoctoproject.org> mailing list
> > (CCed in this email).
> >
> >
> >
> >
> > Also, when you generally do a pull of the latest Toaster code, do you
> find
> > that you need to rebuild your projects also? In other words, is there a
> way
> > to just update the Toaster code with affecting the rest of the Poky
> > installation, such that projects can be persistent?
> >
> >
> > You can switch at any time between different branches of what you have on
> > your disk. Toaster is designed to not retrigger or interfere with what's
> > already built, i.e. will not affect the signatures or recipes or trigger
> > rebuilds.
> >
> >
> > I noticed that even though I had a built project, nothing came up in the
> > toaster web view. I assume that this is because we had pulled the older
> > code. Just in case, could you point me to were in the code the database
> > picks up the available projects, in case I need to debug this while you
> are
> > away on vacation?
> >
> >
> > Toaster will only record builds that happen after you started it, i.e.
> after
> > launching "source toaster start". Any build ran without Toaster running
> > will not be recorded. Toaster doesn't search and integrate for projects
> > built prior to having it running.
> >
> >
> > Thanks!
> > David
> >
> >
> > Hope this helps :)
> >
> > Alex
> >
> > From: Damian, Alexandru
> > [mailto:alexandru.damian@intel.com<mailto:alexandru.damian@intel.com>]
> > Sent: Wednesday, December 18, 2013 3:11 PM
> > To: Barros Pena, Belen
> > Cc: Reyna, David; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul;
> Eggleton,
> > Paul; Voicu, Cristiana Subject: Re: Toaster meeting notes (Dec 18th)
> >
> > Hi,
> >
> > I have pushed a new version of poky-contrib/toaster-master with:
> > - the UI now lives in toastergui/ application, instead of advui/
> > - the complete filters set-up for Builds landing page are now working,
> > - new comments.
> >
> > This version will suffer a revision in the next couple of days to
> prepare it
> > for integration into origin/master, but any work on top of it should be
> > easily rebase-able after the revision.
> >
> > Cheers,
> > Alex
> >
> > On Wed, Dec 18, 2013 at 7:27 PM, Barros Pena, Belen
> > <belen.barros.pena@intel.com<mailto:belen.barros.pena@intel.com>> wrote:
> > Just a few notes from the meeting. If I have forgotten anything, please
> let
> > em know.
> >
> > About the development and patch submission process
> >
> > * Alex will send around (through the Toaster mailing list) an stable
> base of
> > toaster/master that can be used for development  (Paul would like to see
> > development on top of master as soon as it is possible / manageable) *
> This
> > base can then be forked for individual development work
> > * Individual development branches can be pushed to the poky-contrib
> > repository (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/),
> where
> > they are public and can be seeing by the whole team * For the moment, we
> > can use the Toaster mailing list to request review / comments of work in
> > progress * Work in progress will then be merged to toaster/master, and a
> > single pull request is sent out to the bitbake-devel mailing list to be
> > merged to origin/master * Please remember to cc the Toaster mailing list
> on
> > any emails we exchange
> >
> > What everybody needs:
> >
> > * Push access to poky-contrib (please contact Michael Halstead at
> > michael@yoctoproject.org<mailto:michael@yoctoproject.org>) * Open an
> > account in the Yocto Project Bugzilla instance
> > (https://bugzilla.yoctoproject.org/createaccount.cgi)
> >
> > Suggested front-end development tools: 2 Firefox extensions
> >
> > * Firebug (https://getfirebug.com/)
> > * HtmlValidator (http://users.skynet.be/mgueury/mozilla/)
> >
> > Bugzilla features:
> >
> > These are the 3 features we identified as good next steps.
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=4283
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=4328
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=4299
> >
> > I will set the status of all front-end Bugzilla features to "accepted".
> Once
> > you have identified a feature you would like to work on, you can change
> the
> > assignee to yourselves and change the status to "In progress
> > implementation". If you have any questions about a feature, reach to Alex
> > and Belén (via IRC or the Toaster mailing list).
> >
> > Our next meeting should be on January 8th.
> >
> > Have a great break!
> >
> > Belén
> >
> >
> > From:
> > david.reyna@windriver.com<mailto:david.reyna@windriver.com><mailto:
> david.re
> > yna@windriver.com<mailto:david.reyna@windriver.com>> When: 17:00 -
> 18:00 18
> > December 2013
> > Subject: WebEx: toaster meeting
> > Location: 1-800-730-2996x7494529#
> >
> >
> > WebEx for the Toaster meeting.
> >
> >
> >
> >
> > DAVID REYNA invites you to an online meeting using WebEx.
> >
> > Meeting Number: 591 835 399
> > Meeting Password: This meeting does not require a password.
> >
> > -------------------------------------------------------
> > To join this meeting (Now from mobile devices!)
> > -------------------------------------------------------
> > 1. Go to https://windriver.webex.com/windriver/j.php?J=591835399
> > 2. If requested, enter your name and email address.
> > 3. If a password is required, enter the meeting password: This meeting
> does
> > not require a password. 4. Click "Join".
> > 5. Follow the instructions that appear on your screen.
> >
> >
> >
> > -------------------------------------------------------
> > Teleconference information
> > -------------------------------------------------------
> > Provide your phone number when you join the meeting to receive a call
> back.
> > Alternatively, you can call: Conference dial-in number: 1-8007302996
>  (US)
> > Access Code: 749 452 9
> >
> > http://www.webex.com
> >
> >
> >
> > IMPORTANT NOTICE: This WebEx service includes a feature that allows audio
> > and any documents and other materials exchanged or viewed during the
> > session to be recorded. By joining this session, you automatically
> consent
> > to such recordings. If you do not consent to the recording, discuss your
> > concerns with the meeting host prior to the start of the recording or do
> > not join the session. Please note that any such recordings may be subject
> > to discovery in the event of litigation.
> >
> >
> >
> > --
> > Alex Damian
> > Yocto Project
> > SSG / OTC
> >
> >
> >
> > --
> > Alex Damian
> > Yocto Project
> > SSG / OTC
> ---------------------------------------------------------------------
> 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.
>
>


-- 
Alex Damian
Yocto Project
SSG / OTC

[-- Attachment #2: Type: text/html, Size: 14488 bytes --]

Re: Toaster meeting notes (Dec 18th)

[Reyna, David]

Hi Paul,

Both Dave and I can confirm that your additional step works!

Thanks,
David

> -----Original Message-----
> From: Paul Eggleton [mailto:paul.eggleton@intel.com]
> Sent: Friday, December 20, 2013 5:44 AM
> To: Lerner, Dave; Reyna, David
> Cc: Damian, Alexandru; toaster@yoctoproject.org; Bansal, Atul; Zhang,
> Jessica
> Subject: Re: Toaster meeting notes (Dec 18th)
> 
> Hi folks,
> 
> I think you need to do the following before the git checkout:
> 
>   git fetch contrib
> 
> Cheers,
> Paul
> 
> On Friday 20 December 2013 13:16:05 Lerner, Dave wrote:
> > Hi David, Alex
> >
> > I get the same complaint that David gets.
> >
> > - Dave
> >
> > ________________________________
> > From: toaster-bounces@yoctoproject.org [toaster-
> bounces@yoctoproject.org] on
> > behalf of Reyna, David [david.reyna@windriver.com] Sent: Thursday,
> December
> > 19, 2013 6:09 AM
> > To: Damian, Alexandru; toaster@yoctoproject.org
> > Cc: Bansal, Atul; Zhang, Jessica; Eggleton, Paul
> > Subject: Re: [Toaster] Toaster meeting notes (Dec 18th)
> >
> > Hi Alex,
> >
> > This is what I get:
> >
> >   ~/toaster_1_6/poky$ git remote add contrib
> > http://git.yoctoproject.org/git/poky-contrib ~/toaster_1_6/poky$ git
> > checkout contrib/toaster/master -b toaster-master fatal: Cannot
> update
> > paths and switch to branch 'toaster-master' at the same time. Did you
> > intend to checkout 'contrib/toaster/master' which can not be resolved
> as
> > commit? ~/toaster_1_6/poky
> >
> > > Toaster will only record builds that happen after you started it,
> i.e.
> > > after launching "source toaster start".
> > Hmm. With my unregistered project, if I do a clean (on at least one
> package)
> > and a rebuild, will I get the whole project, only the parts that
> updated,
> > or do I have to create and build the entire project from scratch?
> >
> > - David
> >
> > From: Damian, Alexandru [mailto:alexandru.damian@intel.com]
> > Sent: Thursday, December 19, 2013 3:55 AM
> > To: Reyna, David; toaster@yoctoproject.org
> > Cc: Barros Pena, Belen; Zhang, Jessica; Ravi Chintakunta; Bansal,
> Atul;
> > Eggleton, Paul; Voicu, Cristiana Subject: Re: Toaster meeting notes
> (Dec
> > 18th)
> >
> > Hi David,
> >
> > I got some comments below, I hope I got your questions right.
> >
> > Cheers,
> > Alex
> >
> > On Thu, Dec 19, 2013 at 9:28 AM, Reyna, David
> > <david.reyna@windriver.com<mailto:david.reyna@windriver.com>> wrote:
> > ________________________________
> >
> > Hi Alex,
> >
> > You had us originally pull against master, but your notes indicate
> that your
> > updates are it not in master yet. How would we pull this intermediate
> > content into our cloned installations? Do we indicate a specific
> branch? I
> > am new to your process so I am trying not to guess :=) I very much
> want to
> > replicate what you demonstrated before the break so that I can
> continue
> > working on it, because we have of course little time after we return
> to
> > make the M2 dates.
> >
> > In your poky directory do:
> >
> > # git remote add contrib http://git.yoctoproject.org/git/poky-contrib
> > # git checkout contrib/toaster/master -b toaster-master
> >
> > This will get your local toaster-master branch in sync with the
> current
> > updates that are not in the master. To start working on a new feature
> do:
> >
> > # git checkout toaster-master -b new_feature_01012014
> >
> > Commit all changes to this branch, and push it to contrib:
> >
> > # git push contrib new_feature_01012014:dreyna/new_feature_01012014
> >
> > And let us know that you pushed on the
> > toaster@yoctoproject.org<mailto:toaster@yoctoproject.org> mailing
> list
> > (CCed in this email).
> >
> >
> >
> >
> > Also, when you generally do a pull of the latest Toaster code, do you
> find
> > that you need to rebuild your projects also? In other words, is there
> a way
> > to just update the Toaster code with affecting the rest of the Poky
> > installation, such that projects can be persistent?
> >
> >
> > You can switch at any time between different branches of what you
> have on
> > your disk. Toaster is designed to not retrigger or interfere with
> what's
> > already built, i.e. will not affect the signatures or recipes or
> trigger
> > rebuilds.
> >
> >
> > I noticed that even though I had a built project, nothing came up in
> the
> > toaster web view. I assume that this is because we had pulled the
> older
> > code. Just in case, could you point me to were in the code the
> database
> > picks up the available projects, in case I need to debug this while
> you are
> > away on vacation?
> >
> >
> > Toaster will only record builds that happen after you started it,
> i.e. after
> > launching "source toaster start". Any build ran without Toaster
> running
> > will not be recorded. Toaster doesn't search and integrate for
> projects
> > built prior to having it running.
> >
> >
> > Thanks!
> > David
> >
> >
> > Hope this helps :)
> >
> > Alex
> >
> > From: Damian, Alexandru
> >
> [mailto:alexandru.damian@intel.com<mailto:alexandru.damian@intel.com>]
> > Sent: Wednesday, December 18, 2013 3:11 PM
> > To: Barros Pena, Belen
> > Cc: Reyna, David; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul;
> Eggleton,
> > Paul; Voicu, Cristiana Subject: Re: Toaster meeting notes (Dec 18th)
> >
> > Hi,
> >
> > I have pushed a new version of poky-contrib/toaster-master with:
> > - the UI now lives in toastergui/ application, instead of advui/
> > - the complete filters set-up for Builds landing page are now
> working,
> > - new comments.
> >
> > This version will suffer a revision in the next couple of days to
> prepare it
> > for integration into origin/master, but any work on top of it should
> be
> > easily rebase-able after the revision.
> >
> > Cheers,
> > Alex
> >
> > On Wed, Dec 18, 2013 at 7:27 PM, Barros Pena, Belen
> > <belen.barros.pena@intel.com<mailto:belen.barros.pena@intel.com>>
> wrote:
> > Just a few notes from the meeting. If I have forgotten anything,
> please let
> > em know.
> >
> > About the development and patch submission process
> >
> > * Alex will send around (through the Toaster mailing list) an stable
> base of
> > toaster/master that can be used for development  (Paul would like to
> see
> > development on top of master as soon as it is possible / manageable)
> * This
> > base can then be forked for individual development work
> > * Individual development branches can be pushed to the poky-contrib
> > repository (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/),
> where
> > they are public and can be seeing by the whole team * For the moment,
> we
> > can use the Toaster mailing list to request review / comments of work
> in
> > progress * Work in progress will then be merged to toaster/master,
> and a
> > single pull request is sent out to the bitbake-devel mailing list to
> be
> > merged to origin/master * Please remember to cc the Toaster mailing
> list on
> > any emails we exchange
> >
> > What everybody needs:
> >
> > * Push access to poky-contrib (please contact Michael Halstead at
> > michael@yoctoproject.org<mailto:michael@yoctoproject.org>) * Open an
> > account in the Yocto Project Bugzilla instance
> > (https://bugzilla.yoctoproject.org/createaccount.cgi)
> >
> > Suggested front-end development tools: 2 Firefox extensions
> >
> > * Firebug (https://getfirebug.com/)
> > * HtmlValidator (http://users.skynet.be/mgueury/mozilla/)
> >
> > Bugzilla features:
> >
> > These are the 3 features we identified as good next steps.
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=4283
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=4328
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=4299
> >
> > I will set the status of all front-end Bugzilla features to
> "accepted". Once
> > you have identified a feature you would like to work on, you can
> change the
> > assignee to yourselves and change the status to "In progress
> > implementation". If you have any questions about a feature, reach to
> Alex
> > and Belén (via IRC or the Toaster mailing list).
> >
> > Our next meeting should be on January 8th.
> >
> > Have a great break!
> >
> > Belén
> >
> >
> > From:
> >
> david.reyna@windriver.com<mailto:david.reyna@windriver.com><mailto:davi
> d.re
> > yna@windriver.com<mailto:david.reyna@windriver.com>> When: 17:00 -
> 18:00 18
> > December 2013
> > Subject: WebEx: toaster meeting
> > Location: 1-800-730-2996x7494529#
> >
> >
> > WebEx for the Toaster meeting.
> >
> >
> >
> >
> > DAVID REYNA invites you to an online meeting using WebEx.
> >
> > Meeting Number: 591 835 399
> > Meeting Password: This meeting does not require a password.
> >
> > -------------------------------------------------------
> > To join this meeting (Now from mobile devices!)
> > -------------------------------------------------------
> > 1. Go to https://windriver.webex.com/windriver/j.php?J=591835399
> > 2. If requested, enter your name and email address.
> > 3. If a password is required, enter the meeting password: This
> meeting does
> > not require a password. 4. Click "Join".
> > 5. Follow the instructions that appear on your screen.
> >
> >
> >
> > -------------------------------------------------------
> > Teleconference information
> > -------------------------------------------------------
> > Provide your phone number when you join the meeting to receive a call
> back.
> > Alternatively, you can call: Conference dial-in number: 1-8007302996
> (US)
> > Access Code: 749 452 9
> >
> > http://www.webex.com
> >
> >
> >
> > IMPORTANT NOTICE: This WebEx service includes a feature that allows
> audio
> > and any documents and other materials exchanged or viewed during the
> > session to be recorded. By joining this session, you automatically
> consent
> > to such recordings. If you do not consent to the recording, discuss
> your
> > concerns with the meeting host prior to the start of the recording or
> do
> > not join the session. Please note that any such recordings may be
> subject
> > to discovery in the event of litigation.
> >
> >
> >
> > --
> > Alex Damian
> > Yocto Project
> > SSG / OTC
> >
> >
> >
> > --
> > Alex Damian
> > Yocto Project
> > SSG / OTC
> ---------------------------------------------------------------------
> 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.

git push to poky-contrib/ravi

[Ravi Chintakunta]

I got push access from Michael and pushed a small commit to ravi/all-tasks-feature branch. 

Just a few notes to help others with the first push.

1. Changing the branch name: 
============================
It is good to have the same name for the local branch and the remote branch. If your local branch name is not in the form <yourname>/<branch name> you can rename your current branch by:

git branch -m <yourname>/<branch name>


2. Changing the remote url:
===========================
When you setup your development environment, you would have cloned from a http url like http://git.yoctoproject.org/git/poky-contrib. You will not be able to push to this url and you will get an error like this:

fatal: unable to access 'http://git.yoctoproject.org/git/poky-contrib/': The requested URL returned error: 403


You have to edit the remote url, by first checking the remote alias and url, and then changing the url.

You can view the remote aliases and the url by:

git remote --verbose

>>> This is the output on my machine:
contrib http://git.yoctoproject.org/git/poky-contrib (fetch)
contrib http://git.yoctoproject.org/git/poky-contrib (push)

** Note contrib is my remote alias for poky-contrib


For push, you have to change the url to git@git.yoctoproject.org:poky-contrib 

You can change the url by:

git remote set-url contrib git@git.yoctoproject.org:poky-contrib


After that you will able to push by:

git push contrib <yourname>/<branch name>


Thanks,
Ravi

all tasks

[Ravi Chintakunta]

I have pushed the "All tasks" code to ravi/all-tasks-feature branch.  This is still work in progress and I have pushed it for your review.

The push includes the all-tasks page and these enhancements to the basetable:

- Display the table column header as a link only if it is sortable
- Indicate the sort order as a up/down icon next to the column header

I have a few questions:

1. The UI design indicates filtering on Order, Executed, Outcome and Cache Attempt columns. What are the filtering options for these columns?

2. Is it correct to display the sstate_result for Cache Attempt?

3. Should the Task log be a link to the file, and if so should the log be opened in the browser or compressed and shown as a download.  

Thanks,
Ravi

Re: all tasks

[Reyna, David]

Hi Ravi, 

My two cents below...

> -----Original Message-----
> From: Ravi Chintakunta [mailto:ravi.chintakunta@timesys.com]
> Sent: Friday, January 10, 2014 3:44 PM
> To: Reyna, David; Lerner, Dave; 'Damian, Alexandru'; 'Barros Pena,
> Belen'; 'Zhang, Jessica'; Bansal, Atul
> Cc: 'toaster@yoctoproject.org'
> Subject: all tasks
> 
> I have pushed the "All tasks" code to ravi/all-tasks-feature branch.
> This is still work in progress and I have pushed it for your review.
> 
> The push includes the all-tasks page and these enhancements to the
> basetable:
> 
> - Display the table column header as a link only if it is sortable
> - Indicate the sort order as a up/down icon next to the column header
> 
> I have a few questions:
> 
> 1. The UI design indicates filtering on Order, Executed, Outcome and
> Cache Attempt columns. What are the filtering options for these
> columns?

I understand the it will be ascending or descending, but those values are not explicitly defined in the "models.py" file. I expect that the answer is related to my question about "orderby" that Alex gave part of an answer.
 
> 2. Is it correct to display the sstate_result for Cache Attempt?

I am doing exact that for the "recipes" detail page. I am getting my values and human readable values from the SSTATE_RESULT choices table within the "Recipe" class.

> 3. Should the Task log be a link to the file, and if so should the log
> be opened in the browser or compressed and shown as a download.

I myself am hoping and expecting that the user can be able to directly bring up the file in question, so that it is one stop shopping to see the log, and especially the errors, in order for the developer to directly address the issues for the rebuild. I do not know if we can a class for this operation yet, where a file is read into an object that can then be iterated by Django in the template.

I can though see the case where downloading the file for later review could be of value, but as a developer I find that a quick look at the errors allows me to directly see and resolve the problems almost every time.

David

> Thanks,
> Ravi
> 

Re: all tasks

[Ravi Chintakunta]

Hi David,

Thanks for your feedback.

>  > I have a few questions:
>  >
>  > 1. The UI design indicates filtering on Order, Executed, Outcome and
>  > Cache Attempt columns. What are the filtering options for these
>  > columns?
>  
>  I understand the it will be ascending or descending, but those values
>  are not explicitly defined in the "models.py" file. I expect that the
>  answer is related to my question about "orderby" that Alex gave part
>  of an answer.
> 

I have the ascending and descending order in place. Filtering is displayed as a funnel icon next to the column header and clicking that opens the filtering options in a modal dialog.

 
>  > 2. Is it correct to display the sstate_result for Cache Attempt?
>  
>  I am doing exact that for the "recipes" detail page. I am getting my
>  values and human readable values from the SSTATE_RESULT choices table
>  within the "Recipe" class.

Cool, I too did that.

>  
>  > 3. Should the Task log be a link to the file, and if so should the
>  log
>  > be opened in the browser or compressed and shown as a download.
>  
>  I myself am hoping and expecting that the user can be able to directly
>  bring up the file in question, so that it is one stop shopping to see
>  the log, and especially the errors, in order for the developer to
>  directly address the issues for the rebuild. I do not know if we can a
>  class for this operation yet, where a file is read into an object that
>  can then be iterated by Django in the template.
>  
>  I can though see the case where downloading the file for later review
>  could be of value, but as a developer I find that a quick look at the
>  errors allows me to directly see and resolve the problems almost every
>  time.
>  

I too prefer viewing the log in the browser. The task log in the database is the absolute path to the log file, so it should be easy to launch it in browser. But I am not sure how big the log files can be, and viewing large files in the browser will be a pain. 

-Ravi

Re: all tasks

[Reyna, David]

Hi Ravi,

I am having problems with the bread crumbs. Did you get the intermediate back link to "Tasks" in your tasks detail page? I am not seeing my "Recipes" backlink, nor any obvious way to add it. I will have to start my google search.

> I too prefer viewing the log in the browser. The task log in the
> database is the absolute path to the log file, so it should be easy to
> launch it in browser. But I am not sure how big the log files can be,
> and viewing large files in the browser will be a pain.

We could have a specific view for displaying files. I would think that there would be four ways to view the file. At the top of the page we can perhaps display the total number of lines, to help guide the user in selecting the appropriate template.

  (a) This option would display only the end of the log file. As per the command line, the last n (~50) lines are the most valuable if there is an error, and if you are being interactive in the manner with Toaster I think that what you are doing is trying to resolve builds. I would propose that this be the default display, where the other modes would be selectable in the side bar.

  (b) To address your point, the next display could be by pages, where there is a default line count much as there already a record count option in the current views. 

  (c) I would think that we would still want to offer a continuous display choice, for those that want to view, cut, and paste the whole content without it paginated as per option "b".

  (d) Finally, we should offer the file download option.

- David

Re: all tasks

[Reyna, David]

Hi again,

> I am having problems with the bread crumbs. 

Ah, I figured out the breadcrumbs by looking at "basebuildpage.htm"! I somehow though that there was more inheritance going on in the background, but I see now that one needs to explicitly add all breadcrumbs past the build selection, in my case:

{% block localbreadcrumb %}
<li><a href="{% url 'recipes' build.pk %}">Recipes</a></li>
<li><a href="{% url 'recipe'  build.pk object.pk%}">Recipe ({{object.name}}_{{object.version}})</a></li>
{% endblock %}

- David

Re: all tasks

[Barros Pena, Belen]

On 10/01/2014 23:43, "Ravi Chintakunta" <ravi.chintakunta@timesys.com>
wrote:

>I have pushed the "All tasks" code to ravi/all-tasks-feature branch.
>This is still work in progress and I have pushed it for your review.
>
>The push includes the all-tasks page and these enhancements to the
>basetable:
>
>- Display the table column header as a link only if it is sortable
>- Indicate the sort order as a up/down icon next to the column header
>
>I have a few questions:
>
>1. The UI design indicates filtering on Order, Executed, Outcome and
>Cache Attempt columns. What are the filtering options for these columns?

Filtering, searching and sorting for each page have their own Bugzilla
features. The filtering feature for the tasks table is 4278

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4278

There is a design document attached to the feature explaining each filter
in detail. You might want to coordinate with Alex, who is working on
filtering for the builds table.

>
>2. Is it correct to display the sstate_result for Cache Attempt?

Yes. That should do fine for the moment.

>
>3. Should the Task log be a link to the file, and if so should the log be
>opened in the browser or compressed and shown as a download.

This is a very good question, and the answer is "not for the moment (I
think)". The designs reflect the fact that the version 1 of the analysis
functionality works only locally (Toaster needs to be running in the same
machine as the build). However, we are moving towards providing remote
functionality, so things will change. But before making specific changes
we should put some thought into which files should be accessible through
Toaster and how we are going to provide access to them.

>
>Thanks,
>Ravi
>
>

Tasks table row style

[Ravi Chintakunta]

I pushed a couple of commits to ravi/all-tasks-feature branch:

- add custom tag "task_color" to return a style based on task execution status and outcome
- tasks table that uses the custom tag

The custom tag can be included in the table row <tr> to style the entire row. The row cells that have a hyperlink do not pick up the style. You have to also include the custom tag in the <a href> tags to modify the style. 

Please review and let me know what you think.

Thanks,
Ravi

Re: Tasks table row style

[Ravi Chintakunta]

>  
>  I pushed a couple of commits to ravi/all-tasks-feature branch:
>  
>  - add custom tag "task_color" to return a style based on task
>  execution status and outcome
>  - tasks table that uses the custom tag
>  
>  The custom tag can be included in the table row <tr> to style the
>  entire row. The row cells that have a hyperlink do not pick up the
>  style. You have to also include the custom tag in the <a href> tags to
>  modify the style.
>  

I have fixed the code to use the css class instead of hard coded colors. With that you can include the custom tag in the table row <tr> and that would take care of changing the color of all the cells in the row, including hyperlinks. So you need not repeat the custom tag in <a href> tag.

Thanks,
Ravi

Re: Tasks table row style

[Barros Pena, Belen]

On 15/01/2014 17:27, "Ravi Chintakunta" <ravi.chintakunta@timesys.com>
wrote:

>>  
>>  I pushed a couple of commits to ravi/all-tasks-feature branch:
>>  
>>  - add custom tag "task_color" to return a style based on task
>>  execution status and outcome
>>  - tasks table that uses the custom tag
>>  
>>  The custom tag can be included in the table row <tr> to style the
>>  entire row. The row cells that have a hyperlink do not pick up the
>>  style. You have to also include the custom tag in the <a href> tags to
>>  modify the style.
>>  
>
>I have fixed the code to use the css class instead of hard coded colors.
>With that you can include the custom tag in the table row <tr> and that
>would take care of changing the color of all the cells in the row,
>including hyperlinks. So you need not repeat the custom tag in <a href>
>tag.

Thanks, Ravi. Is this also working with the error class? It looks like
Bootstrap defines certain styles for rows with the .error class, and I am
wondering if we'll need to override those.

Cheers

Belén


>
>Thanks,
>Ravi

Re: Tasks table row style

[Ravi Chintakunta]

Hi Belen,
  
>  Thanks, Ravi. Is this also working with the error class? It looks like
>  Bootstrap defines certain styles for rows with the .error class, and I
>  am
>  wondering if we'll need to override those.
>  

For .error class, the hyperlinks are not being colored and also the row background is being changed. 

The background is being set in bootstrap.min.css

The hyperlinks are not colored, because there is no style for ".error a" in default.css. The style is set for ".muted a" though.

Can you fix the css or do you want me to?

Thanks,
Ravi

Re: Tasks table row style

[Barros Pena, Belen]

On 15/01/2014 18:16, "Ravi Chintakunta" <ravi.chintakunta@timesys.com>
wrote:

>Hi Belen,
>  
>>  Thanks, Ravi. Is this also working with the error class? It looks like
>>  Bootstrap defines certain styles for rows with the .error class, and I
>>  am
>>  wondering if we'll need to override those.
>>  
>
>For .error class, the hyperlinks are not being colored and also the row
>background is being changed.
>
>The background is being set in bootstrap.min.css
>
>The hyperlinks are not colored, because there is no style for ".error a"
>in default.css. The style is set for ".muted a" though.
>
>Can you fix the css or do you want me to?

I can do that. 

Belén

>
>Thanks,
>Ravi

Re: git push to poky-contrib/ravi

[Reyna, David]

Hi Ravi,

Here is my first pass review. 

1) I observe for your "...5ee1" commit there is no "Signed-off-by". Your other two commits do have that field.

  $ git log
  ...
  commit 2848c7e9cdb37890c5f602dc5a8cebc5fad95ee1
  Author: Ravi Chintakunta <ravi.chintakunta@timesys.com>
  Date:   Thu Jan 9 22:08:09 2014 -0500

    Django settings: Removed duplicate toastergui entry in INSTALLED_APPS

  [[ no "Signed-off-by" ]]
  ...

2) It does not appear that you have the row context coloring based on the "outcome" value. I actually have that working in my new "recipe details" page (via my "outcome_highlight" helper method). We could share this implantation.

3) It appears that "{% if not objects %}" is the same as "{% ifequal 0 objects.count %}". If so, I can simplify my code accordingly.

4) I observe that you have not implemented the href for the log file, presumably waiting for resolution of the questions you raised. 

Question for Belen. The sample All Tasks page from "yocto.com/toaster" has HREF links on all items in the table, but the design document has no reference as far as I can see to HREF usage.

5) Another question for Belen. The design document says that there are 3 values for "Cache Attempt" (presumably mapping to "sstate_result", but SSTATE_RESULT has 4 values, not three. And none of them map to an empty display string, in contrast to the screen shot in the design document.

- David

 

> -----Original Message-----
> From: Ravi Chintakunta [mailto:ravi.chintakunta@timesys.com]
> Sent: Friday, January 10, 2014 9:11 AM
> To: Reyna, David; Lerner, Dave; 'Damian, Alexandru'; 'Barros Pena,
> Belen'; 'Zhang, Jessica'; Bansal, Atul
> Cc: 'toaster@yoctoproject.org'
> Subject: git push to poky-contrib/ravi
> 
> I got push access from Michael and pushed a small commit to ravi/all-
> tasks-feature branch.
> 
> Just a few notes to help others with the first push.
> 
> 1. Changing the branch name:
> ============================
> It is good to have the same name for the local branch and the remote
> branch. If your local branch name is not in the form <yourname>/<branch
> name> you can rename your current branch by:
> 
> git branch -m <yourname>/<branch name>
> 
> 
> 2. Changing the remote url:
> ===========================
> When you setup your development environment, you would have cloned from
> a http url like http://git.yoctoproject.org/git/poky-contrib. You will
> not be able to push to this url and you will get an error like this:
> 
> fatal: unable to access 'http://git.yoctoproject.org/git/poky-
> contrib/': The requested URL returned error: 403
> 
> 
> You have to edit the remote url, by first checking the remote alias and
> url, and then changing the url.
> 
> You can view the remote aliases and the url by:
> 
> git remote --verbose
> 
> >>> This is the output on my machine:
> contrib http://git.yoctoproject.org/git/poky-contrib (fetch)
> contrib http://git.yoctoproject.org/git/poky-contrib (push)
> 
> ** Note contrib is my remote alias for poky-contrib
> 
> 
> For push, you have to change the url to git@git.yoctoproject.org:poky-
> contrib
> 
> You can change the url by:
> 
> git remote set-url contrib git@git.yoctoproject.org:poky-contrib
> 
> 
> After that you will able to push by:
> 
> git push contrib <yourname>/<branch name>
> 
> 
> Thanks,
> Ravi

Re: git push to poky-contrib/ravi

[Barros Pena, Belen]

On 13/01/2014 06:01, "Reyna, David" <david.reyna@windriver.com> wrote:

>Hi Ravi,
>
>Here is my first pass review.
>
>1) I observe for your "...5ee1" commit there is no "Signed-off-by". Your
>other two commits do have that field.
>
>  $ git log
>  ...
>  commit 2848c7e9cdb37890c5f602dc5a8cebc5fad95ee1
>  Author: Ravi Chintakunta <ravi.chintakunta@timesys.com>
>  Date:   Thu Jan 9 22:08:09 2014 -0500
>
>    Django settings: Removed duplicate toastergui entry in INSTALLED_APPS
>
>  [[ no "Signed-off-by" ]]
>  ...
>
>2) It does not appear that you have the row context coloring based on the
>"outcome" value. I actually have that working in my new "recipe details"
>page (via my "outcome_highlight" helper method). We could share this
>implantation.
>
>3) It appears that "{% if not objects %}" is the same as "{% ifequal 0
>objects.count %}". If so, I can simplify my code accordingly.
>
>4) I observe that you have not implemented the href for the log file,
>presumably waiting for resolution of the questions you raised.
>
>Question for Belen. The sample All Tasks page from "yocto.com/toaster"
>has HREF links on all items in the table, but the design document has no
>reference as far as I can see to HREF usage.

Interactivity for each cell in the table is explained on page 8 (the last
one) of the design document (Design 1.3 All tasks) attached to

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4275

There is a table in that page with an Interactivity column, where you can
see if the cell is a link and to where.

The following cells are links:

Order (to Task details page)
Recipe (to Recipe details page)
Recipe version (to recipe details page)
Task (to task details page)
Executed (to task details page)
Outcome (to task details page)
Cache attempt (to task details page)

Time, CPU, Disk I/O and Log are not links (Log will become a link at some
point, but first we need to work out how we are going to provide access to
log files for the remote use case: it does not make sense to have a link
for the local use case).

>
>5) Another question for Belen. The design document says that there are 3
>values for "Cache Attempt" (presumably mapping to "sstate_result", but
>SSTATE_RESULT has 4 values, not three. And none of them map to an empty
>display string, in contrast to the screen shot in the design document.

Good question: this is not explained properly anywhere (apologies). There
are indeed 4 sstate results:

SSTATE_NA - Not Applicable. This is for tasks that do not attempt to reuse
sstate objects. That value does not display on the table (the cell should
be blank)

SSTATE_MISS - Missing. This is for tasks that attempt to reuse an sstate
object but the object searched for does not exist. This value shows in the
table as "File not in cache"

SSTATE_FAILED - Failed. This is for tasks that attempt to reuse an sstate
object, the object is found but cannot be restored. This value shows in
the table as "Failed" and has the .warning class applied

SSTATE_RESTORED - Restored. This is for tasks that successfully reuse an
sstate object (i.e. Cached tasks). This value shows in the table as
"Succeeded"

Let me know if you have any questions.

Belén



>
>- David
>
> 
>
>> -----Original Message-----
>> From: Ravi Chintakunta [mailto:ravi.chintakunta@timesys.com]
>> Sent: Friday, January 10, 2014 9:11 AM
>> To: Reyna, David; Lerner, Dave; 'Damian, Alexandru'; 'Barros Pena,
>> Belen'; 'Zhang, Jessica'; Bansal, Atul
>> Cc: 'toaster@yoctoproject.org'
>> Subject: git push to poky-contrib/ravi
>> 
>> I got push access from Michael and pushed a small commit to ravi/all-
>> tasks-feature branch.
>> 
>> Just a few notes to help others with the first push.
>> 
>> 1. Changing the branch name:
>> ============================
>> It is good to have the same name for the local branch and the remote
>> branch. If your local branch name is not in the form <yourname>/<branch
>> name> you can rename your current branch by:
>> 
>> git branch -m <yourname>/<branch name>
>> 
>> 
>> 2. Changing the remote url:
>> ===========================
>> When you setup your development environment, you would have cloned from
>> a http url like http://git.yoctoproject.org/git/poky-contrib. You will
>> not be able to push to this url and you will get an error like this:
>> 
>> fatal: unable to access 'http://git.yoctoproject.org/git/poky-
>> contrib/': The requested URL returned error: 403
>> 
>> 
>> You have to edit the remote url, by first checking the remote alias and
>> url, and then changing the url.
>> 
>> You can view the remote aliases and the url by:
>> 
>> git remote --verbose
>> 
>> >>> This is the output on my machine:
>> contrib http://git.yoctoproject.org/git/poky-contrib (fetch)
>> contrib http://git.yoctoproject.org/git/poky-contrib (push)
>> 
>> ** Note contrib is my remote alias for poky-contrib
>> 
>> 
>> For push, you have to change the url to git@git.yoctoproject.org:poky-
>> contrib
>> 
>> You can change the url by:
>> 
>> git remote set-url contrib git@git.yoctoproject.org:poky-contrib
>> 
>> 
>> After that you will able to push by:
>> 
>> git push contrib <yourname>/<branch name>
>> 
>> 
>> Thanks,
>> Ravi
>

Re: git push to poky-contrib/ravi

[Ravi Chintakunta]

Hi David,

>  -----Original Message-----
>  From: Reyna, David [mailto:david.reyna@windriver.com]
>  Sent: Monday, January 13, 2014 1:02 AM
>  To: Ravi Chintakunta; Lerner, Dave; 'Damian, Alexandru'; 'Barros Pena,
>  Belen'; 'Zhang, Jessica'; Bansal, Atul
>  Cc: 'toaster@yoctoproject.org'
>  Subject: RE: git push to poky-contrib/ravi
>  
>  Hi Ravi,
>  
>  Here is my first pass review.
>  
>  1) I observe for your "...5ee1" commit there is no "Signed-off-by".
>  Your other two commits do have that field.
>  
>    $ git log
>    ...
>    commit 2848c7e9cdb37890c5f602dc5a8cebc5fad95ee1
>    Author: Ravi Chintakunta <ravi.chintakunta@timesys.com>
>    Date:   Thu Jan 9 22:08:09 2014 -0500
>  
>      Django settings: Removed duplicate toastergui entry in
>  INSTALLED_APPS
>  
>    [[ no "Signed-off-by" ]]
>    ...
>  

Yeah, I missed it. I saw the commit message guidelines after committing this.


>  2) It does not appear that you have the row context coloring based on
>  the "outcome" value. I actually have that working in my new "recipe
>  details" page (via my "outcome_highlight" helper method). We could
>  share this implantation.
>  

Yes, still work in progress.

>  3) It appears that "{% if not objects %}" is the same as "{% ifequal 0
>  objects.count %}". If so, I can simplify my code accordingly.
>  

They are not same. "{% if not objects %}" will work when objects is None and when the size is zero. 

>  4) I observe that you have not implemented the href for the log file,
>  presumably waiting for resolution of the questions you raised.
>  

Yes.


Thanks,
Ravi

Re: git push to poky-contrib/ravi

[Barros Pena, Belen]

On 13/01/2014 14:17, "Ravi Chintakunta" <ravi.chintakunta@timesys.com>
wrote:

>Hi David,
>
>>  -----Original Message-----
>>  From: Reyna, David [mailto:david.reyna@windriver.com]
>>  Sent: Monday, January 13, 2014 1:02 AM
>>  To: Ravi Chintakunta; Lerner, Dave; 'Damian, Alexandru'; 'Barros Pena,
>>  Belen'; 'Zhang, Jessica'; Bansal, Atul
>>  Cc: 'toaster@yoctoproject.org'
>>  Subject: RE: git push to poky-contrib/ravi
>>  
>>  Hi Ravi,
>>  
>>  Here is my first pass review.
>>  
>>  1) I observe for your "...5ee1" commit there is no "Signed-off-by".
>>  Your other two commits do have that field.
>>  
>>    $ git log
>>    ...
>>    commit 2848c7e9cdb37890c5f602dc5a8cebc5fad95ee1
>>    Author: Ravi Chintakunta <ravi.chintakunta@timesys.com>
>>    Date:   Thu Jan 9 22:08:09 2014 -0500
>>  
>>      Django settings: Removed duplicate toastergui entry in
>>  INSTALLED_APPS
>>  
>>    [[ no "Signed-off-by" ]]
>>    ...
>>  
>
>Yeah, I missed it. I saw the commit message guidelines after committing
>this.
>
>
>>  2) It does not appear that you have the row context coloring based on
>>  the "outcome" value. I actually have that working in my new "recipe
>>  details" page (via my "outcome_highlight" helper method). We could
>>  share this implantation.
>>  
>
>Yes, still work in progress.
>
>>  3) It appears that "{% if not objects %}" is the same as "{% ifequal 0
>>  objects.count %}". If so, I can simplify my code accordingly.
>>  
>
>They are not same. "{% if not objects %}" will work when objects is None
>and when the size is zero.

Just a quick comment on this one: as a general rule, we don't display
values when they are none or 0. The reason is to show only meaningful
information, because there is already a lot of it!

So, for example, if you look at the Time table

http://www.yoctoproject.org/toaster/build-time.html

you'll see that when time is 0 (for example, for not executed tasks) the
cells are empty.

> 
>
>>  4) I observe that you have not implemented the href for the log file,
>>  presumably waiting for resolution of the questions you raised.
>>  
>
>Yes.
>
>
>Thanks,
>Ravi