SharePoint 2010 Build Numbers (Cube Sheet)

SharePoint 2010 Build Numbers Cube Sheet

As many times used in our daily business, we’re used to ask for “Build number” rather than “Service Pack or Patch level”.
Because of some confusion of the customers and for transparency I’ll provide here a list of the most relevant Build numbers and its related KB Numbers.

Quick Jump list:

Build Tables for other SharePoint versions:

image Important:

Bildergebnis für notice  Note:
The bits of RTM version are shown in central admin page with Build number “14.0.4762.1000” but it’s actually “14.0.4763.1000” – So no worry about 😉
In case of early publishing, some KB article might not be available right away while the download links already working. Please consider, that delay’s in publishing the according KB articles will be expected!

)1 = in the KB articles for the October 2013 CU there is the Build Number 14.0.7110.5000 mentioned but after installing the Oct. 2013 CU, you’ll find the Build Version 14.0.7108.5000 shown in the central admin.
If you want to be sure that you have installed the right CU/Version, see here for more info about it:

Table View:  [ Last Updated: 2016-12-30 ]  (find the archived Builds prior SP2 here)

Title and post in reference

Build# Srv
Build# WSS

MSF2010 *
KB articles

SPS 2010 Server KB articles

Project Server 2010 KB articles

Global language

Notes, Remarks, Known Issues

RTM (04/2010) 14.0.4763.1000 n/a Major release
SP1 – 2011 14.0.6029.1000 2460058 2510766 2460047 y SP1 and June CU
SP2 – 2013 14.0.7015.1000 2687464 2687453 2687452 no
June CU 13 14.0.7102.5000 2817552 2817527 2817368 y Blog
August CU 13 14.0.7106.5000
y Blog
October CU 13  )1
(Build shown in CA)
2825824 2825786 2825793 y
December CU 13 14.0.7113.5000 2849990 2849971 2849972 y
Feb. CU 14 14.0.7116.5000 2863938 2863913 y
April CU 14 14.0.7121.5000 2878270 2878250 2878253 y
June CU 14 14.0.7125.5002 2880975 2880972  2880974 y
July CU 14 14.0.7128.5001 2883026 2883005 n/a y
August CU 14 14.0.7129.5000 2889831 n/a y see post
August CU 14 14.0.7130.5000 2889825 n/a y see post
September CU 14 14.0.7132.5000 2889932 2883103 2883006 n/a see KB’s
October 14 (no uber!) 14.0.7134.5000 n/a 2899490 2899485, 2880539 y see post
November 14 14.0.7137.5000 2889933 2899478 2899479 y SP2 required!
December 14 14.0.7140.5000 2899585 2899583 2899583 y SP2 required!
February 15 14.0.7143.5000 2910904 2899558 2899557 y
MS15-012 see here
March 15 14.0.7145.5001 2956208 2956201 2956198 y
April 15 14.0.7147.5000 2965241 2965294 2965293 y
see here
May 15 14.0.7149.5000 3017815 3015569 2999496 y
June 15 14.0.7151.5001 3054847 3054880 3054877 y
July 15 14.0.7153.5000 3054983  3054975 3054972 y MS15-046
August 15 14.0.7155.5001 3055049 3055040 3055038 y
September 15 14.0.7157.5001 3085530 3085521 3085517 y
October 15 14.0.7160.5000 3085613 3085603 3085598 y
MS15-110 n/a 3085613 3085596 Blog1
November 15 14.0.7162.5000 3101547 3101534 3101530 y
December 15 14.0.7164.5000 3114418 3114408 3114405 y
January 16 no CU released. n/a n/a 3114556 y Blog
February 16 14.0.7166.5000 3114567 3114558 3114754 y Blog
March 16 14.0.7167.5000 3114886 3114882  3114876 y
April 16 14.0.7168.5000 n/a 3114995 3114992 y
May 16 14.0.7169.5000 n/a 3115126 3115122 y
June 16 14.0.7170.5000 n/a 3115245 3115242 y MS16-70
July 16 14.0.7171.5002 3114890 3115319 3115316 y MS16-088
August 16 -not released- n/a n/a n/a n/a n/a n/a
September 16 14.0.7173.5000 3115477 3115473 3115470 y MS16-107
October 16 14.0.7174.5001 n/a 3118387 3118383 y MS16-121
November 16 14.0.7176.5000 n/a 3127957 3127952 y MS16-133
December 16 14.0.7177.5000 3118391 3128036 3128033 y MS16-148


Bildergebnis für notice  Note:
Due to early posting, sometimes the KB-articles and Descriptions for the updates are not directly working!
So please expect some delay in final publishing of the KB’s!  But the Download Links should work almost immediately!

As usual, the SharePoint 2010 Products Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” should be executed on every server in the farm following the update installation.

Regarding more detailed Info about the Build number shown in your central admin -> servers in farm’s site copmared to what you see on the KB-articles,
Please see here for more:

New! PowerShell script to display version info for installed SharePoint product and language packs

Bildergebnis für notice  Note: For SP2 2013 and June 2013 CU:
==> List of all SharePoint 2010 and Office Server 2010 SP1 packages

Background Information of Cumulative Update (CU)

Cumulative update packages for Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 containing hotfixes for the issues that were fixed since the release of SharePoint foundation and SharePoint Server 2010. ´
They are sometimes also called “Uber Package”.

After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” in command line.
This needs to be done on all servers in the farm with SharePoint 2010 installed.
As usually, you should start with the server, hosting the central admin and finishing it there, after all other servers has been updated as well!
The other servers now can run the psconfig wizard in parallel (on MOSS we had to run them sequentially, one by one).

Please see also here for more general info: Common Question: What is the difference between a PU, a CU and a COD?
See also “SharePoint patching demystified”

Recommended Update sequence of packages:

As commented by the escalation folks at Microsoft, it should be sufficient to apply only the SharePoint Server2010 “Uber” packages (aka MOSS14; SPS2010) as these contains the SharePoint Foundation packages (aka WSSv4; MSF2010) as well. But still there is a recommendation to stick on the “old common” approach…

Resource: SharePoint Server 2010, SharePoint Foundation 2010 – Updates | TechNet

Best practice (this is my opinion and is the result of daily support challenges and issues, that are related to this process!)

For any given build you may find that it is not necessary to install a SharePoint Foundation 2010 update before you install a SharePoint Server 2010 update. This flexibility in the installation sequence is part of the software update system design. However, there might be times where it is necessary to remove this flexibility in order to properly fix a specific issue.

As per this Link now:
“…it is no longer necessary to install the SharePoint Foundation cumulative update and then install the SharePoint Server cumulative update.”

Well yes, its true and you can do so if it is more applicable for your Environment. but I still may recommend to follow as above to keep the best consistency for any updates as well for future.
But yeah, if you don’t want to go the extra step, for common CU updates, the server package (SharePoint) or the full Project Server package suffices all your needs, 😉

Slipstreamed installation and updates:
How to create a slipstreamed installation source:

Be careful when you use SharePoint slipstreamed installations!   – by Jie Li

Project Server 2010:
Updates for Project Server 2010
Blog of Brian Smith
Project Server Admin blog

Microsoft Project Support Blog
Service Pack 1 for Microsoft Project Server 2010 (KB2460047)

Service Pack 2 for Microsoft Project Server 2010 (KB2687452)
Most Recent Project Server updates:

Ee721049.note(en-us,office.14).gifRemember!  -> SP1 is a pre-requisite for the Office 2010 February 2013 CUs.

Language Packs:
Deploy language packs (SharePoint Server 2010)
Deploy language packs (SharePoint Foundation 2010)
Install Language Packs for SharePoint Server 2010
Install available language template packs (SharePoint Foundation 2010)
Install available language template packs (SharePoint Server 2010)
Install SharePoint 2010 Language Pack on Windows 7   (PDF)
2010 Server Language Packs for SharePoint Server 2010, Project Server 2010, Search Server 2010, and Office Web Apps 2010

Language Pack SP1

Language Pack SP2

Ff182925.Important(en-us,office.14).gif Note:
Installing language packs on the Web servers
After you install the necessary language files on the Web servers, you can install the language packs. Language packs are available as individual downloads (one download for each supported language). If you have a server farm environment and you are installing language packs to support multiple languages, you must install the language packs on each of the Web servers.

Ff182925.Important(en-us,office.14).gif Important:
The language pack is installed in its native language. For example, the Russian language pack executable file is in Russian…

SharePoint Foundation 2010 language packs are not required for SharePoint Server 2010 (

Filter Packs:
Microsoft Office 2010 Filter Packs

Office Web Apps for SharePoint 2010:

The office Web apps are not like the SharePoint Server updates. They are mostly released either as a single hotfix/update, a security fix or sometimes even as a bulk pack.
So please consider to check via the Windows update services, the Office Team Blogs as listed below and/or via the links from the below table

The Updates for Office Web apps are not maintained in detail like the SharePoint CU updates in this post! I’m only lisitng the most important or Service Packs,
so please apologize if not all updates or not the most recent news are published just-in-time.
If in doubt, run the windows Update service on your Server, hosting the Office Web Apps and check if there is any office web app offered.   😉

See also these blogs and posts for more info:

Office Web Apps for SharePoint 2010 Update overview: Links: Notes:
Service Pack 1 for Office Web Apps n/a
Service Pack 2 for Office Web Apps Known issues

As usual, after you finish applying the updates, run the SharePoint 2010 Products Configuration Wizard,
or from a command line, on each server in the farm:

psconfig -cmd upgrade -inplace b2b -wait

Additional or related resources:

Please send me a comment, if you find a mistake or dead link here,
Thx, Steve  😉

69 thoughts on “SharePoint 2010 Build Numbers (Cube Sheet)

  1. @Steve
    Thanks for the reply. The link in the OWA section does point to the "Update Office Web Apps (Installed on SharePoint 2010 Products)" which has not been updated since 2011 and describes SP1 as the most up-to-date version. So unless there have been no patches
    since 2011 (which seems impossible given that SP2 is out) that page is very out-of-date.

    Also, are OWA hotfixes ever rolled up, or does patching OWA to the most up-to-date version involve scouring for all the past hotfixes and downloading and installing them individually? Take this KB article for example: in regards to OWA. Is the only way to patch this security vulnerability always going to be to install that specific hotfix or would it be resolved through any other
    hotfix or rolled into a later patch?


  2. @Steve

    How do I determine the most recent versions of OWA for SharePoint 2010? The link listed for "Update Office Web Apps (Installed on SharePoint 2010 Products)" points to an article from 2011. Once I installed SP2, my version numbers for all of OWA went to "14.0.7015.1000"
    but subsequent CU installs have not modified this version. I am currently under the impression that CUs do not patch OWA and it must be patched separately. How do I determine the most recent version and where should I get the updates?


  3. Pingback from June 2014 CU for SPS2010/Foundation – Steve Chen [MSFT] Sr. Support Escalation Engineer – Site Home – TechNet Blogs


  4. Pingback from June 2014 CU for SPS2010/Foundation – Steve Chen [MSFT] Sr. Support Escalation Engineer – Site Home – TechNet Blogs


  5. Pingback from June 2014 CU for SPS2010/Foundation – Steve Chen [MSFT] Sr. Support Escalation Engineer – Site Home – TechNet Blogs


  6. Pingback from June 2014 CU for SPS2010/Foundation – Steve Chen [MSFT] Sr. Support Escalation Engineer – Site Home – TechNet Blogs


  7. Pingback from June 2014 CU for SPS2010/Foundation – Steve Chen [MSFT] Sr. Support Escalation Engineer – Site Home – TechNet Blogs


  8. Pingback from June 2014 CU for SharePoint 2013 – Steve Chen [MSFT] Sr. Support Escalation Engineer – Site Home – TechNet Blogs


  9. Pingback from SharePoint Sicherheitshinweis: Installation Sicherheitsupdate | Fragen zu SharePoint und Cloud-L??sungen?


  10. Pingback from SharePoint Sicherheitshinweis: Installation Sicherheitsupdate | Fragen zu SharePoint und Cloud-L??sungen?


  11. Pingback from SharePoint Sicherheitshinweis: Installation Sicherheitsupdate | Fragen zu SharePoint und Cloud-L??sungen?


  12. Pingback from SharePoint Sicherheitshinweis: Installation Sicherheitsupdate | Fragen zu SharePoint und Cloud-L??sungen?


  13. Pingback from SharePoint Sicherheitshinweis: Installation Sicherheitsupdate | Fragen zu SharePoint und Cloud-L??sungen?


  14. Pingback from SharePoint Sicherheitshinweis: Installation Sicherheitsupdate | Fragen zu SharePoint und Cloud-L??sungen?


  15. @Reinhard and Reinhardl:
    Hi Guys, I'll check that and will get back to you asap.
    Normally, the DLL Version is the one that Shows up in Central Admin and should be equal to the one from the KB. It might be possible that we have just patched the DLL to a lower build whereas other important files are being really on the mentioned Build.
    Please go to the Folder  C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14ISAPI  and verify all files with Microsoft.SharePoint.*  for the Version.


  16. @Steve
    Hi, i also have this Versionnumber 14.0.7108.5000 after SP2 and oct Cu on a freshly installed System (1x Frontend, 1x Backend). I am running PSConfig after each step. Microsoft.Sharepoint.dll is also Version 14.0.7108.5000.


  17. @SharePoint Redneck, Steve
    Hi, i am also getting database Version 14.0.7108.5000 after a Installation of SP2 and Oct CU on a fresh installed System.
    The Dll you mentioned in your post has also this Versionnumber.


  18. @SharePoint Redneck:
    Hi, the file Version should be the one as mentioned in my post above. From the KB article 2825786 (  you will also
    see the file ubersrv2010-kb2825786-fullfile-x64-glb.exe with version 14.0.7110.5000.
    Did you run the PSConfig wizard after install?  
    What Build Version is shown in central admin, under Servers in farm?
    What Version do you see at the [Microsoft.SharePoint.dll], found in C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14ISAPI  ???


  19. As I was installing the Oct CU on a new farm (after installing SP2 and all that), I am getting a database version of 14.0.7108.5000 instead of 14.0.7110.5000 noted above.  Just an FYI unless I am looking in the wrong place.  Thanks.


  20. Thanks for the answer Steve.
    That environment was a mess and i Remade it.
    Now it is ok.
    Sorry by the late answer.
    By the way, great article.


  21. Hi,  i have the Aug 11 CU installed on my environment 14.0.6109.5002 (not 14.0.6109.5005) as posted here.
    And I am trying to update to april 13 CU version 14.0.6137.5000, and I am receiving the message: "The expected version of the product was not found on the system".
    But the pre Prerequisites as informed on KB page are only the SPS2010 SP1 and SPF2010 SP1, and they are already installed.
    What am I missing?


  22. Nice list and other useful information.  Thank you for putting it together and keeping it up to date.
    I have a question about language pack build numbers.
    After installing Dec. 2012 CU on all servers in the farm, I checked the Patch Levels Status (http://servername:port/_admin/PatchStatus.aspx) and see that while core sharepoint and the databases are 14.0.6131.5003, the various language packs are mostly 14.0.6029.1000 (SP1), but some items for each language pack range from 14.0.6029.1000  to 14.0.6131.5003.
    Shouldn't all the build numbers be the same?
    Or are their specific CUs/Patched for the language packs that need to be applied after installing a CU?
    Thank you,


  23. Hi Kristin: as many times already posted, the version is based on that file with the highest patch build. The version shown in central admin, config DB or from the Microsoft.sharepoint*.* dll’s can vary and does not necessary reflect the exact same number
    as outlined in the respective KB article. Don’t worry, it’s always confusing folks 😉


  24. HI Dennis, this is probably a security fix that might have had some sharepoint bits updated as well. Actually it is a build post SP2 already and the next higher CU would have been October 2013 CU = 14.0.7110.5000.


  25. Hey Bo,

    yes, you can install SP2 on top of SP1+August 2012 CU. Once updated to SP2, I’d recommend to install soon the next most recent CU as well.
    See the table above for latest info.

    cheers; Steve


  26. (logged in before commenting this time)
    Hi Steve
    Thanks for putting together this post, I use it religiously
     >Best Practice
     >I personally recommend that you always install SharePoint Foundation 2010 patches before installing SharePoint Server 2010 patches.
    This best practice is no longer correct. As per this link it has changed:…/ff800847.aspx
     >The packaging of cumulative updates changed as of August 31, 2011
     >As a result of the new packaging, it is no longer necessary to install the SharePoint Foundation cumulative update and then install the SharePoint Server cumulative update.
    So can you please strike-through that Best Practice and add that comment and link
    Cheers, Adam Cogan


  27. A recent Question about updating WAC (aka Office web app Server) reached me and here is the conversation:
    My customer is in SharePoint Server 2010, with August 2012 CU. They have Office Web Apps SP1 in place. They are thinking of updating Office Web Apps. I think that latest that we have that’s publicly available is June 2011 CU (…/2553919). According to the KB article, this is a hotfix but we refer to it as a CU. Since it is a hotfix, it’s a single update. Does this mean that the customer should have installed a CU prior to June 2011 CU?
    The referenced KB is a single hotfix for a specific issue with Microsoft PowerPoint 2010 by using Web apps. So it is not a full WAC packages nor is it a CU.
    However, unfortunately there is no matrix or alignment between the WAC updates and the default SharePoint CU’s.
    So in case you want have them anyway,
    There are no “server/rollup packages” for Office Web Apps, and none of the SharePoint packages will contain Office Web App Fixes. You must download each individual Office Web App Patch and apply it.
    The only direct mapping is the Service pack level and all other “hotfixes” are single packs mostly for a certain version i.e. Excel, PowerPoint, Access etc. and they are only recommended to be installed
    …it is being referred as June "CU" in this blog:…/patching-office-web-apps-to-sp1-and-june-cus-including-sharepoint-server-2010.aspx
    Step 1: SharePoint Server 2010 SP1:…/2460045
    Step 2: Office Web Apps SP1:…/2460073
    Step 3: SharePoint Server 2010 June CU:…/2536599
    Step 4: Office Web Apps June CU:…/2553919
    The blog you mentioned, describes the special circumstance with our SP1 and June CU geared up to each other and hence needs to be applied in that order 😉
    For all later CU’s for SharePoint, there is no mapping to single hotfixes for office web apps.
    The WAC fixes are mostly security fixes and should come via WSUS or Windows online update anyway.
    If not, its only recommended to install these fixes if you having the described problems.
    There appear to be a couple of fixes for office web apps fix for October 2011 and they are KB 2687562, KB 2687617, 2760391, and 2687614 but these are for single product versions like one for excel, PowerPoint a.s.o.  None of them is considered as a full WAC rollup packages and hence each one considered only for a specific issue.
    Hope that helps,


  28. @Jonny Smooth Bravo:
    sorry for delayed answer. although you found already the other post. But just to get back to your first question:
    "Why is this so difficult, why are there not any indication of these issues mentioned in any of the KB articles for the CU or service pack?"
    Service Packs are usually intensive tested and also being passed through Beta testing stages same as our main porducts. But even then, we cannot find each and every bug Prior to it's occurence if it is not reported during beta nor might be fixed Prior public release.
    There are lots of circumstances that can Impact and change the behavior on installing SP's which we cannot test all possible Scenarios.
    CU's are not stress tested same as SP's and hence can have more often regressions and/or other unexpected issues.
    Sometimes, we find Problems after Publishing and by reports from Customers when doing the updates.
    These we will follow up asap and of course trying to do the updates in either our Escalation Engineer's Posts and/or changing the KB's etc. as quickly we can
    but this might often takes some time and will not always reach you right in time while you do the update.
    That's why we always pray to "test it before applying into production, learn, repeat testing"
    HtH,  😉


  29. Hi Kyle,
    as already said, I haven’t had time to maintain it accurately but did some changes today, that will list at least some more links and info’s along with the two service packs, already released yet.

    So if SP1 + SP2 for office web apps is installed, the further updates following SP2 may either being deployed via WSUS or security fixes which are usually announced by the MS-Bulletins news letter.

    Please use it "as is" since I don’t have enough time to iterate through all the content to list up and keep it current with all released updates in particular.
    Hope that helps a bit,
    cheers, Steve


  30. Hi Tom,
    depending on what the fix contains, not all files/DLLs will be patched/updated. If you check the Microsoft.sharepoint.dll file version, this reflects the most recent update status. For language packs, usually also service packs will be served and needs to
    be installed inline with the SharePoint patch level. So if you have SharePoint SP1+ AND LP Sp1 applied as well, still not all files would show up the same version, so this wouldn’t be a mistake. finally the CU in general are commonly "global" means they are
    not language specific and will patch the installed language files too. All related information on language packs can be found here:…/3293169.aspx

    Hope that helps and answers your Q.
    Cheers, Steve


  31. @steve – Stefan (…/sharepoint-server-2010-service-pack-2-has-been-released.aspx)
    indicated I could install June 2013 CU on top of RTM, and then Service Pack 2, but I’m getting a messaging indicating "The expected version of the product was not found on the system" the only successfully way I have been able to accomplish this is via the
    way you mentioned above?
    Why is this so difficult, why are there not any indication of these issues mentioned in any of the KB articles for the CU or service pack?


  32. Hi Vince,
    you're right but the list should not imply the install order bat rather giving a cube of all updates since RTM, but thnx, I'll correct this right away to not confuse any others further.
    Please note my changed post above…
    cheers, Steve


  33. Hi Adam,
    many thanks for your commitment to my blog and your comments. Well yes it is not necessary anymoer to install both parts of the pacakges (foundation + server) but it still becomes important on certain scenarios and combinations and may casue unexoected issues if you dont do so.
    For short:  yes, it is sufficient just to install the Server CU or Project packages as they contain all required bits. But it is just an extra mile but not a problem when you still follow my recommendations.
    Its just for future cases and for consistency at all to be on the secure side. However, as written above, its just my personal view and also have been stated so on the sustained engineering blog whch are the folks that creates the fixes 😉
    anyway, thnx, cheers and greetz, Steve


  34. @Reinhard and Reinhardl:
    so it seems that although we have on the KB’s 2825786 and 2825824 that this is build 14.0.7110.5000, the Microsoft.sharepoint.dll and Microsoft.sharepoint.portal.dll are of Version 14.0.7108.5000

    – thats correct and also shown in central admin – manage Servers in farm.
    The build Version 14.0.7110.5000 is pulled from the and is then highest build in the oct. 2013 package, thats why its confusing with the given build number from the KBs.

    It’s all ok but just missleaded statement in the KBs
    cheers, Steve


  35. Kyle:

    OWA never was part of any CU for SharePoint. It is an independent update stream. You may find more info on most recent updates above in the "Office Web App Section". Since there is no frequency like the CU’s it is more like a "hotfix" being released via KBs.
    I was working on a similar sheet but haven’t found the time yet to maintain it.
    HtH, Cheers, Steve


  36. A recent question to my sheet:
    Q:  On this post and several other sites I see the build numbers 14.0.4762.1000 and 14.0.5123.5000 listed but no 14.0.5123.5002 listed.
         Is there a reason 14.0.5123.5002 isnt listed in your article?
    A:  This fix (14.0.5123.5002) is a single hotfix for a specific issue (…/2398734) and is included in the October CU!
        On my sheet, there is only listed the each cumulative update or so called “Uber-Packages” which are containing all fixes provided
        in-between the regular CU frequency.
    When you install the cumulative package, you’ll have included all single fixes, newly released since last prior CU.
    So in your case, if you install the Oct. CU, the mentioned fix is included.
    Hope that answers your Question 😉


  37. Hi Cherina,
    I'm assuming you mean with "OWA" NOT the 'Outlook Web Access' but 'Office Web App', right?
    Well,  there is no direct mapping to CU's. Only at Service Pack Level, the updates should be aligned. The 'Office Web App' updates are released separate and in my post above you'll find all Web App updates published so far. if ther eis a new one, I'll add it here, else you can also simply search for updates on…/search.aspx
    Hope that asnwers your Question 😉


  38. @Marcos
    Are you sure, that your last CU was properly installed? Since you have installed the Aug 11 CU with 14.0.6109.5002, the error might come from a check against the updated Version of the aug. 11 CU with 14.0.6109.5005. This was a fixed Versions as it might had a Regression in the 5002 build and hence, the update probably check for the increment and may prevent you here from installing any higfher bits. Please try and get the fresh Aug.11 Cu on 5005 Build and install it on top, this should help to get the next higher CU's after. If this still does not work, then you maybe have another issue and this needs to be investigated within a MS Service request.
    HtH, cheers, Steve


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s