Re: [Tsheetx-developers] Who's actively working on the TSNG system?

[David T. <tom...@us...>]

Answers below:
 




> Date: Fri, 11 Feb 2011 16:34:01 +0000
> From: ma...@rw...
> To: tsh...@li...
> Subject: Re: [Tsheetx-developers] Who's actively working on the TSNG system?
>

> Does anyone know what the timesheet.ng-2.x branch is? - if checked out it doesn't run 
> and there doesn't appear to be any information how to make it run (if indeed it would).
This branch can now be junked. It is the work of Rob Searles (the guy who started this - and still pays for the domainname). He wanted to go more MVC-like and this was his start. I think the better starting point is now txsheet-2.0-demo.
> 
> Scott, when you refer to the txsheet-2.0 branch which one do you mean? 
> timesheet.ng-2.x or txsheet-2.0-demo?
> Its my bad for naming the branch in an unconventional way, it could be renamed?
Renaming an existing branch is one simple command in SVN, but can cause a lot of confusion to people with working copies based on that branch. So I wouldn't recommend it, we can solve the confusion by removing the other branch.
> 
> Myself and peter have currently tried to keep as much of the codebase intact as to 
> not introduce thousands of bugs while doing some restructuring.  At least this way 
> we can get to a 'stable' point more quickly, get more developers involved to then 
> go nuts with the core parts of the txsheet codebase. :)
> 
> One thing I have wondered is svn is great at propagating code changes but not db 
>changes.  What is the best method to make changes to your db and then notify 
> developers that their db will need to be modified?  An sql file can be written to 
> make the changes and stored in the sql folder but what about the notification bit? 
> - maybe an automated routine could be written? - start making more use of the 
> version number in the config table and started incrementing the minor version 
> number when a database tweak is required?
Yes, it is a problem, but only for people with live data based on that developmental version (which is unusual). Simplest would be to start an "upgrade" script (see the examples in /install) and update the file every time you commit a change to the DB structure. That way when people update their working copies, they see a diff in that file to show them what DB structure changes have been made. I think using lots of minor version numbers is too much work.

> Re: Can anyone claim responsibility for the changes?
> To which part? - could you just run blame?
> So far txsheet-2.0-demo has just been Peter and Mark (me)
Blame just tells me who made the changes, I would like someone to take responsibility for them. Meaning - it is their baby, and they will keep on the work until it is merged into the ongoing work. Someone else's half-finished code is what I deal with at work, I am not so keen to do it in my spare time too.
 
Cheers