--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To post to this group, send an email to joomla-...@googlegroups.com.
To unsubscribe from this group, send email to joomla-dev-cm...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
I agree with Andrew Eddie's proposal a while ago to adjust the dates
to something like Feb 15 / Aug 15 instead of Jan / July. Other than
that, I think we should stick with the current plan, at least until we
have more experience with it.
As far as 3.0, if we are short of time we should scale back the plans
for it. For example, the first goal might be to just get the new
platform files integrated and working and then perhaps add a new
component using UCM for 3.1 if we don't have time for 3.0.
I think we had good reasons for adopting the current strategy, including:
1. Predictable schedule for users and 3pd's.
2. Frequent releases to allow timely integration of new code, both
from our devs and from 3p libraries.
These reasons still apply in my opinion. Mark
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To view this discussion on the web, visit
> https://groups.google.com/d/msg/joomla-dev-cms/-/dZZih1BDS0QJ.
--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/joomla-dev-cms/-/Xoma6PyZwSsJ.
Michael Babker
Owner, BabDev.com
"You can't connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future. You have to trust in something - your gut, destiny, life, karma, whatever. This approach has never let me down, and it has made all the difference in my life." - Steve Jobs
Why don't we use Ubuntu style (April/October)?
They have proven experience with this version releases (twice a
year)
Ofer Cohen
On Mon, Jan 2, 2012 at 1:19 PM, Jeremy Wilken
<gnom...@gnomeontherun.com> wrote:
> I agree that fitting some of the major concepts into the x.0 releases
> probably doesn't work well in a 6 month cycle, it seems to take 2-3 months
> just to clean them up for production use and that doesn't leave much time to
> develop. The release cycle IMO is a good target, but the development cycle
> is still struggling to adjust. A lot of the changes in 2.5 were added
> in towards the end, and we are still struggling to get
> a concurrent development cycle from what I can see.
In most development groups I've worked with, things tend to be added
towards the end regardless of what mechanism you use. Agile is perhaps
the best of the lot because while things get added towards the end of
the sprint, the period is relatively short (two weeks, one month, one
lunar month, what ever tickles your fancy) which means things get
integrated quicker. They still have bugs and sometimes they don't go
in either because the change delta is so much that it would be
disruptive to include all of them incrementally.
Given this is the second release on our schedule (1.7 being the
first), I would suggest that we need to give it some more time so we
can actually get into the cadence and rhythm.
And in a sense we've had the concurrent development with both multi-db
and the Smart Search integration. Both were developed in their own
branches, merged and are now being integrated with other changes that
have been made as well. In a sense now that I think about it, this is
what we're hoping to achieve.
>
> As far as pushing it out of January, that is reasonable due to the holidays
> making it pretty hard to get folks to assist during the time leading up to a
> release. There are still a lot of people who don't get why 1.7 to 2.5 is a
> logical step, or realize we are on the new cycle, but changing it again
> would only set things back from any progress made on making that more clear.
I agree, we've made a decision so let's stick with it more than a
single release. This is the second release and we're already
considering changing things! Let's give it a year instead and see how
things pan out of the year, see how things change.
>
> I also wonder about having the Platform on a different release cycle, as we
> are seeing leading up to 2.5 that it has 11.3 but issues have come up. Why
> aren't they on the same cycle, or at least the target for every other
> Platform release should coincide with the CMS release? No matter how hard
> you try to separate the CMS and Platform, they are related and should be
> treated more closely that it seems they have been.
Last I saw CMS 2.5 was running current Platform trunk, or what will be
the next platform release. Platform 11.3 similarly was heavily
influenced by the CMS release as well. I don't see the problem you're
trying to imagine here. CMS is a client of the platform, reports up
bugs, bugs get fixed and are merged back down. The entire point is to
stop treating them as closely related and work on ensuring the
platform is more stable, CMS only items are shifted out of the
platform (already well under way) and the platform realises the long
term dream of the project that we grow our overall developer base by
making our underlying proven and tested platform completely
accessible.
Sam Moffatt
http://pasamio.id.au
--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/joomla-dev-cms/-/6xD2-RE8Y14J.
It's way too long from Christmas and Rosh Ha'Shana (Hebrew new year)� :-)
And now seriously - this is cause Gnome release version month before that and the latter is one month after X (Linux graphic engine which all desktops use to run on).
Maybe we should stick to the platform versions?
Sources:
Ofer Cohen
Ofer,
This is an interesting idea. I do agree that April and October feel right. Do you know the reasoning behind Ubuntu choosing those months? I couldn't find anything with a quick Google search.
Best,
Matt ThomasFounder�betweenbrain�Lead Developer�Construct Template Development FrameworkPhone: 203.632.9322
Twitter: @betweenbrain
Github:�https://github.com/betweenbrain
On Mon, Jan 2, 2012 at 4:59 PM, Ofer Cohen <oc...@netvision.net.il> wrote:
Why don't we use Ubuntu style (April/October)?
They have proven experience with this version releases (twice a year)
Ofer Cohen
--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
Andrew Eddie
----- Original Message -----
From: "Andrew Eddie" <mamb...@gmail.com>
To: <joomla-...@googlegroups.com>
Sent: Tuesday, January 03, 2012 3:21 PM
Subject: Re: [jcms] Re: Release cycle
> -1 to changing the 6 month cycle
> +1 to shifting 3.0 to September as a once off
>
> Andrew Eddie
>
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To view this discussion on the web, visit
> https://groups.google.com/d/msg/joomla-dev-cms/-/mHEv_xLhXacJ.