Difference between revisions of "Talk:AirborneCodeReorg"
Jump to navigation
Jump to search
m |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
AIRBORNE source code reorganization and cleanup | AIRBORNE source code reorganization and cleanup | ||
This page is to discuss option for code cleanup. | |||
REMARKS: | |||
# It would be great to involve a little more people also using the code. | |||
# Use GIT only for the new code part so people are not confuse using either svn or git. | |||
# Make changes that are beneficial, not change for the sake of cleanup only | |||
# Use GIT in full effect what is was designed for, thus for others to submit code and merge later. | |||
# Use Branching and merging | |||
-- | -- | ||
Note1: I agree with the code need improvement. Just as a side-remark, you can link to a makefile already, no need to include it in the XML document. Which is indeed much much better, because including it in the XML, the document is not an XML document anymore. IMHO it is bet to first see what is already possible, then slowly evolve.[OpenUAS] | |||
Latest revision as of 22:45, 18 August 2010
AIRBORNE source code reorganization and cleanup
This page is to discuss option for code cleanup.
REMARKS:
- It would be great to involve a little more people also using the code.
- Use GIT only for the new code part so people are not confuse using either svn or git.
- Make changes that are beneficial, not change for the sake of cleanup only
- Use GIT in full effect what is was designed for, thus for others to submit code and merge later.
- Use Branching and merging
--
Note1: I agree with the code need improvement. Just as a side-remark, you can link to a makefile already, no need to include it in the XML document. Which is indeed much much better, because including it in the XML, the document is not an XML document anymore. IMHO it is bet to first see what is already possible, then slowly evolve.[OpenUAS]