I saw this on dev@ a.o and have not read later things here. Forgive me if there are other recommendations. I trust any solution Kay comes up with.
My suggestion: Copy 4.1.0 to a 4.1.2 branch. Staunch the problems of difficulty synchronizing source to distributions and also allow a way to make a release-specific retro-active patch if necessary to issue one. I don't know if you can commit individual changes, by copying from trunk to a branch. Someone here should know. Or copy trunk to a 4.1.2 branch, assuming all the mods in it belong in 4.1.2. That would be ideal. We are digging a hole for ourselves and anyone who needs to audit our stuff otherwise. - Dennis -----Original Message----- From: Kay Schenk [mailto:[email protected]] Sent: Thursday, July 9, 2015 12:48 To: OOoDev Apache Subject: How to commit changes to 410 branch? It seems we are still using the 410 branch for the 4.1.2 release. There have been quite a number of changes to trunk since the 4.1.1 release that I feel ALL these should be incorporated into 4.1.2. How do we get the changes from trunk into the 410 branch easily? It seems we could use -- svn copy <my changes> https://svn.apache.org/repos/asf/openoffice/branches/AOO410/trunk/<my changes> and do a commit on https://svn.apache.org/repos/asf/openoffice/branches/AOO410/<my changes> once this is done? If not, how do we do this without actually making the 410 branch local? Wouldn't it be easier just to tag when we're ready to do the release instead of all this back porting? -- -------------------------------------------- MzK "We can all sleep easy at night knowing that somewhere at any given time, the Foo Fighters are out there fighting Foo." -- David Letterman --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
