• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Lifecycle of a Bug

Lifecycle of a Bug






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Lifecycle of a Bug Lifecycle of a Bug Presentation Transcript

    • Lifecycle of a BugJohn GreeneSenior Director, Customer Centric Engineering@eviljgVijay SwamidassSMTS, Customer Centric Engineering@vijayswamidass
    • 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 litigation, 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.
    • Lifecycle of a BugJohn Greene, Sr. Director, CCEVijay Swamidass, SMTS, CCE
    • Who has encountered aSalesforce Bug?
    • Lifecycle of Salesforce Bug
    • So how do I track mySalesforce Bug?
    • Known Issues Demo
    • CaseObjective - Solve or Reproduce and Escalate to R&DOwner - Customer SupportView - help.salesforce.com
    • InvestigationObjective – Triage and Diagnose issue. Resolve if possible or create Bug.Owner – Engineering (CCE or Scrum Team)View – None
    • Investigation Demo
    • BugObjective – Determine the code change to fix the defect and tests to verifyOwner – Development and Quality EngineeringView – Known Issues Site
    • Bug Demo
    • FixObjective – Check in the corrected code to a scheduled releaseOwner – Development and Quality EngineeringView – Known Issues Site
    • FixDetermine a release and commit codeType When WhatMajor Every 4 months * New Features and Bug FixesPatch Weekly ** Bug Fixes * Dates are published in advance ** Usually Wednesdays
    • Fix Demo
    • ReleaseObjective – Deploy the correct code to production instancesOwner – Release EngineeringView – Known Issues Site
    • 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
    • Release Demo
    • Release Demo
    • Release Demo
    • Lifecycle of Salesforce Bug
    • Known IssuesTips and Ideas
    • RSS• Subscribe to a Tag or a Status• Use publically available tools to get email notification (i.e. feedmyinbox.com)
    • This Affects Me!• Let’s Salesforce know which issues are affecting the most customers• Helps the community identify hot issues
    • 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
    • Things to Remember
    • Remember!1. Google your Salesforce Bugs2. Provide quick, simple steps to reproduce your problem!3. Ask your support rep if your bug is a candidate for KI4. Vote for the issues that affect you
    • Where to Go NextKnown Issues http://success.salesforce.com/issues Vijay Swamidass @vijayswamidass vswamidass@salesforce.com John Greene @eviljg jgreene@salesforce.com