Hi Dan,
I'm just creating a slot in JIRA for tracking sequences of related
changes. In this case, I would like to have a permanent record of the
work done to merge the trunk into the 10.2 branch. This involves a
number of separate commits which are part of a single logical operation.
I don't see the value in creating a separate JIRA for each of these
merges and I see some value in being able to survey the whole logical
operation at a glance.
If there's a better way to accomplish this goal, I'm always eager to learn!
Regards,
-Rick
Daniel John Debrunner wrote:
Rick Hillegas (JIRA) wrote:
Placeholder for 10.2 merges
---------------------------
Key: DERBY-1725
URL: http://issues.apache.org/jira/browse/DERBY-1725
Project: Derby
Issue Type: Task
Affects Versions: 10.2.1.0
Reporter: Rick Hillegas
Fix For: 10.2.1.0
This is a placeholder for recording merges from the trunk to the 10.2 branch.
Rick, I've seen a couple of issues described like this, what exactly is
a "placeholder"?
Thanks,
Dan.
