Re: [cross-project-issues-dev] Webtools JSDT considering new Bower integration

2015-01-10 Thread Matthias Sohn
On Thu, Jan 8, 2015 at 9:40 PM, Chuck Bridgham  wrote:

> I'm posting this to cross-projects because we are considering a change
> that requires a significant dependency (jGit).
> A new contribution to JSDT revolves around support for Bower javascript
> package manager runtime, and this has a jGit dependency.
> Our biggest issue from a build standpoint is we (WTP) have a +2 offset,
> while jGit is +3.  I'm actually surprised this has remained at +3.
>
> I'm looking for advise how to proceed, what options do we have to consider
> this change?  Ask for jGit to move to +2?  Change the packaging
> of the JSDT bower support to be optional?  What have other projects done
> in this case?
>

JGit has no dependencies to other release train projects. EGit depends on
platform (+0) and Mylyn (+3)
but I don't expect any problems with Mylyn.

So I think we can move JGit and EGit to offset +1.

-Matthias
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Your friendly error reports bot is suspended

2015-01-10 Thread Marcel Bruch
Yes, efxclipse is currently not tracked and before sending you emails, we need 
you to state your interest.


Since efxclipse can be installed on top of any existing Eclipse installation 
and to get most out of it, I think we should consider to equip more EPP 
packages with the error reporter. 

So far it’s part of the committers and modeling *Mars Milestone Builds* package 
since M3. There are requests pending to add it to the Java [1] and Scout [2] 
package. But maybe we should consider adding it to all EPP packages by default 
- similar to the EPP Marketplace client?


Since the quality of the platform (and our extensions to it) is of critical 
importance to many of us, I think it's an important and necessary step to learn 
about any kind of problems our users experience.

In the meanwhile the error reporting client got a lean UI making it easy for 
clients to report issues. The server side also got it's own UI (decoupled from 
Bugzilla), provides means to help committers triaging problems, requesting 
further information etc.

Projects like JDT, Egit, Xtext, Sirius, ECP and others embrace the error 
reporter as new input source for finding errors in their code base. Projects 
like the Platform, PDE, CDT carefully start using it and even a fair share of 
UI freezes have been recognized and fixed [4].

Although challenging, we made recognizable progress in detecting similar 
reports and prevent committers from being flooded with duplicated error reports.

The EF offered the necessary technical support and infrastructure to set up 
that service for the Mars Release.


All these points make me believe that adding an automated error reporting 
client should be added to the Eclipse IDE as a whole - similar to the EPP 
Marketplace client.

Adding it now to M5 also has the advantages that the server gets a fair stress 
test before the release, we get the chance to spot many more issues, and last 
but not least committers will be able to make an informed decision by M7 
whether or not to integrate it into the Mars release.


When we started the initiative, 20 committers on this mailing list supported 
the development of this feature [3]. What’s your feeling after 2 milestone 
phases? I created bug 457180 to track your feedback and opinion about adding it 
to all EPP packages with Mars M5. Thanks for casting your voice.


Marcel



[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=457081
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=457082
[3] 
https://docs.google.com/a/codetrails.com/forms/d/1BLbeAtu-pvz26aXgfP2v4Sm3ysPjkUknkxEJsj909Lk/viewform
[4] 
http://blog.vogella.com/2015/01/09/eclipse-git-gets-faster-ui-freeze-reporting-activated-by-default-in-saneclipse/
[5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=457180




> On 10 Jan 2015, at 09:11, Tom Schindl  wrote:
> 
> Do I = e(fx)clipse have to opt-in explictly if i want to go with option 2?
> 
> Tom

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Your friendly error reports bot is suspended

2015-01-10 Thread Tom Schindl
Do I = e(fx)clipse have to opt-in explictly if i want to go with option 2?

Tom

Von meinem iPhone gesendet

> Am 09.01.2015 um 08:04 schrieb Marcel Bruch :
> 
> I see three valuable ways:
> 
> 1. Only report issues into the separate system and let committers review 
> these items from time to time manually.
> 2. Report issues into the separate system and send daily reports to 
> committers or project lists that there are new incoming problems.
> 3. Report issues into the separate system AND directly into the project’s 
> bugzilla product/component.
> 
> Options 1. and 2. are on my todo list for M5. Your option 3 seems viable to 
> me as well. 
> My proposal: Projects that wish to receive error reports directly in 
> bugzilla, should say so (e.g. by a decision on the mailing list) and specify 
> the bugzilla component to assign these reports with. I’ll add an UI for that.
> 
> What do you/others think?
> 
> Best,
> Marcel
> 
>> On 09 Jan 2015, at 05:04, Lars Vogel  wrote:
>> 
>> Hi Marcel,
>> 
>> thanks for the information.
>> 
>> From the platform.ui side I'm not sure that we will be able to adapt "yet 
>> another system" for looking at bug reports. IIRC the update of Bugzilla 
>> worked fine for us, with the only issue that the duplicate bug dedection has 
>> marking not the main bug and therefore created a long dependency chain. But 
>> I think this has been fixed.
>> 
>> Would it be possible to configure your intermediate system per comment to 
>> continue to create automatic Bugzilla entries? If yes, every project could 
>> vote to use your new system or continue to work only in Bugzilla. 
>> 
>> Best regards, Lars
>> 
>> 2015-01-08 8:55 GMT+01:00 Marcel Bruch :
>>> Hi Lars,
>>> 
>>> no, there is no bug for this. But an interim system is live and receives 
>>> errors. 
>>> 
>>> The UI also offers basic search capabilities now. See [1] for an overview 
>>> and [2] for an example of a concrete query. It also offers a set of 
>>> predefined per-project queries (see below for a comprehensive list).
>>> 
>>> 
>>> Plans are to have it operational by M5 (end of January). Until M5 the 
>>> proposed workflow is as follows:
>>> 
>>> 1. Committers can review the 'project problem listings' (given below) once 
>>> per day
>>> 2. For every new problem that (you think) needs a closer look, move it to 
>>> Bugzilla. Convenient support for this will be added tomorrow.
>>> 
>>> 
>>> Some notes about the interim system:
>>> 1. Even if possible, please do not make any changes in ui except creating 
>>> bugs from there; they might get lost during system updates.
>>> 2. Bugzilla is the only stable reference you have. Thus, move errors to 
>>> Eclipse’ Bugzilla if you think they are bugs and start working on them 
>>> there.
>>> 3. Once a bug was created in bugzilla, don’t look back or try to keep the 
>>> error reporting system in-sync. Eventually we’ll do that automatically.
>>> 4. Problem statistics and duplicate detection results may look suspicious 
>>> at times. It's more challenging than it may look on a first sight to detect 
>>> duplicates in large, moving code bases. 
>>> 
>>> Having said this, I’m happy to receive feature requests and suggestions by 
>>> email (probably better off this list) or, preferably, via bugzilla.
>>> 
>>> Best,
>>> Marcel
>>> 
>>> 
>>> Unconfirmed problems by project Quickstarter Queries
>>> 
>>> Acceleo
>>> Ant
>>> C/C++ Development Tools
>>> Code Recommenders
>>> Eclipse Debug
>>> Eclipse Platform
>>> EGit / JGit
>>> EMF Client Platform
>>> Epsilon
>>> Graphical Modeling Framework
>>> Graphical Modeling Tools
>>> Help
>>> Java Debug Interface
>>> Java Development Tools
>>> Machine 2 Machine
>>> Marketplace Client
>>> Maven 2 Eclipse
>>> Modisco
>>> Mylyn
>>> Object Teams
>>> OCL
>>> Oomph
>>> P2
>>> Papyrus
>>> Plugin Development Environment
>>> Webtools Project
>>> Windowbuilder
>>> Xtend
>>> Xtext
>>> 
>>> 
>>> 
>>> 
>>> 
>>> [1] https://dev.eclipse.org/recommenders/committers/confess/#/
>>> [2] 
>>> https://dev.eclipse.org/recommenders/committers/confess/#/problems/search?projects=platform&kinds=NORMAL&kinds=FREEZE&categories=UNCONFIRMED&page=0&size=10&sort=createdOn,desc
>>> 
>>> 
>>> 
 On 07 Jan 2015, at 11:30, Lars Vogel  wrote:
 
 Hi Marcel,
 > I’ve been asked to shutdown the collector to keep the annoyance low 
 > until this is fixed, which I do hereby.
 
 Do you have the bug number for the pending fix in the error reporting bot?
 
 Best regards, Lars 
 
 2014-12-19 7:35 GMT+01:00 Marcel Bruch :
> Hi,
> 
> in Bug 455361 Konstantin expressed his annoyance about another comment  
> on his bug.
> I’ve been asked to shutdown the collector to keep the annoyance low until 
> this is fixed, which I do hereby.
> 
> The collector will continue to receive errors but will not send 
> notifications to anyone or create comments in bugzilla.
> 
> 
> Happy Christmas Season
> Marcel
> ___