<?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: Joomla! development news: an interview with Jen Kramer, lynda.com author</title>
	<atom:link href="http://blog.lynda.com/2011/02/23/joomla-development-news-an-interview-with-jen-kramer-lynda-com-author/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.lynda.com/2011/02/23/joomla-development-news-an-interview-with-jen-kramer-lynda-com-author/</link>
	<description>the blog of lynda.com</description>
	<lastBuildDate>Mon, 20 May 2013 15:07:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Jen Kramer</title>
		<link>http://blog.lynda.com/2011/02/23/joomla-development-news-an-interview-with-jen-kramer-lynda-com-author/comment-page-1/#comment-157232</link>
		<dc:creator>Jen Kramer</dc:creator>
		<pubDate>Thu, 12 May 2011 11:00:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lynda.com/?p=6307#comment-157232</guid>
		<description><![CDATA[Hi everyone -- thanks for the comments! I&#039;ll address each:

@Hussain: Sorry if the development path isn&#039;t clear. 1.6 becomes 1.7; 1.7 becomes 1.8. 1.5 is maintained while this is happening. You will be able to jump from 1.5 to 1.8, or you can follow the path to 1.8 via 1.6 and 1.7.

The reason for maintaining 1.5 while having short releases for 1.6 and 1.7 is so that development is happening while those who need long-term stability can also have that. Joomla&#039;s release cycle is patterned after Ubuntu&#039;s.

@PatVB: The template clubs are, for the most part, keeping up with the development of Joomla. 1.7 is currently in development. I do not expect templates will change much from 1.6 to 1.7. However, templates are VERY different between 1.5 and 1.6.

@diver165: The Joomla project can be pretty bad at communicating their intentions. One of their problems is communicating across too many channels, and then no one can find what was said later. The release schedule is very much in the open, and the development process is as well. This post is a good summary of all of the places where things were said about 1.7 (and later) development:

http://people.joomla.org/groups/viewdiscussion/1070-Beyond+16.html?groupid=458

@chris: Your summary of the intentions of the Joomla project is correct. The theory is that a 1.6.3 migration to 1.7.0 is a &quot;one click&quot; process. However, the project does have a history of having some difference between theory and reality. The leadership knows that easy migrations are critical to making this work, so they are working on making the migration process easy... at least for core features.

As always, the tricky part is with the extensions. I am not a developer, and I can&#039;t say whether the migration for 1.6 to 1.7 from a 3rd party extension point of view will be trivial or a nightmare. It may even depend on the extension. Pay close attention to what&#039;s being discussed over the next 2 months to get a better picture of what&#039;s happening.

The Joomla community has been burned by migrations before, and they are concerned about charging clients lots of money to complete tasks that are, in theory, supposed to be easy. We will have a much better picture about how this plan works going forward, after the 1.7 release.

@Hussain: I don&#039;t know whether 1.6 extensions will work for 1.7 or not. Right now, they are picking features to include in 1.7 and starting the debug process for the July release. We should know the answer to this question shortly.

Thanks all,
Jen]]></description>
		<content:encoded><![CDATA[<p>Hi everyone &#8212; thanks for the comments! I&#8217;ll address each:</p>
<p>@Hussain: Sorry if the development path isn&#8217;t clear. 1.6 becomes 1.7; 1.7 becomes 1.8. 1.5 is maintained while this is happening. You will be able to jump from 1.5 to 1.8, or you can follow the path to 1.8 via 1.6 and 1.7.</p>
<p>The reason for maintaining 1.5 while having short releases for 1.6 and 1.7 is so that development is happening while those who need long-term stability can also have that. Joomla&#8217;s release cycle is patterned after Ubuntu&#8217;s.</p>
<p>@PatVB: The template clubs are, for the most part, keeping up with the development of Joomla. 1.7 is currently in development. I do not expect templates will change much from 1.6 to 1.7. However, templates are VERY different between 1.5 and 1.6.</p>
<p>@diver165: The Joomla project can be pretty bad at communicating their intentions. One of their problems is communicating across too many channels, and then no one can find what was said later. The release schedule is very much in the open, and the development process is as well. This post is a good summary of all of the places where things were said about 1.7 (and later) development:</p>
<p><a href="http://people.joomla.org/groups/viewdiscussion/1070-Beyond+16.html?groupid=458" rel="nofollow">http://people.joomla.org/groups/viewdiscussion/1070-Beyond+16.html?groupid=458</a></p>
<p>@chris: Your summary of the intentions of the Joomla project is correct. The theory is that a 1.6.3 migration to 1.7.0 is a &#8220;one click&#8221; process. However, the project does have a history of having some difference between theory and reality. The leadership knows that easy migrations are critical to making this work, so they are working on making the migration process easy&#8230; at least for core features.</p>
<p>As always, the tricky part is with the extensions. I am not a developer, and I can&#8217;t say whether the migration for 1.6 to 1.7 from a 3rd party extension point of view will be trivial or a nightmare. It may even depend on the extension. Pay close attention to what&#8217;s being discussed over the next 2 months to get a better picture of what&#8217;s happening.</p>
<p>The Joomla community has been burned by migrations before, and they are concerned about charging clients lots of money to complete tasks that are, in theory, supposed to be easy. We will have a much better picture about how this plan works going forward, after the 1.7 release.</p>
<p>@Hussain: I don&#8217;t know whether 1.6 extensions will work for 1.7 or not. Right now, they are picking features to include in 1.7 and starting the debug process for the July release. We should know the answer to this question shortly.</p>
<p>Thanks all,<br />
Jen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hussain</title>
		<link>http://blog.lynda.com/2011/02/23/joomla-development-news-an-interview-with-jen-kramer-lynda-com-author/comment-page-1/#comment-155371</link>
		<dc:creator>Hussain</dc:creator>
		<pubDate>Mon, 09 May 2011 17:55:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lynda.com/?p=6307#comment-155371</guid>
		<description><![CDATA[Chris hi, 

when you talk about security updates do you mean that templates and extensions developed for 1.6.X do not need to be updated to work for 1.7.X or 1.8.X? Is it that what you mean?  Do you mean extensions developed for 1.6.X automatically will work for 1.7.X?

Please explain, the answer is indeed important to us... It is updating extensions and templates that concerns us. Thank you.]]></description>
		<content:encoded><![CDATA[<p>Chris hi, </p>
<p>when you talk about security updates do you mean that templates and extensions developed for 1.6.X do not need to be updated to work for 1.7.X or 1.8.X? Is it that what you mean?  Do you mean extensions developed for 1.6.X automatically will work for 1.7.X?</p>
<p>Please explain, the answer is indeed important to us&#8230; It is updating extensions and templates that concerns us. Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blog.lynda.com/2011/02/23/joomla-development-news-an-interview-with-jen-kramer-lynda-com-author/comment-page-1/#comment-152717</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 04 May 2011 22:39:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lynda.com/?p=6307#comment-152717</guid>
		<description><![CDATA[The Joomla strategy haters may be right, I don&#039;t know, but the Joomla Development Team seem to be pretty smart.

First, the only support or &quot;development&quot; for J1.5 will be security updates. It is COMPLETELY normal to release and develop these while working on 1.6. Also, 1.6 is no longer being &quot;developed&quot; in the sense that they are adding features. My understanding is that, they are only doing security updates for that as well (at least from J1.6.3 on). they are really only &quot;developing&quot; 1.7. And even then, you could just as well call it J1.6.XX. It is just a number. The idea is that they are adding new features every 6 months with security updates along the way.

It seems like a MAJOR misunderstanding and mis-use of words to say that the short-term releases will &quot;not be supported&quot; after a certain date. I think this is to say that they will no longer be releasing security updates for it. That is because instead of the security update, you just need to update to the latest Joomla (i.e. J1.6.3 to J1.7.0, etc.). The word is that it should be as simple to upgrade from J1.6.2 to J1.6.3 as it will be from J1.6.3 to J1.7.0.

Am I wrong? Do I misunderstand?

The only real uncertainty and confusion I have are concerning the new features released from say a J1.6 to a J1.7. Will these added features make many J1.6 templates, extensions, plugins, etc. goof up when moving to 1.7?

It actually seems like an exciting plan, I am just concerned that the Joomla community doesn&#039;t truly understand it and is not getting behind it. This will just grid-lock things. I say we do what it takes to stay up with the J! development.

What are you thoughts? 

Chris]]></description>
		<content:encoded><![CDATA[<p>The Joomla strategy haters may be right, I don&#8217;t know, but the Joomla Development Team seem to be pretty smart.</p>
<p>First, the only support or &#8220;development&#8221; for J1.5 will be security updates. It is COMPLETELY normal to release and develop these while working on 1.6. Also, 1.6 is no longer being &#8220;developed&#8221; in the sense that they are adding features. My understanding is that, they are only doing security updates for that as well (at least from J1.6.3 on). they are really only &#8220;developing&#8221; 1.7. And even then, you could just as well call it J1.6.XX. It is just a number. The idea is that they are adding new features every 6 months with security updates along the way.</p>
<p>It seems like a MAJOR misunderstanding and mis-use of words to say that the short-term releases will &#8220;not be supported&#8221; after a certain date. I think this is to say that they will no longer be releasing security updates for it. That is because instead of the security update, you just need to update to the latest Joomla (i.e. J1.6.3 to J1.7.0, etc.). The word is that it should be as simple to upgrade from J1.6.2 to J1.6.3 as it will be from J1.6.3 to J1.7.0.</p>
<p>Am I wrong? Do I misunderstand?</p>
<p>The only real uncertainty and confusion I have are concerning the new features released from say a J1.6 to a J1.7. Will these added features make many J1.6 templates, extensions, plugins, etc. goof up when moving to 1.7?</p>
<p>It actually seems like an exciting plan, I am just concerned that the Joomla community doesn&#8217;t truly understand it and is not getting behind it. This will just grid-lock things. I say we do what it takes to stay up with the J! development.</p>
<p>What are you thoughts? </p>
<p>Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kareem</title>
		<link>http://blog.lynda.com/2011/02/23/joomla-development-news-an-interview-with-jen-kramer-lynda-com-author/comment-page-1/#comment-149359</link>
		<dc:creator>Kareem</dc:creator>
		<pubDate>Thu, 28 Apr 2011 20:18:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lynda.com/?p=6307#comment-149359</guid>
		<description><![CDATA[i dont think it&#039;s so bad. if you consider it more just a change of versioning strategy it makes more sense]]></description>
		<content:encoded><![CDATA[<p>i dont think it&#8217;s so bad. if you consider it more just a change of versioning strategy it makes more sense</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: diver165</title>
		<link>http://blog.lynda.com/2011/02/23/joomla-development-news-an-interview-with-jen-kramer-lynda-com-author/comment-page-1/#comment-144533</link>
		<dc:creator>diver165</dc:creator>
		<pubDate>Tue, 19 Apr 2011 17:08:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lynda.com/?p=6307#comment-144533</guid>
		<description><![CDATA[I honestly do not understand.

How can you still develop Joomla 1.5 and Joomla 1.6 at the same time secretely developing Joomla 1.7?  How can you honestly put out a link to Joomla 1.6 on your website and tout it to be the latest and best Joomla available, but have secret plans to only support it for 6 months?  Why go through the trouble of releasing it in the first place!!!  All you do by releasing something like this is waste time supporting and patching CMS that is marked for end of life.

I agree with the previous posters, this will be a total nightmare in keeping up with the various extensions and templates.  I honestly don&#039;t know what to tell me customers.  Some want the ACL functionality but I don&#039;t want to sell them a site that I know will be end of life by the time I&#039;m finished.

Lets here something official on the Joomla web site.  Maybe I&#039;ve just missed it.]]></description>
		<content:encoded><![CDATA[<p>I honestly do not understand.</p>
<p>How can you still develop Joomla 1.5 and Joomla 1.6 at the same time secretely developing Joomla 1.7?  How can you honestly put out a link to Joomla 1.6 on your website and tout it to be the latest and best Joomla available, but have secret plans to only support it for 6 months?  Why go through the trouble of releasing it in the first place!!!  All you do by releasing something like this is waste time supporting and patching CMS that is marked for end of life.</p>
<p>I agree with the previous posters, this will be a total nightmare in keeping up with the various extensions and templates.  I honestly don&#8217;t know what to tell me customers.  Some want the ACL functionality but I don&#8217;t want to sell them a site that I know will be end of life by the time I&#8217;m finished.</p>
<p>Lets here something official on the Joomla web site.  Maybe I&#8217;ve just missed it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PatVB</title>
		<link>http://blog.lynda.com/2011/02/23/joomla-development-news-an-interview-with-jen-kramer-lynda-com-author/comment-page-1/#comment-142317</link>
		<dc:creator>PatVB</dc:creator>
		<pubDate>Fri, 15 Apr 2011 05:17:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lynda.com/?p=6307#comment-142317</guid>
		<description><![CDATA[I am wondering what about the template clubs and how they will keep templates in all these versions: 1.5, 1.6, 1.7 and 1.8 and all within a very short time span.  I depend heavily on the template clubs to steer my clients to, and I like being able to give them a wide variety to choose from.  It just seems like it&#039;s going to be a nightmare of sorts for template designers and extension designers to keep up with this pace.

I still have a few sites in Joomla 1.0 because they are still working well and earning money, but now are really starting to show their age.  Waiting for 1.8 seems like a good idea.  What are others doing?

Pat Vanden Bosche]]></description>
		<content:encoded><![CDATA[<p>I am wondering what about the template clubs and how they will keep templates in all these versions: 1.5, 1.6, 1.7 and 1.8 and all within a very short time span.  I depend heavily on the template clubs to steer my clients to, and I like being able to give them a wide variety to choose from.  It just seems like it&#8217;s going to be a nightmare of sorts for template designers and extension designers to keep up with this pace.</p>
<p>I still have a few sites in Joomla 1.0 because they are still working well and earning money, but now are really starting to show their age.  Waiting for 1.8 seems like a good idea.  What are others doing?</p>
<p>Pat Vanden Bosche</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hussain</title>
		<link>http://blog.lynda.com/2011/02/23/joomla-development-news-an-interview-with-jen-kramer-lynda-com-author/comment-page-1/#comment-135481</link>
		<dc:creator>Hussain</dc:creator>
		<pubDate>Sat, 02 Apr 2011 00:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lynda.com/?p=6307#comment-135481</guid>
		<description><![CDATA[I do not know if it is me who is stupid or those who decide version releases of Joomla... 

If Joomla 1.5 is still will be developed parallel to 1.6 and then parallel to 1.7 and then all the garbage will be migrated to the heroic version 1.8 then my stupid question is:

Why releasing 1.6 and 1.7? why not just working with 1.5 until a stable version of so called 1.8 is released? What is the meaning of these short period 1.6 and 1.7 releases? Why all these parallel developments and confusions?

/Hussain]]></description>
		<content:encoded><![CDATA[<p>I do not know if it is me who is stupid or those who decide version releases of Joomla&#8230; </p>
<p>If Joomla 1.5 is still will be developed parallel to 1.6 and then parallel to 1.7 and then all the garbage will be migrated to the heroic version 1.8 then my stupid question is:</p>
<p>Why releasing 1.6 and 1.7? why not just working with 1.5 until a stable version of so called 1.8 is released? What is the meaning of these short period 1.6 and 1.7 releases? Why all these parallel developments and confusions?</p>
<p>/Hussain</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching using memcached
Object Caching 401/434 objects using memcached

 Served from: blog.lynda.com @ 2013-05-20 10:58:06 by W3 Total Cache -->