[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ecf-dev] ECF freeze and 2.0 endgame/branching
|
Hi Folks,
I had planned to create the 2_0_0 branch today (Tues, May 27), but I
didn't anticipate taking so long doing some other things (generating the
review slides, doing an interview for ECF's 2.0.0 release etc).
So, Ted K and I will do this *tomorrow...Wed, May 27, 2008*. In the
mean time, of course, please only commit to HEAD bug fixes as per this
list of open ECF bugs targeted for 2.0.0:
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&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&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=noop&type0-0-0=noop&value0-0-0=
Thanks,
Scott
Scott Lewis wrote:
Hi Folks,
Note that we are on both a feature freeze and an API freeze for ECF
except bug fixes, and documentation. All committers: please consult
the existing bugs list and
At yesterday's ECF conf call:
http://wiki.eclipse.org/ECF_Conference_Call_5.22.2008 we discussed
moving the existing HEAD onto a new 2_0 branch, so that work on 2.1
could begin (on HEAD).
After discussing the timing of this a little bit, we concluded that we
would create a 2_0 branch next week (Tuesday, 5/27), have all further
development/testing/bug fixing on the 2_0 branch, and open up HEAD for
2.1 development.
This also means that we need to modify our existing build so that
daily builds and the release builds are done off of the new branch
(2_0) rather than HEAD. I haven't had a chance to consult with Ted
about the timing of this (i.e. whether he has time on/before Tuesday
to deal with these changes), so we may have to delay beyond Tues 5/27
if Ted is unable to work on the necessary changes.
Please respond if you have any questions/comments about this. I
(Scott) won't be online for a couple of days (Sat-Mon am), so won't be
responding immediately (spending some happy time away from computers
and near family and nature).
Thanks,
Scott
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev