The 16 september 2006 build will NOT be out.

[killerbot]

no commits

[Phatency]

I get depressed on these days with no commits

[Pecan]

I get depressed on these days with no commits

Don't get depressed! It probably means the devs are off working on "something wonder-ful". 

[David Perfors]

Or they have worked to hard, so they needed a rest... (There is nothing wrong with that.. )

[C D Tamhankar]

For effective utilization of developed code  and also  proper testing of code .... there should be  3-4 commits per week. Otherwise there is toooo much pressure on developers to complete commits.

[David Perfors]

hmm. lets see:
* last week: 11 commits
* week before last week: 22 commits
* week before that: over 30 commits

so, I think the developers are committing enough

[Encryptor]

Doesn't this also imply that the number commits is decreasing?  :?

[mandrav]

Doesn't this also imply that the number commits is decreasing?  :?

Please keep in mind that we 're slowly reaching the feature-freeze period where only bug-fixes are committed.
And please give us some slack here... We have real lives too, you know .

[jarro_2783]

For effective utilization of developed code  and also  proper testing of code .... there should be  3-4 commits per week. Otherwise there is toooo much pressure on developers to complete commits.

lol, for a project I'm working on we just commit whenever. Sometimes I've commited almost 10 times in one day.

[David Perfors]

For effective utilization of developed code  and also  proper testing of code .... there should be  3-4 commits per week. Otherwise there is toooo much pressure on developers to complete commits.

lol, for a project I'm working on we just commit whenever. Sometimes I've commited almost 10 times in one day.

Sometimes I commit once in the month then development is going very slow

[C D Tamhankar]

For effective utilization of developed code  and also  proper testing of code .... there should be  3-4 commits per week. Otherwise there is toooo much pressure on developers to complete commits.

lol, for a project I'm working on we just commit whenever. Sometimes I've commited almost 10 times in one day.

Sometimes I commit once in the month then development is going very slow

Mr. Mispunt ...

I have different views on number of commits and speed.

I feel commits & development speed has no direct relations.
Number of commits  entirely depends on the development stage of the package and complication level of the logic.

For last 8-10 yrs, I do not encourage my team members to commit more than once a day unless its very very essential. And every team member commits ( normally ) at a specific time. And my team has rarely crossed the deadline. And over the period we have realized that, less commits has not affected to completion of the assignment.

You style of working has to equally good, as you all are achieving, what you have planned. I have all praise for you all !!!

(I was not interested in distracting you all, so I was not replying. But, I am replying today because there are no commits for last 2 days.)

[David Perfors]

Mr. Mispunt ...

Wow, I am called mr. I can't believe it

But since there are no rules about committing. But in this opensource world, people are committing changes when one or more bug(s) is fixed or a new feature is implemented. So it is up to the developer to deside when there is a commit. I know that Yiannis is testing features for a few days sometimes before he is committing it.
Beside that, this project doesn't have any deadlines, so the devs are not crossing that line

(To be honnest, I think I am not fully understanding all the talk keep that in mind...)