Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Elgg development
Home
+ new post
About this group
Join this group
Message from discussion New Blog Post -- How to make Elgg 1.7 the most stable yet
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Follow-up To:
Add Cc | Add Follow-up to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers that you hear
 
Brett Profitt  
View profile   Translate to Translated (View Original)
 More options 7 Oct 2009, 13:21
From: Brett Profitt <br...@elgg.com>
Date: Wed, 7 Oct 2009 13:21:06 -0400
Local: Wed 7 Oct 2009 13:21
Subject: Re: [Elgg development] Re: New Blog Post -- How to make Elgg 1.7 the most stable yet
Print | View thread | Show original | Report this message | Find messages by this author
I like it.  Talked to the team and still working out the details, but
it will be something like this:

In 1.7 elgg_*() functions are new and improved.  Old functions will
rewrite to elgg_*() functions preserving all param order and oddities
of the original functions where applicable.

In 1.8 old functions are deprecated.

@Alivin -- Our release policy is that bugfix releases (3rd decimal) do
not make changes to the API, but major and minor (1st or 2nd decimals)
can.  This is a minor release instead of a bugfix release because it
*does* change the API.

----
Brett Profitt
Elgg Core Engineer

Skype: brett.profitt
Twitter: http://twitter.com/brettprofitt

On Wed, Oct 7, 2009 at 11:45 AM, Alivin70 <alivi...@gmail.com> wrote:

> 2009/10/7 Kevin Jardine <kevinjard...@gmail.com>

>> A lot depends upon how the refactoring is done. If it creates new
>> functions and a good document on how to use them and migrate existing
>> functions over time, and does not change/break the existing API, then
>> many of my clients would sleep much better at night!

> I agree with Kevin.
> In such bugfix release new functions can be added, optimizations can be
> made, and so on.
> But all existing functions must be the same (same parameters and return
> value). Eventually they can be marked as "Deprecated" (as in Java) and
> removed in a future release.

> --
> ______________________
> mail: alivi...@gmail.com
> web: www.vinsoft.it


 
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google