[jQuery] How does everyone handle the constant updating of jQuery and plug-ins?

[jQuery] How does everyone handle the constant updating of jQuery and plug-ins?

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>What does everyone do to stay updated with the latest jQuery
and plug-ins<o:p></o:p>
<p class=MsoNormal>for every website?<o:p></o:p>
<p class=MsoNormal><o:p> </o:p>
<p class=MsoNormal>Up to this point, I’ve been putting my jQ in my site
folders, but the more jQ I use<o:p></o:p>
<p class=MsoNormal>on sites, the more of a chore it is to go through and update
everything with the<o:p></o:p>
<p class=MsoNormal>latest versions… and jQ and its plug-ins changes
quickly!<o:p></o:p>
<p class=MsoNormal><o:p> </o:p>
<p class=MsoNormal>Is it better to setup a central repository on my server to
hold the jQ and plug-ins?<o:p></o:p>
<p class=MsoNormal>It would seem so…<o:p></o:p>
<p class=MsoNormal><o:p> </o:p>
<p class=MsoNormal>That leads me to another question… has anyone thought
about developing some<o:p></o:p>
<p class=MsoNormal>kind of auto-updating function(s) like most software has
today for jQ and the plug-ins?<o:p></o:p>
<p class=MsoNormal><o:p> </o:p>
<p class=MsoNormal>Is it possible to use jQ to check online for updated
versions and plug-ins that are in<o:p></o:p>
<p class=MsoNormal>use on a particular system, compare the updated versions to
what’s currently on the<o:p></o:p>
<p class=MsoNormal>server and download newer versions that are deemed stable
and ready for primetime?<o:p></o:p>
<p class=MsoNormal><o:p> </o:p>
<p class=MsoNormal>I know this raises some issues with whether or not updates
will break existing code,<o:p></o:p>
<p class=MsoNormal>but the current plug-ins for a particular jQ version could
be verified by the plug-in<o:p></o:p>
<p class=MsoNormal>user as having been testing for the jQ version being
considered for download.<o:p></o:p>
<p class=MsoNormal>If all is not well, then the update doesn’t occur.<o:p></o:p>
<p class=MsoNormal><o:p> </o:p>
<p class=MsoNormal>I just think we need some kind of automated system to keep
everything up-to-date<o:p></o:p>
<p class=MsoNormal>without breaking anything versus having to manually perform
updates to jQ, et al…<o:p></o:p>
<p class=MsoNormal><o:p> </o:p>
<p class=MsoNormal>Thoughts?<o:p></o:p>
<p class=MsoNormal><o:p> </o:p>
<p class=MsoNormal>Rick<o:p></o:p>
</div>
</body>
</html>