RE: [mylar-dev] task list externalization

["Mik Kersten" <beatmik@xxxxxxx>]

This patch can't make it into 1.0 for the reasons stated on the
corresponding bug, i.e. mostly because it was too disruptive at this stage
in the 1.0 end game and because we had to prioritize other fixes with more
impact to overall 1.0 quality and APIs.

166609: [api] improve task externalization API
https://bugs.eclipse.org/bugs/show_bug.cgi?id=166609

Regarding "stay forever", yes, Mylar 1.0.x itself will stay around forever.
But the stream we're working on after the 1.0 release is Mylar 2.0M1, M2,
etc, up to the Europa-based 2.0 release of Mylar.  We can currently be
confident that the 1.0 APIs support the kinds of connectors, bridges, and
team providers that we have working with 1.0.  But what I expect us to get
some substantial input from integrators working with 1.0 that are extending
Mylar in ways we have not accounted for yet, and we will want to support
them by gracefully moving forward on the 2.0 stream.  That said, obviously
we'll try to minimize the burden of any API changes that we make, and make
it possible for integrators to support both 1.0 and 2.0Mx for as long as
possible.  This will probably require forking the version numbers of the
plug-ins post 1.0. 

Mik 

P.S. Regarding communication like "Whatever.", I know that this is a subtle
point, but it would be nice to avoid that kind of banter on the list if
possible because it can make the list feel aggressive or disrespectful, and
discourage newcomers from posting their opinions.  And the opinions of
newcomers are very important for a healthy developer community.  In that
respect, bug reports are much better for flaming than the newsgroup or
mailing list :)

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: Sunday, December 03, 2006 4:12 PM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] task list externalization
> 
>   Whatever. I just thought that it is important to deliver 1.0 with an
> API that would allow further evolution, because we should expect more
> 3rd party connectors after the release, so API published with 1.0 will
> have to stay forever.
> 
>   See Evolving Java-based APIs document
>   http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs
> 
>   regards,
>   Eugene
> 
> PS: same applies to ITaskListElement class hierarchy
> 
> 
> Nathan Hapke wrote:
> > While I think your idea is a reasonable one, I don't think that this
> > should make it into 1.0 like you suggested it needed to be.  If my
> > memory serves, RC2 is scheduled to go out within the next day or two,
> > which IMHO doesn't leave us enough time to stabilize this new API.
> >
> > I think it would be a good idea to make this change when we revisit
> > Bug 150680: Generalize repository configuration persistance and move
> > into tasklist
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=150680
> >
> > regards,
> > Nathan
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev