I actually do branching via terminal, since the Eclipse interface for
that is a little confusing. As soon
as the branch tag exists, the rest is easy to do in Eclipse.
Once you make the branch, create another project for it and leave the
old branch intact. Having
just one project per module doesn't really save you anything, and
becomes a giant pain when
you want to have both open at once. You could just make do with diff
windows, but it's hard to
work like that.
Betas and such are really a non-issue, because you don't have to
branch (just tag). Get to the
point where you want to release a beta, commit in the 6--2 project,
then tag. Beta 2 is the same,
commit then tag. Backport to 6--1? Open the 6--1 project, patch it,
commit, tag for release.
- Ken Winters
On Jun 6, 2010, at 11:18 PM, Syscrusher wrote:
On Sun, 2010-06-06 at 14:12 -0400, Ken Winters wrote:
Then I do one "project" per module per active branch. For example,
if
I
need to implement
a feature in D7 then backport to D6, I'll have one "project" per.
Importing a project via
CVS makes this easy. Also, I can keep most of the projects closed
and
cut down on memory footprint.
Thanks for the post -- this is what I was thinking about doing, but
wanted to ask before I completely rebuild my workspace, to avoid
wasted
effort if it was a Very Bad Idea. :-)
So let's say I have "mymodule" with a branch tag of DRUPAL-6--1. What
process would you use (from the Eclipse perspective) to commit first a
beta (or two) and then a production release in getting that to
DRUPAL-6--2?
It sounds as if my problem may stem from having done one project per
module rather than one project per module per branch.
Scott
--
------------------------------------------------------------------------------
Scott Courtney [email protected]
http://www.4th.com/
--
Syscrusher <[email protected]>
