Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tools-pmc] Requesting exception for patch feature shipped by Object Teams

I have to agree with Gunnar and Dani Megert. You can't patch another
project on the train without their approval. You are essentially
forking the JDT, which is fine on it's own, but the JDT team owns the
JDT that's on the train and need to own the patch. And at the end of
the day you need to work with the JDT team to provide a mechanism so
that there isn't a patch/fork, or at least a patch that the JDT team
is happy with. Or find another way to release Object Teams that
doesn't involve the train.


On Tue, Nov 16, 2010 at 8:34 AM, Stephan Herrmann
<stephan@xxxxxxxxxxxxxxx> wrote:
> Dear Tools PMC,
> (Cc: our Mentors)
> Bug 330288 [1], which is actually a technical bug in the b3 aggregator
> has triggered a discussion in bug 330312 [2], which may or may not
> significantly influence the future of the Object Teams project.
> I've actively tried to trigger this discussion for a long time and I appreciate
> that it is happening now.
> However, if the rules proposed by Gunnar will be enforced in the near
> future, perhaps as a pre-requisiste for participating in the release train,
> this would potentially rule out our (Object Teams) participation in the train.
> Therefor, and in order to keep special case considerations out off that
> discussion, I precautionarily request an exception from those future rules.
> If relevant I will ask you (the Tools PMC) to forward this request to the
> Planning Council.
> I believe I have sufficient arguments for justifying this exception.
> Please let me know, where and how I should communicate these arguments.
> Thanks for considering,
> Stephan
> [1]
>     Indigo repository does not include all the versions of jdt.core
> [2]
>     Rules for project patches in the train
> _______________________________________________
> tools-pmc mailing list
> tools-pmc@xxxxxxxxxxx

Back to the top