Hi, Thanks for the critiques. I'm almost done with this development cycle, and so I'll commit my changes soon to SVN. After that, I'll use branches and standard SVN workflows to version-control my code.
I have a quick question about use of Apache SVN: in the places I've worked where we've used SVN, it has been heavily discouraged to check in broken or unfinished code. We didn't do much branching, but mostly worked out of trunk. I think that breaking a branch is not as bad as breaking trunk, but I wanted to check with the community: are broken, intermediate commits to branches considered poor practice? What about to trunk? Thanks, Jake On Tue, Jun 8, 2010 at 11:37 AM, Ted Dunning <ted.dunn...@gmail.com> wrote: > > Making your code public early also saves you lots of effort because others > can jump in and help. That sort of community is a lot of what Apache is all > about. > > On Tue, Jun 8, 2010 at 8:24 AM, Rahul Akolkar <rahul.akol...@gmail.com> > wrote: >> >> Also, in the last paragraph you mention waiting till you finish >> porting more before checking into the Apache SVN -- whereas I'd >> actually suggest that you even do all your experimentation in the >> Apache SVN > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
