Difference between revisions of "Road To 1.0"

From Lazarus wiki
Jump to navigationJump to search
m
Line 54: Line 54:
 
|1.0.0||Mattias||<strike>Export LFM as xml</strike>
 
|1.0.0||Mattias||<strike>Export LFM as xml</strike>
 
|----
 
|----
|1.0.0||-||Icon editor
+
|1.0.0||Tombo||Icon editor (see [[Icon Editor Roadmap]])
 
|----
 
|----
 
|1.0.0||various||Webbugs to be fixed before the 1.0 release: [http://www.lazarus.freepascal.org/mantis/view_all_set.php?type=3&source_query_id=91 target 1.0 bugs]
 
|1.0.0||various||Webbugs to be fixed before the 1.0 release: [http://www.lazarus.freepascal.org/mantis/view_all_set.php?type=3&source_query_id=91 target 1.0 bugs]

Revision as of 14:47, 1 October 2006

English (en) español (es) 日本語 (ja)

This document helps the Lazarus team to focus on a 1.0 release in the near future.

The work to be done is divided into 3 targets:

  • things to be done before the next release (0.9.16)
  • things to be done before the 1.0 release
  • things to be done after the 1.0 release


Setting the target of a bugfix

When new bugs are entered, we try to give them a target in which version the bug will be fixed. If a bug is set to post 1.0, that means the developers think this bug is not important enough to block a 1.0 release. In order to have a 1.0 sooner rather than later, developers will leave those bugs for later. Of course you can make sure these post 1.0 issues are fixed in the 1.0 release by providing patches for these issues.

Some criteria are:

  • Only gtk1 and win32 widget sets are stable in 1.0. So bugs for other widget set (gtk2, carbon) are set to post 1.0.
  • Until the 1.0 there will be a feature freeze. New features and components generally get a post 1.0 target. Bugs affecting stability have a higher priority than bugs fixing the implementation of a property.
  • Some components are not stable enough and should be disabled for 1.0. If they are disabled, then fixing them before 1.0 will not be necessary.

Work to be done

Target Responsible Comment
0.9.16 Vincent Find out, if Lazarus configuation files can be stored in the profile directory under windows
0.9.16 Vincent Find out, what needs to be done to make it possible to install Lazarus in c:\Program Files\Lazarus
0.9.16 Vincent Use fpmkcfg to create a default configuration file
0.9.16 Various Webbugs to be fixed before the next release: target 0.9.16 bugs
0.9.16 Mattias Copying from KDE applications under gtk (copy text from xterm/kde app) See
0.9.16 Mattias Find out, why sometimes designer controls are invisible (the gtk seems to not draw them, it happens on windows too, see issue 1622) (Reproduce by: Copy+Paste) Difficult bugs
0.9.16 Mattias Create a SuSE package
1.0.0 - Debugger options
1.0.0 - Doc Editor
1.0.0 Mattias Help for fpc key words
1.0.0 Mattias Help for fpc messages
1.0.0 Mattias Helpsystem for IDE items
1.0.0 various Help for common IDE items (see IDE Documentation Roadmap)
1.0.0 Mattias Multi replace dialog
1.0.0 Mattias Export LFM as xml
1.0.0 Tombo Icon editor (see Icon Editor Roadmap)
1.0.0 various Webbugs to be fixed before the 1.0 release: target 1.0 bugs
1.0.0 Mattias check and warn when open form for uninstalled packages with registration
1.0.0 - more LCL Documentation (see LCL Documentation Roadmap)
1.0.0 Marc fix debugging in windows and linux
1.0.0 Mattias start protocol: IDE should remember if there is a problem opening a form or project and should not open it on a second start
1.0.0 Mattias improve make install target
1.0.0 Vincent add framework for easily using resourcestrings and translations in applications
1.0.0 Mattias gtk interface: recognize and translate dead keys
post 1.0 - Webbugs to be fixed after the 1.0 release: target post 1.0 bugs
post 1.0 Mattias IDE Feature: Improve TDataModule, so that its components can be used in other forms/datamodules at design time