Skip to main content ↑ ↓
Topic: ElkArte 1.0 Release Candidate 1 - release notes (Read 16800 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

ElkArte 1.0 Release Candidate 1 - release notes

Don't forget the second part of the release notes: the list of know issues.

This is a summary of the major fixes and improvements since the previous release, if you are interested in the details, you can have a look at the repository, the detailed list of commits and changes is too long.

Major changes since ElkArte Beta 2:
  • Added Drag&Drop to attach files (not supported by some old browser like IE8 and 9, in that case only the basic interface is provided)
  • Dropped compatibility with php 5.1, now the minimum is set to 5.2, even though 5.3 is highly recommended because it will be the minimum version for ElkArte 1.1
  • Admin panel news and the detailed versions are now grabbed directly from GitHub
  • Several improvements and fixes for the theme
  • The {db_prefix}admin_info_file table and the relative code (including the fetchFiles scheduled task) is now deprecated, the table has not been removed in order to reduce possible issues
  • Several tweaks to the language strings
  • Completed standardization of class naming
  • Language strings now don't have any concatenation
  • tons of bug fixes

1345 commits and a total of 418 files have been changed since ElkArte beta 2.
Last Edit: July 12, 2014, 01:13:19 pm by emanuele
Bugs creator.
Features destroyer.
Template killer.

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #1 –

I am eagerly waiting for the stable release. When can we expect RC1 ?

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #2 –

When it's ready. :D
Master of Expletives: Now with improved family f@&king friendliness! :D

Sources code: making easy front end changes difficult since 1873. :P

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #3 –

My first hope is mid-March, but I tend to feel it's a bit early... dunno.
Bugs creator.
Features destroyer.
Template killer.

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #4 –

Mid- March would be great, but I'm thinking more towards April 1st.

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #5 –

April 1st was my plan for final... O:-) :P
Bugs creator.
Features destroyer.
Template killer.

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #6 –

lol guys.  :P

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #8 –

I was going to bump the version, but I faced an existential crisis:
Code: [Select]
@version 1.0 RC 1
or
Code: [Select]
@version 1.0 Release Candidate 1
Tough question...

I'm tempted to use the second just because it looks better in titles (e.g. help and ssi_examples), so we don't have exceptions, but the first is shorter and nicer...

Which one do you prefer? O:-)
Bugs creator.
Features destroyer.
Template killer.

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #9 –

Don't you have real polls here?

The first, as anyone looking at the code is probably a developer and knows what RC is. If they don't, they usually know how to use Google.

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #10 –

Quote from: Eliana Tamerin – Don't you have real polls here?
LOL .. Hey lets have a team vote :P

Are we just talking about the version in the script headers (don't want to bork pacman and the like) ... for the headers the release candidate looks a bit nicer ... like Beta 1 instead of B 1


Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #11 –

Screw polls!
Never liked such silly method to take decisions. :-\

Script headers and for example the title attributes of the help files and ssi_examples.
But also $forum_version that at the moment uses Beta 2 I think.
Bugs creator.
Features destroyer.
Template killer.

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #12 –

I'm not sure how compareVersions would deal with it if the $forum_version was not RC, that uses alpha, beta, rc  as far as I recall.   The rest could use the nicer format with any issues.

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #13 –

i  say second one to  be different from norm
Bryan Deakin
Former Project Manager/Customiser/Marketing @ SMF

Re: [WIP] ElkArte 1.0 Release Candidate 1 - release notes

Reply #14 –

https://github.com/elkarte/Elkarte/pull/1544
Bugs creator.
Features destroyer.
Template killer.