Difference between revisions of "Education Project/Effort/Replace Mozilla175"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 1: Line 1:
FIXME :  
+
This task is the first one of the application. ETA ~end august/early september
 +
 
 +
 
 +
Todo / objectives to be validated:  
 +
 
 +
- check the sources (one milestone)
 +
 
 +
- understand how cvs manages the sources ( CVS dirs)
 +
 
 +
- configure step : find information, be able to modify configure.in
 +
 
 +
- bootstrap
 +
 
 +
- build mozilla archive separately :
 +
 
 +
-- file an issue for a breaker on AMD64 (aka x86_64)
 +
 
 +
-- fix a build issue (bad compiler option maybe)
 +
 
 +
-- understand how patches are used at buildtime
 +
 
 +
- modify the makefile, and start building seamonkey  ( basic patch provided )
 +
 
 +
- define a strategy for the migration
 +
 
 +
- modify configure (replace mozilla checking with seamonkey checking)
 +
 
 +
- apply the changes progressively ( and propose tests for the QA)
 +
 
 +
- propose patches to commit the changes in several cws
 +
 
 +
- verify it works on other ports ( Mac OS X , windows )
 +
 
 +
- verify the crashes are fixed (see relevant issues)
 +
 
  
* Create a Todo
 
 
* Create a Gantt diagram / Planning
 
* Create a Gantt diagram / Planning
 
* ....
 
* ....

Revision as of 18:50, 17 July 2008

This task is the first one of the application. ETA ~end august/early september


Todo / objectives to be validated:

- check the sources (one milestone)

- understand how cvs manages the sources ( CVS dirs)

- configure step : find information, be able to modify configure.in

- bootstrap

- build mozilla archive separately :

-- file an issue for a breaker on AMD64 (aka x86_64)

-- fix a build issue (bad compiler option maybe)

-- understand how patches are used at buildtime

- modify the makefile, and start building seamonkey ( basic patch provided )

- define a strategy for the migration

- modify configure (replace mozilla checking with seamonkey checking)

- apply the changes progressively ( and propose tests for the QA)

- propose patches to commit the changes in several cws

- verify it works on other ports ( Mac OS X , windows )

- verify the crashes are fixed (see relevant issues)


  • Create a Gantt diagram / Planning
  • ....
Personal tools