hi Red1 On Sun, Apr 3, 2011 at 2:58 AM, red1 <[email protected]> wrote: > btw Boh, how did u know it involved an Exocet? You are on the watchlist now > my friend :)
I was just guessing, are you admitting its an Exocet!? ;-) Pls keep it away from my backyard ;-) > Ok back to the log book argument. Why not go back to our own best practice? > Show me your code. No, not from your notebook. From SourceForge template or > other repository and there we can examine trackers and their log entries to > see if they follow the discipline or not. > I learnt alot while working on the ADempiere project using SourceForge. > Stuff such as FR, Bug trackers, auto numbering; atomic mapping of each > tracker to each bug fix and commit; describing how to replicate the bug, and > which Bug tracker number refers to which commit revision. Just an idea on > how to be lazy fruitfully. > I agree, any CVS (Code Versioning System) and/or Issue/BugTracking system is also equivalent to a log book. How many proprietry projects actually use those tools? OSDC care to take a survey? > On 4/3/11 2:19 AM, Boh Yap wrote: >> >> ah, good discussion, logbook vs exams, lets carry on... >> >> These are 2 different paradigms, >> >> > From the employee POV: >>> >>> >> >> >> > > -- > To unsubscribe from and detail about this group > http://portal.mosc.my/osdc-my-mailing-list-information > > MOSC2011 http://fb.me/mosc2011 and http://portal.mosc.my/ > -- #------- regds, Boh Heong, Yap -- To unsubscribe from and detail about this group http://portal.mosc.my/osdc-my-mailing-list-information MOSC2011 http://fb.me/mosc2011 and http://portal.mosc.my/
