Re: [higgins-dev] Code Changes

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

Re: [higgins-dev] Code Changes

From: "Jim Sermersheim" <jimse@xxxxxxxxxx>
Date: Wed, 06 Jun 2007 10:44:48 -0600
Delivered-to: higgins-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/listinfo/higgins-dev>
List-help: <mailto:higgins-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/higgins-dev>, <mailto:higgins-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/higgins-dev>, <mailto:higgins-dev-request@eclipse.org?subject=unsubscribe>

sounds good.

If/when we need to do a bug fix, I suppose we should notify the list just in case of unforseen ramifications?

>>> Anthony Nadalin <drsecure@xxxxxxxxxx> 6/6/07 10:33 AM >>>

I would like to propose that all non-bug related changes be held or forked until after June 25, thus putting a freeze on current code before the Burton Interop, as we don't want to spend resources chasing bugs that changes might cause, and we would resume normal processes after June 25th

Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122

Follow-Ups:
- Re: [higgins-dev] Code Changes
  - From: Anthony Nadalin

References:
- [higgins-dev] Code Changes
  - From: Anthony Nadalin

Prev by Date: [higgins-dev] Code Changes
Next by Date: Re: [higgins-dev] Code Changes
Previous by thread: [higgins-dev] Code Changes
Next by thread: Re: [higgins-dev] Code Changes
Index(es):
- Date
- Thread

Breadcrumbs