jcracknell wrote:months are supposed to be capitalised e.g. May and not may
Can you read and understand it ? If so, it's fine
jcracknell wrote:months are supposed to be capitalised e.g. May and not may
Jinx wrote:Roadmap updated.
Maintenance Release Number (1.1.X)
An increment of the maintenance number usually indicates bug fixing within the minor release and possibly small enhancements and limited new features.
Jinx wrote:jcracknell wrote:months are supposed to be capitalised e.g. May and not may
Can you read and understand it ? If so, it's fine
fireman wrote:Jinx wrote:jcracknell wrote:months are supposed to be capitalised e.g. May and not may
Can you read and understand it ? If so, it's fine
did the release of beta-2 include a time machine. it says it was released may 2006. wow a whole year has passed and I missed it!
must be that pesky time-space continuum bug!!
AmyStephen wrote:...refactor an entire hugely popular, internationally acclaimed, award winning open source CMS, provide backward compatibility *and* embrace a modern MVC application architecture, give it to the world for free as in beer and liberty...and all they notice are the grammar errors on the roadmap page?
Hang in there, Dev Team!
jcracknell wrote:Trouble is Amy I teach kids (not baby goats before you correct me on my grammar!). My grammar is bad enough, I live in rural Suffolk!
So you might may (as in could) release something, or it might be a May release :-)
Faeton wrote:Congatulations to the developer's team on this milestone for the Joomla community! I think Joomla is by far the best environment in the open source community, at least for the site designers like me - not very well educated in programming, but willing to offer their clients a neat site that answers their needs.
So far, the one thing I tried to see concerning the 1.5 takeoff has been the tribute video. And guess what? It refused to play on Safari 2.0.4 (PowerMac G5, OSX 10.4.... Please, test this version overe and over again, to ensure that even the sparse viewers on a Mac can use Joomla!
Jeroen van Heemskerck Duker, Netherlands
Faeton wrote:So far, the one thing I tried to see concerning the 1.5 takeoff has been the tribute video. And guess what? It refused to play on Safari 2.0.4 (PowerMac G5, OSX 10.4.
am12976 wrote:Excellent Job Team!I'm Having A Little Problem Though.I Use Yahoo Hosting And It Doesn't Allow Me To Upload The Fowllowing File & Folder:
\includes\js\jscalendar-1.0
\libraries\simplepie\compatibility_test\COMPATIBILITY README.txt <<=Not Really Important
I'd Be Thankful If You Could Do Something About It.
c0rinne wrote:Does anyone have any idea what the degree of convertibility from 1.012 to 1.5 (final) will be. Meaning, how difficult will it be for the average novice to convert, say their layout, to 1.5?
Because, from what I've read, it doesn't look like the prospects are good for me.
Does anyone have any idea what the degree of convertibility from 1.012 to 1.5 (final) will be. Meaning, how difficult will it be for the average novice to convert, say their layout, to 1.5?
Quote from: cord on May 05, 2007, 09:45:13 AM
I mean: Will the contents created in Joomla Beta-2 be usable and unaltered after updating to 1.5 stable?
I'm not talking about third-party-components, it's just about sections, categories and content articles!
Yes, you can. With the release of beta 2 we have frozen the API's and database scheme. For 3P developers this means that now is the time to start working on their new extensions or make their existing extensions compatible. People that want to develop websites can already start their development process (designing template, putting content in, ....), just at least wait until we released a first release candidate before putting the site in a production environment.
Jinx wrote:Yes, you can. With the release of beta 2 we have frozen the API's and database scheme. For 3P developers this means that now is the time to start working on their new extensions or make their existing extensions compatible. People that want to develop websites can already start their development process (designing template, putting content in, ....), just at least wait until we released a first release candidate before putting the site in a production environment.