Thanks for the response Mark. Have you guys considered adopting
different dev/release practices to get around this?
I was thinking that one thing to do would be to tag from the trunk
and then branch for the release immediately afterwards. Of course,
all subsequent releases in the branch would not appear.
Bradley
On Aug 28, 2006, at 1:32 PM, Mark Phippard wrote:
> Bradley Wagner <bradley.wagner@hannonhill.com> wrote on 08/28/2006
> 11:47:58 AM:
>
>> Our dev cycle is such that we generally branch prior to any release
>> and end up always tagging from the branch. As such, none of the
>> Subclipse tag metadata makes into the trunk meaning its very
>> difficult to figure out when and for what release files were modified
>> during regular development in the trunk (95% of development occurs in
>> the trunk)
>>
>> Anyone have any suggestions about possibly altering our release
>> practices or using Subclipse in a different way to achieve this
>> effect.
>
> We have the same issue with Subclipse development. I do not see
> any way
> around it if that is the development model you use. Tags are not made
> from trunk so you cannot reliably show them off the trunk's
> history. You
> are free to define any tags you want in the Configure Tags dialog.
> So,
> for example, you can add one or many against trunk that mark key
> events
> such as when the branch was created. Depending on the nature of your
> development, they just might not be completely reliable.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Aug 28 19:58:57 2006