[gef-dev] Branching for post 3.2 development?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[gef-dev] Branching for post 3.2 development?

From: Randy Hudson <hudsonr@xxxxxxxxxx>
Date: Thu, 22 Jun 2006 12:02:05 -0400
Delivered-to: gef-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/gef-dev>
List-help: <mailto:gef-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/gef-dev>, <mailto:gef-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/gef-dev>, <mailto:gef-dev-request@eclipse.org?subject=unsubscribe>

Can we coordinate so that HEAD becomes post 3.2 development (not 3.2 maintenance), and create a 3_2_Maintenance branch for the remainder of 3.2, and for 3.2.1?
I think the build runs entirely off of tags so it should not care which stream was used to create the tags.

-Randy Hudson

Prev by Date: [gef-dev] Information about the IGoToMarker using GEF (eclipse 3.2 RC5 )
Next by Date: Fw: [gef-dev] Branching for post 3.2 development?
Previous by thread: [gef-dev] Information about the IGoToMarker using GEF (eclipse 3.2 RC5 )
Next by thread: Fw: [gef-dev] Branching for post 3.2 development?
Index(es):
- Date
- Thread

Breadcrumbs