Maintaning a private branch of Django
Ramiro Morales
Just wanted to share some notes I've just finished writing (for
my own future reference) and translating to English:
http://seeonee.homeip.net:81/intdoc/DjangoPost096
It describes how I maintain a private branch Django based mostly
in 0.96 with some cherrypicked changesets backported from trunk tip.
This might be of help to people that are not Django core developers
(so, with no write access to the SVN repo) because a core developer
can achieve similar functionality by using svnmerge.py (a tool that
records the list of changeset already applied to a branch in SVN
properties).
Actually, this can be applied to any project that has a a central SVN repo.
This is the kind of things I'll put in a blog the day I finally decide to start
one :).
Just two additional notes:
a. Plaase don't use this technique if you don't have Django experience
and if you don't follow (i.e. read) the bleeding edge changelog[1].
You must know and understand the relationships among changesets
(some are related, some conflict, some undo the effecto of a previous
one, etc.). I'd say the changeset selection is the only sensitive part of
the scheme and care must be exercized if you don't want to get
a broken Django.
b. Don't report bugs to the Django ticket system for things you could
find in such a "customized" copy. Reproduce your particular problem
using the latest stable Django release or the SVN trunk tip before.
submitting a report.
Regards,
1. http://code.djangoproject.com/timeline/
--
Ramiro Morales