<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: A quick look at some possible changes in 3.2</title>
	<atom:link href="http://blogs.liblime.com/developers/2008/10/03/a-quick-look-at-some-possible-changes-in-32/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.liblime.com/developers/2008/10/03/a-quick-look-at-some-possible-changes-in-32/</link>
	<description>Notes on software development, open source, and library technology</description>
	<pubDate>Thu, 17 May 2012 01:39:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joe Atzberger</title>
		<link>http://blogs.liblime.com/developers/2008/10/03/a-quick-look-at-some-possible-changes-in-32/comment-page-1/#comment-5056</link>
		<dc:creator>Joe Atzberger</dc:creator>
		<pubDate>Mon, 20 Oct 2008 02:06:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.liblime.com/developers/?p=84#comment-5056</guid>
		<description>&#62; the above article seemed to say it was 3 October.

It refers to "the end of next week" having been "posted on Friday, October 3rd, 2008 at 3:25 pm".   It should be pretty clear that doesn't mean "today".  

&#62; less than a month is a pretty short time to upgrade enough of our 
&#62; largest libraries to 3.0 and gather their input to 3.2.

Then gather their input for next version or refer them to the RFCs directly.</description>
		<content:encoded><![CDATA[<p>&gt; the above article seemed to say it was 3 October.</p>
<p>It refers to &#8220;the end of next week&#8221; having been &#8220;posted on Friday, October 3rd, 2008 at 3:25 pm&#8221;.   It should be pretty clear that doesn&#8217;t mean &#8220;today&#8221;.  </p>
<p>&gt; less than a month is a pretty short time to upgrade enough of our<br />
&gt; largest libraries to 3.0 and gather their input to 3.2.</p>
<p>Then gather their input for next version or refer them to the RFCs directly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MJ Ray</title>
		<link>http://blogs.liblime.com/developers/2008/10/03/a-quick-look-at-some-possible-changes-in-32/comment-page-1/#comment-4713</link>
		<dc:creator>MJ Ray</dc:creator>
		<pubDate>Wed, 08 Oct 2008 18:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.liblime.com/developers/?p=84#comment-4713</guid>
		<description>I thought it was 10 October!  That's why I was surprised that the above article seemed to say it was 3 October.

Even so, less than a month is a pretty short time to upgrade enough of our largest libraries to 3.0 and gather their input to 3.2.</description>
		<content:encoded><![CDATA[<p>I thought it was 10 October!  That&#8217;s why I was surprised that the above article seemed to say it was 3 October.</p>
<p>Even so, less than a month is a pretty short time to upgrade enough of our largest libraries to 3.0 and gather their input to 3.2.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Galen Charlton</title>
		<link>http://blogs.liblime.com/developers/2008/10/03/a-quick-look-at-some-possible-changes-in-32/comment-page-1/#comment-4685</link>
		<dc:creator>Galen Charlton</dc:creator>
		<pubDate>Tue, 07 Oct 2008 19:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.liblime.com/developers/?p=84#comment-4685</guid>
		<description>The date of 10 October was &lt;a href="http://koha.org/cgi-bin/logs.pl?look=plain&#038;startdate=2008091213:20:26&#038;enddate=2008091213:30:26&#038;search=Search" rel="nofollow"&gt;proposed without disagreement&lt;/a&gt; during the community meeting on 12 September, mentioned again in the &lt;a href="http://lists.koha.org/pipermail/koha-devel/2008-September/008321.html" rel="nofollow"&gt;summary&lt;/a&gt; I sent to the mailing lists the same day, and noted in the &lt;a href="http://blogs.liblime.com/developers/2008/09/16/koha-community-meeting-for-32/" rel="nofollow"&gt;post&lt;/a&gt; about the community meeting that Josh made on 16 September.  Nearly a month's notice is more than sufficient to at least glance at the RFCs.</description>
		<content:encoded><![CDATA[<p>The date of 10 October was <a href="http://koha.org/cgi-bin/logs.pl?look=plain&#038;startdate=2008091213:20:26&#038;enddate=2008091213:30:26&#038;search=Search" rel="nofollow">proposed without disagreement</a> during the community meeting on 12 September, mentioned again in the <a href="http://lists.koha.org/pipermail/koha-devel/2008-September/008321.html" rel="nofollow">summary</a> I sent to the mailing lists the same day, and noted in the <a href="http://blogs.liblime.com/developers/2008/09/16/koha-community-meeting-for-32/" rel="nofollow">post</a> about the community meeting that Josh made on 16 September.  Nearly a month&#8217;s notice is more than sufficient to at least glance at the RFCs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MJ Ray</title>
		<link>http://blogs.liblime.com/developers/2008/10/03/a-quick-look-at-some-possible-changes-in-32/comment-page-1/#comment-4627</link>
		<dc:creator>MJ Ray</dc:creator>
		<pubDate>Mon, 06 Oct 2008 07:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.liblime.com/developers/?p=84#comment-4627</guid>
		<description>You post on a Friday that the RFCs need looking over by the end of the week?  I didn't even see the post until Monday morning!  We're still busy upgrading our Koha libraries to 3.0 - way to exclude them from 3.2 direction. :-(</description>
		<content:encoded><![CDATA[<p>You post on a Friday that the RFCs need looking over by the end of the week?  I didn&#8217;t even see the post until Monday morning!  We&#8217;re still busy upgrading our Koha libraries to 3.0 - way to exclude them from 3.2 direction. <img src='http://blogs.liblime.com/developers/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

