[orbit-dev] How to handle RC's?

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

[orbit-dev] How to handle RC's?

From: Chris Aniszczyk <zx@xxxxxxxxxx>
Date: Thu, 24 Jan 2008 10:53:03 -0600
Delivered-to: orbit-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/listinfo/orbit-dev>
List-help: <mailto:orbit-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/orbit-dev>, <mailto:orbit-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/orbit-dev>, <mailto:orbit-dev-request@eclipse.org?subject=unsubscribe>

Anyone have opinions on how to handle RC's for Orbit bundles. For example, imagine a scenario where we have some Library X... where the version was 1.0.0 RC2.... how would you want to handle this... besides emailing the author and saying when 1.0.0 was coming out?

v1_0_RC2 as a branch with the bundle version as 1.0.0.qualifier?

v1_0_0 as a branch with the bundle version as 1.0.0.qualifier when 1.0 comes out? That should guarantee that the version would get rev'd probably.

Thoughts?

Cheers,

---
Chris Aniszczyk | IBM Lotus | Eclipse Committer | http://mea-bloga.blogspot.com | +1.860.839.2465

Follow-Ups:
- Re: [orbit-dev] How to handle RC's?
  - From: Thomas Watson

Prev by Date: Re: [orbit-dev] Slf4j into Orbit
Next by Date: [orbit-dev] Movin' on
Previous by thread: [orbit-dev] Welcome Mike Squillace as a new tools.orbit Committer
Next by thread: Re: [orbit-dev] How to handle RC's?
Index(es):
- Date
- Thread

Breadcrumbs