BMO/Meetings/2013-07-30

From MozillaWiki
< BMO‎ | Meetings
Jump to: navigation, search

people: dkl, mark, glob, liz, gerv, rail, kyle

Rail Alliev from release engineering - working on setup for AutoLand - depending on group you see this edit link:

3889836b.png

and then this interface:

a7196730.png

Rail is looking into enhancing this and running it against some rel eng repos. It will need a cluster of machines and will be a distributed service - and will have a development and staging server as well. Will be working with others on workflow.

  • The last modified flag. what can change in a bug without changing last modified? product name changes, component name changes.
  • there are things that are referenced by the bug but aren't part of the bug object.
  • since a person doing a UI (the ember.js one) has to change their ui if that info changes they do need to know it.
  • gerv suggests a push mechanism if some things change.
  • dkl and glob think that would be too big of a change.
  • He has to get a list of all the product and components. Maybe they should also have a last modified flag rather than doing an occasional refresh.
  • config.cgi does do etags .
  • last modified and etags are both useful. he is asking for etag support first.
  • etag is a hash of the content you are getting back so if anything changes it will be changed. the last modified only changes with bug data.

May or may not push out changes next week, probably not because of A-Team work week.

Glob is working on gmail again because fonts turned out to be somewhat more complicated than expected. (for html bugmail)

Custom fields are not flags but are going into the main bug table. this will be important for kanban.

  • Discussion of Keywords vs. whiteboard vs. custom field.
  • This might be one field with 6 values.

We had to end the meeting early.

Retrieved from "https://wiki.mozilla.org/index.php?title=BMO/Meetings/2013-07-30&oldid=687510"