Perfomatic:Meeting Notes: Difference between revisions
Jump to navigation
Jump to search
(→Aug 21) |
No edit summary |
||
Line 1: | Line 1: | ||
= Aug 28 = | |||
* Got more [[Perfomatic:Requirements feedback]] | |||
* Code freeze tonight @ 11:59pm PST | |||
* Push Tuesday | |||
* Any bugs that look like they can't be finished by eod, move to 0.5 | |||
* Not all bugs are equal, I (Ryan) need to review each one to make sure people don't have more than one huge bug per sprint. | |||
* Laura moving off of graph server | |||
= Aug 21 = | = Aug 21 = | ||
* We have a QA resource, Stephen! | * We have a QA resource, Stephen! |
Revision as of 01:55, 28 August 2008
Aug 28
- Got more Perfomatic:Requirements feedback
- Code freeze tonight @ 11:59pm PST
- Push Tuesday
- Any bugs that look like they can't be finished by eod, move to 0.5
- Not all bugs are equal, I (Ryan) need to review each one to make sure people don't have more than one huge bug per sprint.
- Laura moving off of graph server
Aug 21
- We have a QA resource, Stephen!
- Creating mailing list: graphserver@mozilla.com
- Got some feedback (barely)
- A lot of test data here (22MB unzipped): http://people.mozilla.org/~rdoherty/graphserver/test_data.sql.zip
- RRDtool
- "RRDtool is the OpenSource industry standard, high performance data logging and graphing system for time series data."
- Could this be a 'good enough' solution to deal with our large data volume?
- Averages and compresses data over time to stop files from becoming huge.
- We need to remove old series data, probably anything older than 60 days.
Aug 14
- Catch Ryan up on current state of graph server
- 100% on hg: YES!
- stage is auto-update every 10 mins
- Set a schedule for when to push changes to prod
- Can we get someone to QA bugs?
- Ryan to find someone to verify bugs
- Moved 0.3 to 0.4
- Schedule 0.4 deadline
- Possible review of suggestions from BZ, dbaron and Vlad
- Sheriffs, dolske & jonas
- SELECT id, machine, test, test_type, date, extra_data, branch FROM dataset_info WHERE type = 'discrete' AND test_type != 'baseline' and (date >= 0)
- Index on type
- 0.4 milestone is still a 'get it working' milestone.
- Linking is important
- Displaying data is important
- Move any trivial or unrelated bugs to 0.5
July 15
- 0.3 updates -- run through the list, identify blockers for Wednesday
- Hugging
- Alice's updates
- i've check in my pending hg patches
- we are still missing re-write rules for old vs. new link format
- we'll need patches to talos config files to point to the new graph server, once we are ready to do the shift
- Other topics
July 9
F
July 2
- identify blockers
- python on OS X -- getting libararies installed
- lorchard errors
- get status updates on open bugs
- get a handle on scheduling
- when will we cut over cvs -> hg
- when will we cut over to the new front-end
- old links will break, people were upset about old graph links in bugs breaking
- what are old link formats and how do they map to the new links
- July 16th for 0.3 (installation, maintneance, cvs->hg)
- On new front-end by July 25th (completely)
- any other open issues
- TODO
- find QA person
- documentation for deployment when we want consolidate on new front end
- Hg tagging for production policies
- re-org 0.3, 0.4
June 20
- Bug List
- identify first 2 milestones (3 week timelines)
- schedule our releases into at least end of July
- team intro, questions about projects, any other topics
- How to get a dev environment setup. Need a wiki page, (small) db dump, etc.