no branches in svn/branches/source

GoogleCodeExporter commented 9 years ago

I found a bug in the Makefile for 2.1.5, but there's no 2.1 branch to supply a 
patch for.

And the Makefile doesn't exist in trunk/source/2.1/  I think trunk/source/2.1 
functions as trunk.  Is trunk/source/2.0 just the 2.0 branch living in an 
unexpected location?

Should I pipe down and learn to love new repository organization schemes?  :P

Dan

Original issue reported on code.google.com by danlo...@gmail.com on 6 Jan 2011 at 11:27

GoogleCodeExporter commented 9 years ago

The normal organization would be to have the latest at
  trunk/source
and the older maintenance branch at
  branches/2.0/source
(with sibling website dirs, obviously)

Is there a reason for not following this pattern?

Original comment by djmitche on 6 Jan 2011 at 11:37

GoogleCodeExporter commented 9 years ago

I've never branched the code in a way that branches would be used. I've worked 
out of the trunk instead, and used tags for the specific releases. The 2.0.x 
series is stable with new releases including only critical bug fixes, and 2.1.x 
is for testing. I prefer to commit only code that has passed unit testing 
though, so HEAD should pretty much always be usable.

Regarding the Makefile not existing, I removed it for the upcoming 2.1.6 
release as it just didn't make any sense to have.

Original comment by kate.war...@gtempaccount.com on 14 Mar 2011 at 10:57

Changed state: WontFix

stefan2904 / shunit2

no branches in svn/branches/source #26