Re: [ecf-dev] ECF freeze and 2.0 endgame/branching

[Scott Lewis <slewis@xxxxxxxxxxxxx>]

Hi Markus,

Markus Alexander Kuppe wrote:
> Scott Lewis wrote:
> > Hi Folks,
> >
> > Here's the current bug list for relevant bugs to be addressed prior 
> > to 2.0:
> >
> > https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&target_milestone=---&target_milestone=1.0.0&target_milestone=1.0.1&target_milestone=1.0.2&target_milestone=1.1.0&target_milestone=1.2.0&target_milestone=2.0.0M1&target_milestone=2.0.0M4&target_milestone=2.0.0M5&target_milestone=2.0.0M6&target_milestone=2.0.0M7&target_milestone=2.0.0RC1&target_milestone=2.0.0RC2&target_milestone=2.0.0&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=n 
> oop&type0-0-0=noop&value0-0-0=
> Does no target milestone set implicitly mean 2.0?

It implicitly means '2.0 if it can be done'...given freeze, technical 
feasibility, IP process, and other constraints.  If with closer 
examination it cannot be done in 2.0, then either change target 
milestone (I believe all ECF committers can now change target 
milestone), or let me know and I will change it after I return on Mon.

Scott