Difference between revisions of "Open Source Meeting/Agenda"
Jump to navigation
Jump to search
(→Agenda Thursday, 03 March 2010: Old and new topics) |
|||
| Line 7: | Line 7: | ||
== Agenda Thursday, | == Agenda Thursday, 03 March 2010 == | ||
# Weekly Snowglobe update - [[User:Merov Linden|Merov Linden]] | # Weekly Snowglobe update - [[User:Merov Linden|Merov Linden]] | ||
# | # Finalize 1.3 | ||
#* | #* outstanding bugs? | ||
#* test sprint required? | |||
#* | #* RC2 ready to be the release? | ||
#* | |||
# {{jira|SNOW-495}}: create a <code>BINDIST</code> CMake variable for producing (hopefully) legally distributable binaries | # {{jira|SNOW-495}}: create a <code>BINDIST</code> CMake variable for producing (hopefully) legally distributable binaries | ||
#* | #* Not answered at last meeting: Could we get LL's legal department to cooperate on this one, so we can minimize the guessing on what the required steps are? | ||
# Snowglobe 1.4: bug triaged in the community, tree's open, commits coming? | |||
#* "commits coming?": looks like not anymore ... | |||
# Snowglobe 2.0: what the heck was Merov doing? | |||
# Snowglobe 1.4: bug triaged in | |||
# Snowglobe 2.0: what the heck | |||
#* Snowglobe 2.0 Source code issues, many with patches (see [https://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&&pid=10100&component=10379&version=10571 SNOW 2.0 Source Code issues on pJIRA]) | #* Snowglobe 2.0 Source code issues, many with patches (see [https://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&&pid=10100&component=10379&version=10571 SNOW 2.0 Source Code issues on pJIRA]) | ||
#* Is there a way to push svn history from projects/2009/snowglobe into projects/2010/snowglobe, and if so, is it worth the effort? | #* Is there a way to push svn history from projects/2009/snowglobe into projects/2010/snowglobe, and if so, is it worth the effort? | ||
#* How to handle ports from Snowglobe 1.x to 2.0? | |||
#** For now, we've opened separate issues, so status can be tracked independently. (We don't want to mess up the 1.x release process by reopening stuff that is and stays fixed in 1.x) | |||
#** Should we still include the original issue IDs in <code>contributions.txt</code>, so that [http://svn.secondlife.com/trac/linden/changeset?old_path=projects%2F2009%2Fsnowglobe%2Ftrunk%2Fdoc%2Fcontributions.txt&new_path=projects%2F2010%2Fsnowglobe%2Ftrunk%2Fdoc%2Fcontributions.txt <code title="compare contributions.txt between trunks of Snowglobe 1.x and 2.x">diff</code>] can be used to see what still needs to be ported? | |||
== Test Sprint == | == Test Sprint == | ||
Revision as of 09:42, 3 March 2010
Open source meeting - Thursday, 2pm PT.
Teleport to the Linden Open Source Project headquarters.
Please try to add your items as early as possible in the week to give Merov a chance to round up any Lindens that may be appropriate to the discussion. Please also bring large or contentious items up on OpenSource-Dev before or concurrently with adding them as agenda items.
Agenda Thursday, 03 March 2010
- Weekly Snowglobe update - Merov Linden
- Finalize 1.3
- outstanding bugs?
- test sprint required?
- RC2 ready to be the release?
- SNOW-495: create a
BINDISTCMake variable for producing (hopefully) legally distributable binaries- Not answered at last meeting: Could we get LL's legal department to cooperate on this one, so we can minimize the guessing on what the required steps are?
- Snowglobe 1.4: bug triaged in the community, tree's open, commits coming?
- "commits coming?": looks like not anymore ...
- Snowglobe 2.0: what the heck was Merov doing?
- Snowglobe 2.0 Source code issues, many with patches (see SNOW 2.0 Source Code issues on pJIRA)
- Is there a way to push svn history from projects/2009/snowglobe into projects/2010/snowglobe, and if so, is it worth the effort?
- How to handle ports from Snowglobe 1.x to 2.0?
- For now, we've opened separate issues, so status can be tracked independently. (We don't want to mess up the 1.x release process by reopening stuff that is and stays fixed in 1.x)
- Should we still include the original issue IDs in
contributions.txt, so thatdiffcan be used to see what still needs to be ported?
Test Sprint
What to do in RC Test Sprints (template, should move to a different wiki page):
- All participants to download the same build, hopefully on a variety of platforms
- Regress bugs and features fixed in cycle
- Test outstanding bugs: narrow them down then we can decide to make them showstoppers or punt to future.
- Pass the regular list of tests:
- Preview Smoke Test
- User Interface Smoke Test
- Newbie_Test
- Preferences and General UI
- Building_Tools_Test
- Media Plugin Test
Default agenda
(after agenda above):
- Update from the Lindens (standing item) - Merov Linden
- SNOW project, unresolved
- VWR project: Affects version: "Snowglobe Test Builds"
- Triage of "Source Code" issues