Difference between revisions of "Projects/KDevelop5/ReleaseTodo"

Jump to: navigation, search
Line 29: Line 29:
 
** clearly document regressions and new features - why is it better, even though some wizards/features got removed, and why is it still OK to go ahead with this functionality
 
** clearly document regressions and new features - why is it better, even though some wizards/features got removed, and why is it still OK to go ahead with this functionality
 
** create an ehterpad for the release announcements
 
** create an ehterpad for the release announcements
 +
* ktexteditor plugin integration:
 +
** blacklist a few plugins: project, gdb, ...
 +
** enable some by default: file browser, snippets, search & replace
 +
** make sure functionality is equivalent, port features from kdevelop to kate as needed
 +
* include paths and defines
 +
** look for siblings as a fallback
 +
** make sure the custom make file stuff is working, esp. the makeresolver
 +
* wizards for project managers
 +
** we need the technology, waiting e.g. for upstream cmake
 +
** they are not that high-priority anyways, simple things are simple to do by hand, hard things are impossible to do by wizard

Revision as of 11:11, 28 July 2015

things left to do

kdev-clang blockers

  • implement functions is broken
  • add include helper

get a vision

  • see a doctor

bof notess

  • remove oldcpp
  • not even keep it around for installing both
  • we'll keep .kdev4 in project files and config folder names
  • we'll add migration code
  • shortcuts: streamline them, desirable. but try to keep compatibility if possible by setting old shortcut as alternative. maybe offer the possibility to import old shortcuts via kxmlgui (which is broken?, but could be fixed/done). while at it: add emacs, vim, visual studio short cut sets etc.
  • also: make sure to document new shortcuts
  • for the release announcement of beta 1:
    • market it as a tech preview, still api can be changed
    • clearly document regressions and new features - why is it better, even though some wizards/features got removed, and why is it still OK to go ahead with this functionality
    • create an ehterpad for the release announcements
  • ktexteditor plugin integration:
    • blacklist a few plugins: project, gdb, ...
    • enable some by default: file browser, snippets, search & replace
    • make sure functionality is equivalent, port features from kdevelop to kate as needed
  • include paths and defines
    • look for siblings as a fallback
    • make sure the custom make file stuff is working, esp. the makeresolver
  • wizards for project managers
    • we need the technology, waiting e.g. for upstream cmake
    • they are not that high-priority anyways, simple things are simple to do by hand, hard things are impossible to do by wizard

Content is available under Creative Commons License SA 4.0 unless otherwise noted.