lifecycle of a bug

30
Lifecycle of a Bug John Greene Senior Director, Customer Centric Engineering @eviljg Vijay Swamidass SMTS, Customer Centric Engineering @vijayswamidass

Upload: salesforce-developers

Post on 18-Nov-2014

323 views

Category:

Documents


4 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Lifecycle of a Bug

Lifecycle of a Bug

John Greene

Senior Director, Customer Centric Engineering

@eviljg

Vijay Swamidass

SMTS, Customer Centric Engineering

@vijayswamidass

Page 2: Lifecycle of a Bug

Safe Harbor

Safe harbor statement under the Private Securities Litigation Reform Act of 1995:

This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if

any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-

looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of

product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of

management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments

and customer contracts or use of our services.

The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our

service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth,

interruptions or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other l itigation, risks associated

with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain,

and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling

non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the

financial results of salesforce.com, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended July 31, 2012. This

documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.

Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may

not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently

available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

Page 3: Lifecycle of a Bug

Lifecycle of a Bug

John Greene, Sr. Director, CCE

Vijay Swamidass, SMTS, CCE

Page 4: Lifecycle of a Bug

Who has encountered a

Salesforce Bug?

Page 5: Lifecycle of a Bug

Lifecycle of Salesforce Bug

Page 6: Lifecycle of a Bug

So how do I track my

Salesforce Bug?

Page 7: Lifecycle of a Bug
Page 8: Lifecycle of a Bug

Known Issues Demo

Page 9: Lifecycle of a Bug

Case

Objective - Solve or Reproduce and Escalate to R&D

Owner - Customer Support

View - help.salesforce.com

Page 10: Lifecycle of a Bug

Investigation

Objective – Triage and Diagnose issue. Resolve if possible or create Bug.

Owner – Engineering (CCE or Scrum Team)

View – None

Page 11: Lifecycle of a Bug

Investigation Demo

Page 12: Lifecycle of a Bug

Bug

Objective – Determine the code change to fix the defect and tests to verify

Owner – Development and Quality Engineering

View – Known Issues Site

Page 13: Lifecycle of a Bug

Bug Demo

Page 14: Lifecycle of a Bug

Fix

Objective – Check in the corrected code to a scheduled release

Owner – Development and Quality Engineering

View – Known Issues Site

Page 15: Lifecycle of a Bug

Fix

Determine a release and commit code

Type When What

Major Every 4 months * New Features and Bug Fixes

Patch Weekly ** Bug Fixes

* Dates are published in advance

** Usually Wednesdays

Page 16: Lifecycle of a Bug

Fix Demo

Page 17: Lifecycle of a Bug

Release

Objective – Deploy the correct code to production instances

Owner – Release Engineering

View – Known Issues Site

Page 18: Lifecycle of a Bug

Release

Status Meaning

In Progress The code fix has been deployed to some (not all) instances

Fixed All Instances have received the fix

Rollback* The fix was reverted

*When a rollback occurs, the Known Issue status will return to the status prior to the release

Page 19: Lifecycle of a Bug

Release Demo

Page 20: Lifecycle of a Bug

Release Demo

Page 21: Lifecycle of a Bug

Release Demo

Page 22: Lifecycle of a Bug

Lifecycle of Salesforce Bug

Page 23: Lifecycle of a Bug

Known Issues

Tips and Ideas

Page 24: Lifecycle of a Bug

RSS

• Subscribe to a Tag or a Status

• Use publically available tools to get email notification (i.e. feedmyinbox.com)

Page 25: Lifecycle of a Bug

This Affects Me!

• Let’s Salesforce know which issues are affecting the most customers

• Helps the community identify hot issues

Page 26: Lifecycle of a Bug

Known Issues Ideas

- How can I view the fixes for a given patch or release?

- I want to be proactively notified!

- Tell us what you want on the Idea exchange

Page 27: Lifecycle of a Bug

Things to Remember

Page 28: Lifecycle of a Bug

Remember!

1. Google your Salesforce Bugs

2. Provide quick, simple steps to reproduce your problem!

3. Ask your support rep if your bug is a candidate for KI

4. Vote for the issues that affect you

Page 29: Lifecycle of a Bug

Where to Go Next

Known Issues http://success.salesforce.com/issues

Vijay Swamidass @vijayswamidass

[email protected]

John Greene @eviljg

[email protected]

Page 30: Lifecycle of a Bug