Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Communications Framework (ECF) » opening the 2.0 floodgates
opening the 2.0 floodgates [message #619595] Fri, 28 September 2007 17:42 Go to next message
Scott Lewis is currently offline Scott LewisFriend
Messages: 1038
Registered: July 2009
Senior Member
Hi Folks,

Here is the *current* ECF roadmap:

http://wiki.eclipse.org/ECF_Ganymede_Roadmap

Since 1.1 was revoked because we didn't yet have a release review, I
propose we simply do the release review with the current state of HEAD,
and have that release be 1.2 as scheduled next Friday (Oct 5). In
effect, this means that we don't/didn't have a 1.1 release. We will
have no more 1.X releases, and will concentrate solely on 2.0 milestone
releases as described on the roadmap.

To summarize :)

1) We have a release review next week (week of Oct 1) and call it for
1.2 using the current state of ECF HEAD. This will end the 1.X line
(unless we have some severe bug that requires a 1.1.1 maintenance...but
we will not plan for that).
2) After that, we open the API floodgates for backward incompatible
changes and assume only ECF 2.0 milestones from here on until Ganymede
release

Does this work for people?

Any interested parties within community please respond with -1, 0, +1.
If -1 please describe what else you require that is not satisfied by
this and we'll to the most possible to accomodate.

(As a quick aside/reminder...thanks to work by Ted and Pete, we now have
daily integration builds made available for both the dev.eclipse.org and
ecf1.osuosl.org codebases, and so people who need/want those can easily
get them).

Thanks,

Scott
[Discovery] proposal for API breaking changes (was Re: [ecf-dev] opening the 2.0 floodgates) [message #619758 is a reply to message #619595] Mon, 22 October 2007 21:02 Go to previous message
Eclipse UserFriend
Originally posted by: eclipse-news.lemmster.de

Scott Lewis wrote:
> Hi Folks,
>
> Here is the *current* ECF roadmap:
>
> ...
> 2) After that, we open the API floodgates for backward incompatible
> changes and assume only ECF 2.0 milestones from here on until Ganymede
> release

Hi everybody,

with 1.2 out of the door and discussion open for 2.0, Scott and me would
like to propose non backward compatible API changes in ecf.discovery:

- [Discovery] IServiceListener API should be simplified/ no partially
resolved services anymore -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=207085
- [Discovery] Namespace semantics for discovery need to be different -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=207089
- [Discovery] Discovery may define a generic IServiceTypeID
independently of providers -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=207091

If anybody sees problems/has comments, please speak up asap. :-)

Regards,
Markus
Previous Topic:ECF 1.2.0 available
Next Topic:Re: Detect if RCP application is already running
Goto Forum:
  


Current Time: Tue Aug 04 18:18:04 GMT 2020

Powered by FUDForum. Page generated in 0.01662 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top