Re: Need some guidance on architecting subversion directories when project modifies another code

Greetings, Dan Nessett!

> I am seeking some guidance on what might be the best way to architect
> the subversion repository directory structure in the following
> situation. We use the mediawiki code base and modify it for some
> special uses. We would like to upgrade to a new version of mediawiki
> by creating a patch tool kit that we would then apply to the
> continuing MW releases. This tool kit would change for each MW
> release we bring over. We plan on retaining our specific
> modifications and bug fixes to those modifications in a subversion
> repository. However, since we will be bringing over tag versions of
> the MW code, the development of our code base will not be continuous.
> That is, we will bring over a tag of MW, patch it to add our
> modifications, do some bug fixes while this version remains in
> production and then (sometime before putting the next release into
> production) bring over a new tag of MW. So, there is discontinuity
> between our various versions based on the discontinuity between the
> MW tag versions.

You really should read the http://svnbook.org/
What you describing is the classic example of what there called "vendor drops".

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 19.11.2009, <16:01>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2420043
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].