My main issue with 1.3 is there is some stuff that even I committed that i'm not sure i'm now happy with - hence the rational for going off of 1.2.x.
 
Having said that, my expectation would be we'd cherry pick stuff back in order from 1.3, so that it's not too much work (tedious but not too taxing).
 
For example
 
185. new column: textarea (memo) custom field type (Daryn/2010)
 
In the 2.x branch, I change the field to XL for custom_field_String, which negates the need for the schema update in 185. If you consider the reasons we've not used XL before, and the implementation ( https://github.com/mantisbt/mantisbt/commit/839f1d68bc771e579a9f48324624973e0c996ebc ), you'll probably agree that just changing the type of the existing field is the more sensible solution.
 
Schema changes in 2.x are as follows:
 
/* 185 */ $upgrade[] = array( 'AlterColumnSQL', array( '{custom_field_string}', "value XL NULL DEFAULT NULL " ) );
/* 186 */ $upgrade[] = array( 'UpdateFunction', "update_export_columns", array() );
/* 187 */ $upgrade[] = array( 'AlterColumnSQL', array( '{user}', "username C(255) NOTNULL DEFAULT ''" ) );
/* 188 */ $upgrade[] = array( 'AddColumnSQL', array( '{bug}', "description XL NOTNULL DEFAULT ''" ) );
/* 189 */ $upgrade[] = array( 'AddColumnSQL', array( '{bug}', "steps_to_reproduce XL NOTNULL DEFAULT ''" ) );
/* 190 */ $upgrade[] = array( 'AddColumnSQL', array( '{bug}', "additional_information XL NOTNULL DEFAULT ''" ) );
/* 191 */ $upgrade[] = array( 'UpdateFunction', "migrate_bug_text", array() );
/* 192 */ $upgrade[] = array( 'DropTableSQL', array( '{bug_text}' ) );
/* 193 */ $upgrade[] = array( 'DropColumnSQL', array( '{bug}', "bug_text_id" ) );
/* 194 */ $upgrade[] = array( 'AddColumnSQL', array( '{bugnote}', "note XL NOTNULL DEFAULT ''" ) );
/* 195 */ $upgrade[] = array( 'UpdateFunction', "migrate_bugnote_text", array() );
/* 196 */ $upgrade[] = array( 'DropTableSQL', array( '{bugnote_text}' ) );
/* 197 */ $upgrade[] = array( 'DropColumnSQL', array( '{bugnote}', "bugnote_text_id" ) );
/* 198 */ $upgrade[] = array( 'UpdateFunction', "check_project_hierarchy", array() );
/* 199 */ $upgrade[] = array( 'CreateIndexSQL', array('idx_project_hierarchy','{project_hierarchy}','child_id,parent_id',array('UNIQUE')));
/* 200 */ $upgrade[] = array( 'AlterColumnSQL', array('{tokens}','owner I UNSIGNED NOTNULL') );
/* 201 */ $upgrade[] = array( 'AddColumnSQL', array( '{bug_file}', "downloaded I UNSIGNED NOTNULL DEFAULT '0'" ) );
/* 202 */ $upgrade[] = array( 'AddColumnSQL', array( '{project_file}', "downloaded I UNSIGNED NOTNULL DEFAULT '0'" ) );
/* 203 */ $upgrade[] = array( 'AddColumnSQL', array( '{user_pref}', "theme C(32) NOTNULL DEFAULT '' " ) );


On Tue, Oct 1, 2013 at 8:16 AM, Damien Regad <dregad@mantisbt.org> wrote:
On 2013-10-01 05:55, Victor Boctor wrote:
> Also it would be useful to understand the list of schema changes (if any).

List of schema changes vs 12x (status for my 13x branch as of today):

184. updates to stored filters (Daryn/2010)
185. new column: textarea (memo) custom field type (Daryn/2010)
186. fix truncated custom fields name in history (me/2012)
187. new index for bug monitor table (me/2013)
188. alter column from I (int) to L (bool) to fix pgsql issue (me/2012)
189. idem



------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
mantisbt-dev mailing list
mantisbt-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev