Posts

Showing posts with the label svn

Some cure for abrupt SVN hickups.

Image
Committing the binary files to SVN: Normally binary files like libs, and .a wont be committed on SVN. They are prohibited to be added to your neat clean repository up there in the heavens. Ubuntu There are two ways to enable that. On command line, it is simple. Go to the folder where the binary files, i.e. .a and .lib are located.. Type the following, the path is just for example, you CD to your own path. cd /development/project/library svn add --no-ignore svn commit OR you can remove the global ignore rule from configuration file. cd ~/.subversion/config cd /etc/subversion/config sudo svnserve -d cd /development/project/library sudo svn commit Windows On Windows you can pop up the the SVN Settings dialog, in the General Tab, you can see Global Ignore pattern text box. There is the *.a and *.lib. Just remove the entry, i.e. *.a from this text box. This will make the changes global to Subversion. This would allow you to commit required files on SVN.

Software product lifecyle

" ...your document is just great. Please put this on your blog or somewhere ... " -- Mdsr The initiation of a project can be started by any of è è Marketing Requirement Document MRD : This document is conducted by marketing team , which identifies possible product gaps in the industry. They later come up with MRD, highlighting what market is anticipating in the future. This serves as stimulus for product/project initiation. It can be regarded as a wish list + requirement. è Software Requirement Specification SRS : This document is composed by Technical Management at the company. They take input from MRD and devise how to achieve what is proposed by marketing guys. If marketing guys are just beating about the bush, than engineering starts from this document. This document explains the product composition and/or product placement. It shows what is required and where, but not shows how. *There is an IEEE standard for SRS, which is just amazing template to u...