From paul.verest at live.com  Fri Jul  1 02:10:15 2016
From: paul.verest at live.com (Paul Verest)
Date: Fri, 1 Jul 2016 06:10:15 +0000
Subject: [jbosstools-dev] closed freemarker issues
In-Reply-To: <64700995-F4B0-43F9-BFDA-4708E74A3690@redhat.com>
References: <64700995-F4B0-43F9-BFDA-4708E74A3690@redhat.com>
Message-ID: <KL1PR03MB1815930137AA042E8612CE0F86250@KL1PR03MB1815.apcprd03.prod.outlook.com>

Hello

It happens.
1) One that I remember now created as https://issues.jboss.org/browse/JBIDE-22685

I dislike JIRA, it is huge, and 2) login does not take email (and does not says so)
https://developer.jboss.org/message/959483#959483
and 3) it uses Google API that
JIRA e.g. https://issues.jboss.org/browse/JBIDE can't be used in China without VPN

Google services are absent in mainland China.


JIRA make use of google APIs, that make JIRA page load extremely slow (1 minute)

I can't post as 4):
Not allowed to post content more than once every 1800 seconds.

Best regards,
Paul Verest
+86 158 89583889
UTC +8

On 6/24/2016 9:48 PM, Max Rydahl Andersen wrote:
Hey,

I started to see more and more freemarker issues being open on github despite
the readme says to use https://jira.jboss.org/jira/browse/JBIDE.

I wanted to leave a comment on the issues that bugs should be open on JBIDE,
but before that I just tried to click the "Enable issues" checkbox on github
and surprise: github nukes the issues instantly ;/

That was not supposed to happen. Wanted to give a headsup first.

Anyways, in short - freemarker repo is now like others that pull-request
is open and bugs goes to the relevant component in jira.

Paul - sorry for nuking the issues ;/ but please use https://jira.jboss.org/jira/browse/JBIDE
for freemarker work.

/max
http://about.me/maxandersen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160701/b14f25f3/attachment.html 

From aer-bot at ctrlflow.com  Sun Jul  3 23:30:01 2016
From: aer-bot at ctrlflow.com (Automated Error Reporting Bot)
Date: Mon, 4 Jul 2016 03:30:01 +0000 (UTC)
Subject: [jbosstools-dev] [aeri] Weekly JBoss Tools Error Reports Digest
Message-ID: <1962402157.0.1467603001098.JavaMail.ec2-user@aeri-rh>

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160704/0401c375/attachment-0001.html 

From apupier at redhat.com  Mon Jul  4 05:37:08 2016
From: apupier at redhat.com (Aurelien Pupier)
Date: Mon, 4 Jul 2016 11:37:08 +0200
Subject: [jbosstools-dev] Eclipse plugins testing structure
In-Reply-To: <56AFA741.5060807@redhat.com>
References: <56A88DD9.9030802@redhat.com> <56A89139.2040308@redhat.com>
	<56A898F3.9070408@redhat.com> <56A8A1BD.6050908@redhat.com>
	<56AFA309.7000102@redhat.com> <56AFA741.5060807@redhat.com>
Message-ID: <CAFNb52fzJ8MgNQN2i8JMBU9b0keWRusBUCF1mt_YpeEEeFKD-g@mail.gmail.com>

Hi everybody,

I wake up this thread because following this discussion and several point
to point discussions, I gave a presentation @ EclipseCon France about the
importance of "unit tests which are not launching the Workbench or an OSGi
platform".

Here is the recording:
https://www.youtube.com/watch?v=IGkFy2H-d60&index=33&list=PLy7t4z5SYNaRJff0KBMbubOaj8gevvML4

On Mon, Feb 1, 2016 at 7:43 PM, Mickael Istria <mistria at redhat.com> wrote:

> On 02/01/2016 07:25 PM, Aurelien Pupier wrote:
>
> Le 1/27/2016 11:53 AM, Mickael Istria a ?crit :
>
> Yes, but it requires an effort in moving the code to the right plugin or
> turning fragment into a bundle everytime one identifies something to reuse;
> whereas using bundles only doesn't require any effort from the "producer"
> side.
>
> Considering this code as first citizen, it seems to me an acceptable
> effort ;-)
>
> Do you put your actual "first citizen" business code into fragments too?
>
> When running locally, I may want to run only unit tests first.  Without
> launching the OSGi platform it will be faster. It will also allow to use
> some tools such as Infinitest to have continuous feedback while developing.
>
> I don't know much of Infinitest, but I believe it doesn't rely on how
> Maven runs tests. Eclipse already provide the ability to run a test class
> in a bundle in plain Java without starting the workbench; it's "Run As >
> JUnit Test" instead of "Run As > JUnit Plugin Test". I guess Infinitest can
> rely on that, can't it?
>
> Yes Infinitest can rely on it but it means that you are able to launch as
> "JUnit test" and so not starting the workbench.
>
> Yes, and if you're able to do it from the Eclipse IDE for your test class,
> isn't it enough?
> So in your IDE, you can run "unit tests" without the workbench/Platform
> actually started, just the API available; and with Maven and
> tycho-surefire-plugin, you get a Platform/workbench started, like it will
> happen in real-life, to find real issues that wouldn't happen in plain Java
> environment.
>
> Just to be clear, I'm not saying it's wrong to change that; I'm more
> wonderint how much profitable is it, what changing test structure would
> provide better than the current one does. The Infinitest story seems the
> only one "worth it" IMO, and it doesn't seem to be correlated to
> tycho-surefire vs maven-surefire.
>
> InfiniTest or only launching test of a single plugin very fast (less than
> a second versus tens seconds) it is the difference between keeping
> concentrated on the task and have our brain switching to another idea.
> It seems to me that only tests launched with surefire will be able and
> ensured - to run with Junit test.
>
> I believe this sentence illustrates our divergence: you mainly think about
> tests as a tool for the developer, and they have to be fast for the
> developer to use them. That's right.
> I see them as an armor for the application, I want them to find as many
> bugs possible in the actual environment where the code will actually run,
> and if it has a cost for the developer, so be it, as long as tests are
> still run and checked by continuous integration. That's right too.
>
> Overall, both are right and useful. Depending on the test, you might want
> one or the other.
>
> What's possible and that seems like the best thing to me is to have the
> unit-tests in a bundle that run fast with maven-surefire-plugin, and have
> integration tests in another bundle also running the unit-test suite (+
> some other tests) with tycho-surefire-plugin. So you get the best of both:
> unit tests are run fast and keep running fast because they are
> automatically tested using plain JUnit and maven-surefire-plugin; and you
> also have them running as part of the integration tests to also detect bugs
> that depend on the Eclipse runtime mechanism.
> WDYT?
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets
> <http://twitter.com/mickaelistria>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Aurelien Pupier
Senior Software Engineer in JBoss Fuse Tooling team
@apupier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160704/ee460908/attachment.html 

From mistria at redhat.com  Mon Jul  4 06:03:39 2016
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 4 Jul 2016 12:03:39 +0200
Subject: [jbosstools-dev] An Eclipse bug that needs some love
Message-ID: <f5ac4b5f-a5c1-a7d0-f483-e85bffbc8ab3@redhat.com>

Hi all,

I'd like to bring your attention on a bug that I believe can be the 
cause of many performance complaints about Eclipse IDE: 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=494982

I don't know much about the XML editors and the Schema registry in 
Eclipse IDE, but IIRC some of you are much aware of it. It would be nice 
if someone could at least followup on this issue and evaluate how 
difficult/worth it would be to fix it, and then maybe consider planning 
it in JBoss Tools roadmap.

Cheers,

-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160704/73524311/attachment.html 

From manderse at redhat.com  Mon Jul  4 10:10:18 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 04 Jul 2016 16:10:18 +0200
Subject: [jbosstools-dev] Migration to jgit timestamps
In-Reply-To: <CA+QcL12LwGhmOU3hoCfynQySSpLph=kz_j2V5OQd1023Mh+q6w@mail.gmail.com>
References: <CA+QcL114N73n6+zeUGnWQ9ahpum847Tow3tzbXtc2iLvefR8qg@mail.gmail.com>
	<6A20FF77-DC9A-439D-8FC2-B6264D019AF7@redhat.com>
	<d0a9d8a8-3243-2ea2-98fc-6c04c8f0fd9d@redhat.com>
	<CA+QcL12LwGhmOU3hoCfynQySSpLph=kz_j2V5OQd1023Mh+q6w@mail.gmail.com>
Message-ID: <8DC3DBB3-4092-4730-9C55-E422EAFD423A@redhat.com>

Thanks for verifying Nick and Mickael - so I was correct in it is the 
plugins
AND features that will change. Not just the plugins.

I would suggest we ensure we add tests for this so we don't miss it, 
since
I reckon the feature is also included in a feature that might not be 
automatically
upversioned ?

/max


> Or look at the examples I posted on the JIRA [1] . Because
> features/com.jboss.devstudio.core.feature/feature.xml contains
>
>   <plugin id="com.jboss.devstudio.core.central" download-size="0"
> install-size="0" version="0.0.0" unpack="false"/>
>
> therefore its version is bumped to a newer timestamp every time we
> edit anything in com.jboss.devstudio.core.central or cause a new
> version to be produced.
>
> [1] 
> https://issues.jboss.org/browse/JBIDE-13671?focusedCommentId=13259284&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13259284
>
> On Thu, Jun 30, 2016 at 11:48 AM, Mickael Istria <mistria at redhat.com> 
> wrote:
>> On 06/30/2016 05:34 PM, Max Rydahl Andersen wrote:
>>
>> This might already be handed by tycho's jgit mechanism but just 
>> wanted
>>
>> to be sure we didn't state it was just for the plugin if it also
>> includes
>> the feature and all up to whatever product feature.
>>
>> Yeah, see
>> https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers#Feature_version_qualifiers
>>
>> --
>> Mickael Istria
>> Eclipse developer at JBoss, by Red Hat
>> My blog - My Tweets
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From rcernich at redhat.com  Mon Jul  4 10:45:33 2016
From: rcernich at redhat.com (Rob Cernich)
Date: Mon, 4 Jul 2016 10:45:33 -0400 (EDT)
Subject: [jbosstools-dev] An Eclipse bug that needs some love
In-Reply-To: <f5ac4b5f-a5c1-a7d0-f483-e85bffbc8ab3@redhat.com>
References: <f5ac4b5f-a5c1-a7d0-f483-e85bffbc8ab3@redhat.com>
Message-ID: <1248285100.3827355.1467643533791.JavaMail.zimbra@redhat.com>

I wonder if simply adding the schema locally would work around the issue (i.e. no trying to hit an external server to get the schema). That said, I thought most of the standard JavaEE schema were already installed with Eclipse and registered with the XML framework. (Window->Preferences, XML->XML Catalog) 

----- Original Message -----

> Hi all,

> I'd like to bring your attention on a bug that I believe can be the cause of
> many performance complaints about Eclipse IDE:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=494982

> I don't know much about the XML editors and the Schema registry in Eclipse
> IDE, but IIRC some of you are much aware of it. It would be nice if someone
> could at least followup on this issue and evaluate how difficult/worth it
> would be to fix it, and then maybe consider planning it in JBoss Tools
> roadmap.

> Cheers,
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets

> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160704/9cabdf73/attachment.html 

From mistria at redhat.com  Mon Jul  4 10:48:02 2016
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 4 Jul 2016 16:48:02 +0200
Subject: [jbosstools-dev] An Eclipse bug that needs some love
In-Reply-To: <1248285100.3827355.1467643533791.JavaMail.zimbra@redhat.com>
References: <f5ac4b5f-a5c1-a7d0-f483-e85bffbc8ab3@redhat.com>
	<1248285100.3827355.1467643533791.JavaMail.zimbra@redhat.com>
Message-ID: <65446930-22f0-3aab-823e-7cb4ce7e5eac@redhat.com>

On 07/04/2016 04:45 PM, Rob Cernich wrote:
> I wonder if simply adding the schema locally would work around the 
> issue (i.e. no trying to hit an external server to get the schema).  
> That said, I thought most of the standard JavaEE schema were already 
> installed with Eclipse and registered with the XML framework.  
> (Window->Preferences, XML->XML Catalog)
Hey Rob,
Thanks for having a look. Can you please post that on the related 
Bugzilla to hopefully get opinions from other WTP contributors?
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160704/563e7613/attachment-0001.html 

From ggastald at redhat.com  Mon Jul  4 10:49:13 2016
From: ggastald at redhat.com (George Gastaldi)
Date: Mon, 4 Jul 2016 11:49:13 -0300
Subject: [jbosstools-dev] An Eclipse bug that needs some love
In-Reply-To: <1248285100.3827355.1467643533791.JavaMail.zimbra@redhat.com>
References: <f5ac4b5f-a5c1-a7d0-f483-e85bffbc8ab3@redhat.com>
	<1248285100.3827355.1467643533791.JavaMail.zimbra@redhat.com>
Message-ID: <CAMmsnJi3QhfoXcAx=zqKi6Ytjwu9XDejwLdNLmsE9_sMZBdT-g@mail.gmail.com>

I think the main issue is that it happens in the UI thread. Perhaps it
should be moved to another thread and using a ProgressListener somehow?
Em 4 de jul de 2016 11:46, "Rob Cernich" <rcernich at redhat.com> escreveu:

> I wonder if simply adding the schema locally would work around the issue
> (i.e. no trying to hit an external server to get the schema).  That said, I
> thought most of the standard JavaEE schema were already installed with
> Eclipse and registered with the XML framework.  (Window->Preferences,
> XML->XML Catalog)
>
>
> ------------------------------
>
> Hi all,
>
> I'd like to bring your attention on a bug that I believe can be the cause
> of many performance complaints about Eclipse IDE:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=494982
>
> I don't know much about the XML editors and the Schema registry in Eclipse
> IDE, but IIRC some of you are much aware of it. It would be nice if someone
> could at least followup on this issue and evaluate how difficult/worth it
> would be to fix it, and then maybe consider planning it in JBoss Tools
> roadmap.
>
> Cheers,
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets
> <http://twitter.com/mickaelistria>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160704/b1330a8e/attachment.html 

From manderse at redhat.com  Mon Jul  4 15:01:43 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 04 Jul 2016 21:01:43 +0200
Subject: [jbosstools-dev] An Eclipse bug that needs some love
In-Reply-To: <CAMmsnJi3QhfoXcAx=zqKi6Ytjwu9XDejwLdNLmsE9_sMZBdT-g@mail.gmail.com>
References: <f5ac4b5f-a5c1-a7d0-f483-e85bffbc8ab3@redhat.com>
	<1248285100.3827355.1467643533791.JavaMail.zimbra@redhat.com>
	<CAMmsnJi3QhfoXcAx=zqKi6Ytjwu9XDejwLdNLmsE9_sMZBdT-g@mail.gmail.com>
Message-ID: <E1CD1B31-2B91-48C8-82A9-40078B1C040D@redhat.com>

I think to recall Rob Stryker was doing a patch that would fix it so you 
would at least
not get hit by the 'pause' the second time (i.e. cache 404 or 
no-connection responses).

But I don't recall the details. Rob ? Stryker, any memory of this?

/max

> I think the main issue is that it happens in the UI thread. Perhaps it
> should be moved to another thread and using a ProgressListener 
> somehow?
> Em 4 de jul de 2016 11:46, "Rob Cernich" <rcernich at redhat.com> 
> escreveu:
>
>> I wonder if simply adding the schema locally would work around the 
>> issue
>> (i.e. no trying to hit an external server to get the schema).  That 
>> said, I
>> thought most of the standard JavaEE schema were already installed 
>> with
>> Eclipse and registered with the XML framework.  (Window->Preferences,
>> XML->XML Catalog)
>>
>>
>> ------------------------------
>>
>> Hi all,
>>
>> I'd like to bring your attention on a bug that I believe can be the 
>> cause
>> of many performance complaints about Eclipse IDE:
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=494982
>>
>> I don't know much about the XML editors and the Schema registry in 
>> Eclipse
>> IDE, but IIRC some of you are much aware of it. It would be nice if 
>> someone
>> could at least followup on this issue and evaluate how 
>> difficult/worth it
>> would be to fix it, and then maybe consider planning it in JBoss 
>> Tools
>> roadmap.
>>
>> Cheers,
>> --
>> Mickael Istria
>> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
>> My blog <http://mickaelistria.wordpress.com> - My Tweets
>> <http://twitter.com/mickaelistria>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>


> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160704/fc03d3f1/attachment.html 

From nboldt at redhat.com  Mon Jul  4 15:52:01 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 4 Jul 2016 15:52:01 -0400
Subject: [jbosstools-dev] Migration to jgit timestamps
In-Reply-To: <8DC3DBB3-4092-4730-9C55-E422EAFD423A@redhat.com>
References: <CA+QcL114N73n6+zeUGnWQ9ahpum847Tow3tzbXtc2iLvefR8qg@mail.gmail.com>
	<6A20FF77-DC9A-439D-8FC2-B6264D019AF7@redhat.com>
	<d0a9d8a8-3243-2ea2-98fc-6c04c8f0fd9d@redhat.com>
	<CA+QcL12LwGhmOU3hoCfynQySSpLph=kz_j2V5OQd1023Mh+q6w@mail.gmail.com>
	<8DC3DBB3-4092-4730-9C55-E422EAFD423A@redhat.com>
Message-ID: <CA+QcL12VtEDAvfJnvMuTi_gM6sAM2TEapEeL6ATa8Gj_RASTrg@mail.gmail.com>

Based on tests done in the JIRA, if a plugin changes, the features
that contain it, and any features that contain that feature, are also
upversioned. So I'm happy to write tests for this but seems to be
behaving according to Eclipse/OSGi/Tycho rules already.

I suspect too that the baseline comparator test will catch problems
where things are not correctly upversioned, too.

On Mon, Jul 4, 2016 at 10:10 AM, Max Rydahl Andersen
<manderse at redhat.com> wrote:
> Thanks for verifying Nick and Mickael - so I was correct in it is the
> plugins
> AND features that will change. Not just the plugins.
>
> I would suggest we ensure we add tests for this so we don't miss it, since
> I reckon the feature is also included in a feature that might not be
> automatically
> upversioned ?
>
> /max
>
>
>> Or look at the examples I posted on the JIRA [1] . Because
>> features/com.jboss.devstudio.core.feature/feature.xml contains
>>
>>   <plugin id="com.jboss.devstudio.core.central" download-size="0"
>> install-size="0" version="0.0.0" unpack="false"/>
>>
>> therefore its version is bumped to a newer timestamp every time we
>> edit anything in com.jboss.devstudio.core.central or cause a new
>> version to be produced.
>>
>> [1]
>> https://issues.jboss.org/browse/JBIDE-13671?focusedCommentId=13259284&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13259284
>>
>> On Thu, Jun 30, 2016 at 11:48 AM, Mickael Istria <mistria at redhat.com>
>> wrote:
>>>
>>> On 06/30/2016 05:34 PM, Max Rydahl Andersen wrote:
>>>
>>> This might already be handed by tycho's jgit mechanism but just wanted
>>>
>>> to be sure we didn't state it was just for the plugin if it also
>>> includes
>>> the feature and all up to whatever product feature.
>>>
>>> Yeah, see
>>>
>>> https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers#Feature_version_qualifiers
>>>
>>> --
>>> Mickael Istria
>>> Eclipse developer at JBoss, by Red Hat
>>> My blog - My Tweets
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> /max
> http://about.me/maxandersen



-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From ddekany at freemail.hu  Thu Jul  7 17:27:24 2016
From: ddekany at freemail.hu (Daniel Dekany)
Date: Thu, 7 Jul 2016 23:27:24 +0200
Subject: [jbosstools-dev] Any way to make FreeMarker IDE fixes available
	with less delay?
In-Reply-To: <916097661.20160413023325@freemail.hu>
References: <1139481114.20160407233937@freemail.hu>
	<5706D873.2090503@redhat.com>
	<1564144359.20160408083434@freemail.hu>
	<58B67DA7-810A-4E7F-8427-1741A75E6B3C@redhat.com>
	<916097661.20160413023325@freemail.hu>
Message-ID: <1067385354.20160707232724@freemail.hu>

Is it possible to become faster with PR merging on the expense of
thoroughness in the case of FreeMarker IDE, if I'm the one who sent
the PR (or if I have tested a PR)? I understand that there's very
little time for reviewing this plugin, that's why I'm trying to take
more responsibility on myself. Some recent PR-s are less trivial (more
time to thoroughly review) than the earlier merged ones, plus some
similar PR-s weren't even done yet because they build on top of the
ones not merged yet. So I'm a bit worried about how all these will get
in on time. Also, take into account that this plugin is quite broken
and was neglected for so long, so certainly I will only make it better
overall even if I introduce some regressions accidentally.

For convenience, here are some of the pending PR-s:
https://issues.jboss.org/browse/JBIDE-20386
https://issues.jboss.org/browse/JBIDE-22636
https://issues.jboss.org/browse/JBIDE-22656
https://issues.jboss.org/browse/JBIDE-22659


Wednesday, April 13, 2016, 2:33:25 AM, Daniel Dekany wrote:

> Basically, I was thinking about pulling more responsibility on myself.
> That's surely a risk as I'm totally new to Eclipse plugin development,
> and I don't yet know your policies either. So it's very useful if some
> old timer JBoss Tool developers review the PR-s, but often I would
> rather take the risk so that I can quickly fix/update things. That's
> why on the FreeMarker list I asked if we could/should roll our own
> build and update site, which can thus publish things regardless of the
> pace PR-s can be processed (note that that thread has started before
> you guys started reviewing the PR-s). But of course, for me the best
> is if the whole process can stay here. So, who's possibly eligible for
> "reviewing and testing PR's", or how would that work?
>
>
> Monday, April 11, 2016, 11:26:11 AM, Max Rydahl Andersen wrote:
>
>> On 8 Apr 2016, at 8:34, Daniel Dekany wrote:
>>
>>> Thank you very much! To be perfectly clear, I didn't come here to
>>> complain and force JBoss employees to do this. I'm asking if there's a
>>> way to change the overall process somehow. Perhaps not, but, who
>>> knows...
>>
>> There is - we have an updatesite for freemarker site that builds every
>> night, so you can releases/fixes from it more or less immediately.
>>
>> To get more content in, we need more content in PR's to the repos and if
>> someone
>> wants to step up to review and test PR's let us know.
>>
>> As you notice if we come aware of something going stale we do react - to
>> avoid it going
>> stale repeatedly we need someone to have time and skills to push 
>> content.
>>
>> If it was something else you had in mind let me know. In any case, we 
>> are pretty open
>> on what happens with freemarker tooling as long as it keeps (within 
>> reason) being compatible with
>> multiple freemarker versions so it can be used in real projects that end
>> up having wide
>> range of freemarker content.
>>
>> /max
>>
>>>
>>>
>>> Friday, April 8, 2016, 12:00:19 AM, Alexey Kazakov wrote:
>>>
>>>> Sorry for such long delays.
>>>> I pushed the 4-month old PR to the master. We are currently very busy
>>>> preparing JBoss Tools 4.3.1 release (should happen in two weeks) but
>>>> then we will find some time to review the other two PRs.
>>>>
>>>> Thanks for your contributions!
>>>>
>>>> On 04/07/2016 05:39 PM, Daniel Dekany wrote:
>>>>> I'm a contributor at the FreeMarker project, and would like to help
>>>>> maintaining JBoss Tools / FreeMarker IDE
>>>>> (org.jboss.ide.eclipse.freemarker). The problem I'm facing is that
>>>>> pull requests get merged with too big delay. For example, I have a 
>>>>> few
>>>>> simple pull requests waiting for 4 months now, because of the 
>>>>> limited
>>>>> resources available for reviewing them (as I was told). I wonder if 
>>>>> I
>>>>> can help improving this situation somehow.
>>>>>
>>>>> If the above can be addressed, then I guess I could specify the
>>>>> nightly build update site URL to the users, so that they aren't
>>>>> affected by the release cycle of JBoss Tools. After all, FreeMarker
>>>>> IDE is technically quite independent of it.

-- 
Thanks,
 Daniel Dekany


From alkazako at redhat.com  Thu Jul  7 19:51:45 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Thu, 7 Jul 2016 19:51:45 -0400
Subject: [jbosstools-dev] Any way to make FreeMarker IDE fixes available
 with less delay?
In-Reply-To: <1067385354.20160707232724@freemail.hu>
References: <1139481114.20160407233937@freemail.hu>
	<5706D873.2090503@redhat.com> <1564144359.20160408083434@freemail.hu>
	<58B67DA7-810A-4E7F-8427-1741A75E6B3C@redhat.com>
	<916097661.20160413023325@freemail.hu>
	<1067385354.20160707232724@freemail.hu>
Message-ID: <577EEB11.7030601@redhat.com>

Hi Daniel,

Sorry for the delays with PR review.
I merged one PR.
Regarding others... What will definitely help to dramatically speed up 
PR merging is a good automated test coverage.
Please add tests for your PRs and fix licenses in the headers of new 
classes you are adding with these PRs and we will merge them ASAP.
We also now have a dedicated developer who will review freemarker PRs.
But please add tests for your PRs.
If everything goes well we can consider giving you direct write access 
to the freemarker repo in the future.

Thank you.

On 07/07/2016 05:27 PM, Daniel Dekany wrote:
> Is it possible to become faster with PR merging on the expense of
> thoroughness in the case of FreeMarker IDE, if I'm the one who sent
> the PR (or if I have tested a PR)? I understand that there's very
> little time for reviewing this plugin, that's why I'm trying to take

> more responsibility on myself. Some recent PR-s are less trivial (more
> time to thoroughly review) than the earlier merged ones, plus some
> similar PR-s weren't even done yet because they build on top of the
> ones not merged yet. So I'm a bit worried about how all these will get
> in on time. Also, take into account that this plugin is quite broken
> and was neglected for so long, so certainly I will only make it better
> overall even if I introduce some regressions accidentally.
>
> For convenience, here are some of the pending PR-s:
> https://issues.jboss.org/browse/JBIDE-20386
> https://issues.jboss.org/browse/JBIDE-22636
> https://issues.jboss.org/browse/JBIDE-22656
> https://issues.jboss.org/browse/JBIDE-22659
>
>
> Wednesday, April 13, 2016, 2:33:25 AM, Daniel Dekany wrote:
>
>> Basically, I was thinking about pulling more responsibility on myself.
>> That's surely a risk as I'm totally new to Eclipse plugin development,
>> and I don't yet know your policies either. So it's very useful if some
>> old timer JBoss Tool developers review the PR-s, but often I would
>> rather take the risk so that I can quickly fix/update things. That's
>> why on the FreeMarker list I asked if we could/should roll our own
>> build and update site, which can thus publish things regardless of the
>> pace PR-s can be processed (note that that thread has started before
>> you guys started reviewing the PR-s). But of course, for me the best
>> is if the whole process can stay here. So, who's possibly eligible for
>> "reviewing and testing PR's", or how would that work?
>>
>>
>> Monday, April 11, 2016, 11:26:11 AM, Max Rydahl Andersen wrote:
>>
>>> On 8 Apr 2016, at 8:34, Daniel Dekany wrote:
>>>
>>>> Thank you very much! To be perfectly clear, I didn't come here to
>>>> complain and force JBoss employees to do this. I'm asking if there's a
>>>> way to change the overall process somehow. Perhaps not, but, who
>>>> knows...
>>> There is - we have an updatesite for freemarker site that builds every
>>> night, so you can releases/fixes from it more or less immediately.
>>>
>>> To get more content in, we need more content in PR's to the repos and if
>>> someone
>>> wants to step up to review and test PR's let us know.
>>>
>>> As you notice if we come aware of something going stale we do react - to
>>> avoid it going
>>> stale repeatedly we need someone to have time and skills to push
>>> content.
>>>
>>> If it was something else you had in mind let me know. In any case, we
>>> are pretty open
>>> on what happens with freemarker tooling as long as it keeps (within
>>> reason) being compatible with
>>> multiple freemarker versions so it can be used in real projects that end
>>> up having wide
>>> range of freemarker content.
>>>
>>> /max
>>>
>>>>
>>>> Friday, April 8, 2016, 12:00:19 AM, Alexey Kazakov wrote:
>>>>
>>>>> Sorry for such long delays.
>>>>> I pushed the 4-month old PR to the master. We are currently very busy
>>>>> preparing JBoss Tools 4.3.1 release (should happen in two weeks) but
>>>>> then we will find some time to review the other two PRs.
>>>>>
>>>>> Thanks for your contributions!
>>>>>
>>>>> On 04/07/2016 05:39 PM, Daniel Dekany wrote:
>>>>>> I'm a contributor at the FreeMarker project, and would like to help
>>>>>> maintaining JBoss Tools / FreeMarker IDE
>>>>>> (org.jboss.ide.eclipse.freemarker). The problem I'm facing is that
>>>>>> pull requests get merged with too big delay. For example, I have a
>>>>>> few
>>>>>> simple pull requests waiting for 4 months now, because of the
>>>>>> limited
>>>>>> resources available for reviewing them (as I was told). I wonder if
>>>>>> I
>>>>>> can help improving this situation somehow.
>>>>>>
>>>>>> If the above can be addressed, then I guess I could specify the
>>>>>> nightly build update site URL to the users, so that they aren't
>>>>>> affected by the release cycle of JBoss Tools. After all, FreeMarker
>>>>>> IDE is technically quite independent of it.


From ddekany at freemail.hu  Fri Jul  8 02:52:02 2016
From: ddekany at freemail.hu (Daniel Dekany)
Date: Fri, 8 Jul 2016 08:52:02 +0200
Subject: [jbosstools-dev] Any way to make FreeMarker IDE fixes available
	with less delay?
In-Reply-To: <577EEB11.7030601@redhat.com>
References: <1139481114.20160407233937@freemail.hu>
	<5706D873.2090503@redhat.com>
	<1564144359.20160408083434@freemail.hu>
	<58B67DA7-810A-4E7F-8427-1741A75E6B3C@redhat.com>
	<916097661.20160413023325@freemail.hu>
	<1067385354.20160707232724@freemail.hu>
	<577EEB11.7030601@redhat.com>
Message-ID: <1663741876.20160708085202@freemail.hu>

Friday, July 8, 2016, 1:51:45 AM, Alexey Kazakov wrote:

> Hi Daniel,
>
> Sorry for the delays with PR review.

Don't... just merge. ;)

> I merged one PR.
> Regarding others... What will definitely help to dramatically speed up
> PR merging is a good automated test coverage.
> Please add tests for your PRs and fix licenses in the headers of new
> classes you are adding with these PRs and we will merge them ASAP.

Most fixed functionality had no test coverage earlier either, so I'm
fixing things without not fixing the lack of JUnit tests. Hence it
would be probably a better strategy to be more flexible for now, and
handle improving JUnit coverage as a separate issue.

(Sorry for the header oversights. Once the pending PR-s are in, I
will run a header replacer on the project.)

> We also now have a dedicated developer who will review freemarker PRs.

Sounds good, thank you!

> But please add tests for your PRs.
> If everything goes well we can consider giving you direct write access
> to the freemarker repo in the future.
>
> Thank you.
>
> On 07/07/2016 05:27 PM, Daniel Dekany wrote:
>> Is it possible to become faster with PR merging on the expense of
>> thoroughness in the case of FreeMarker IDE, if I'm the one who sent
>> the PR (or if I have tested a PR)? I understand that there's very
>> little time for reviewing this plugin, that's why I'm trying to take
>
>> more responsibility on myself. Some recent PR-s are less trivial (more
>> time to thoroughly review) than the earlier merged ones, plus some
>> similar PR-s weren't even done yet because they build on top of the
>> ones not merged yet. So I'm a bit worried about how all these will get
>> in on time. Also, take into account that this plugin is quite broken
>> and was neglected for so long, so certainly I will only make it better
>> overall even if I introduce some regressions accidentally.
>>
>> For convenience, here are some of the pending PR-s:
>> https://issues.jboss.org/browse/JBIDE-20386
>> https://issues.jboss.org/browse/JBIDE-22636
>> https://issues.jboss.org/browse/JBIDE-22656
>> https://issues.jboss.org/browse/JBIDE-22659
>>
>>
>> Wednesday, April 13, 2016, 2:33:25 AM, Daniel Dekany wrote:
>>
>>> Basically, I was thinking about pulling more responsibility on myself.
>>> That's surely a risk as I'm totally new to Eclipse plugin development,
>>> and I don't yet know your policies either. So it's very useful if some
>>> old timer JBoss Tool developers review the PR-s, but often I would
>>> rather take the risk so that I can quickly fix/update things. That's
>>> why on the FreeMarker list I asked if we could/should roll our own
>>> build and update site, which can thus publish things regardless of the
>>> pace PR-s can be processed (note that that thread has started before
>>> you guys started reviewing the PR-s). But of course, for me the best
>>> is if the whole process can stay here. So, who's possibly eligible for
>>> "reviewing and testing PR's", or how would that work?
>>>
>>>
>>> Monday, April 11, 2016, 11:26:11 AM, Max Rydahl Andersen wrote:
>>>
>>>> On 8 Apr 2016, at 8:34, Daniel Dekany wrote:
>>>>
>>>>> Thank you very much! To be perfectly clear, I didn't come here to
>>>>> complain and force JBoss employees to do this. I'm asking if there's a
>>>>> way to change the overall process somehow. Perhaps not, but, who
>>>>> knows...
>>>> There is - we have an updatesite for freemarker site that builds every
>>>> night, so you can releases/fixes from it more or less immediately.
>>>>
>>>> To get more content in, we need more content in PR's to the repos and if
>>>> someone
>>>> wants to step up to review and test PR's let us know.
>>>>
>>>> As you notice if we come aware of something going stale we do react - to
>>>> avoid it going
>>>> stale repeatedly we need someone to have time and skills to push
>>>> content.
>>>>
>>>> If it was something else you had in mind let me know. In any case, we
>>>> are pretty open
>>>> on what happens with freemarker tooling as long as it keeps (within
>>>> reason) being compatible with
>>>> multiple freemarker versions so it can be used in real projects that end
>>>> up having wide
>>>> range of freemarker content.
>>>>
>>>> /max
>>>>
>>>>>
>>>>> Friday, April 8, 2016, 12:00:19 AM, Alexey Kazakov wrote:
>>>>>
>>>>>> Sorry for such long delays.
>>>>>> I pushed the 4-month old PR to the master. We are currently very busy
>>>>>> preparing JBoss Tools 4.3.1 release (should happen in two weeks) but
>>>>>> then we will find some time to review the other two PRs.
>>>>>>
>>>>>> Thanks for your contributions!
>>>>>>
>>>>>> On 04/07/2016 05:39 PM, Daniel Dekany wrote:
>>>>>>> I'm a contributor at the FreeMarker project, and would like to help
>>>>>>> maintaining JBoss Tools / FreeMarker IDE
>>>>>>> (org.jboss.ide.eclipse.freemarker). The problem I'm facing is that
>>>>>>> pull requests get merged with too big delay. For example, I have a
>>>>>>> few
>>>>>>> simple pull requests waiting for 4 months now, because of the
>>>>>>> limited
>>>>>>> resources available for reviewing them (as I was told). I wonder if
>>>>>>> I
>>>>>>> can help improving this situation somehow.
>>>>>>>
>>>>>>> If the above can be addressed, then I guess I could specify the
>>>>>>> nightly build update site URL to the users, so that they aren't
>>>>>>> affected by the release cycle of JBoss Tools. After all, FreeMarker
>>>>>>> IDE is technically quite independent of it.
>
>

-- 
Thanks,
 Daniel Dekany


From alkazako at redhat.com  Fri Jul  8 14:43:27 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Fri, 8 Jul 2016 14:43:27 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
Message-ID: <577FF44F.50709@redhat.com>

Hi all,

Just a reminder that our initial plan was to release milestones of JBoss 
Tools after every sprint and work on automation of this process so it 
doesn't require a lot of efforts any manual work.
But because of holidays in Canada, USA and Czech Republic plus busy Red 
Hat Summit week before that we skipped public release of JBoss Tools 
4.4.1.AM1.
Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with 
codefreeze on July 21 (Thursday). This will be our first public 
milestone release for JBT 4.4.1.
The release schedule is available here - 
https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page

Thank you.

From alkazako at redhat.com  Fri Jul  8 15:06:55 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Fri, 8 Jul 2016 15:06:55 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <577FF44F.50709@redhat.com>
References: <577FF44F.50709@redhat.com>
Message-ID: <577FF9CF.7050503@redhat.com>

For clarification. We will release JBoss Tools AM2 only. We do not 
release any devstudio milestones.

On 07/08/2016 02:43 PM, Alexey Kazakov wrote:
> Hi all,
>
> Just a reminder that our initial plan was to release milestones of JBoss
> Tools after every sprint and work on automation of this process so it
> doesn't require a lot of efforts any manual work.
> But because of holidays in Canada, USA and Czech Republic plus busy Red
> Hat Summit week before that we skipped public release of JBoss Tools
> 4.4.1.AM1.
> Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with
> codefreeze on July 21 (Thursday). This will be our first public
> milestone release for JBT 4.4.1.
> The release schedule is available here -
> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>
> Thank you.
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From aer-bot at ctrlflow.com  Sun Jul 10 23:30:00 2016
From: aer-bot at ctrlflow.com (Automated Error Reporting Bot)
Date: Mon, 11 Jul 2016 03:30:00 +0000 (UTC)
Subject: [jbosstools-dev] [aeri] Weekly JBoss Tools Error Reports Digest
Message-ID: <1321592283.0.1468207801023.JavaMail.ec2-user@aeri-rh>

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/3faea14b/attachment-0001.html 

From ggastald at redhat.com  Mon Jul 11 12:22:42 2016
From: ggastald at redhat.com (George Gastaldi)
Date: Mon, 11 Jul 2016 13:22:42 -0300
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
	issues?
Message-ID: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>

Hi,

I noticed that the AERI bot opens some JIRA according to the issues
reported by the users. I am having a hard time trying to reproduce these
errors, mostly because I don't know what the user did to make that happen.
How can I have access to the steps performed by the user when the error
occurred?

I think that opening an issue with a Stacktrace is not that useful if you
don't know how to reproduce that error locally.

Best Regards,

*George Gastaldi*

https://onename.com/gastaldi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/a28a5837/attachment.html 

From ldimaggi at redhat.com  Mon Jul 11 12:34:19 2016
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Mon, 11 Jul 2016 12:34:19 -0400
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
	issues?
In-Reply-To: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
Message-ID: <CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>

I thought that we had agreed that Dev + QE component leads would review the
(weekly) reports from AERI and then log JIRAs....selectively.

-- Len

On Mon, Jul 11, 2016 at 12:22 PM, George Gastaldi <ggastald at redhat.com>
wrote:

> Hi,
>
> I noticed that the AERI bot opens some JIRA according to the issues
> reported by the users. I am having a hard time trying to reproduce these
> errors, mostly because I don't know what the user did to make that happen.
> How can I have access to the steps performed by the user when the error
> occurred?
>
> I think that opening an issue with a Stacktrace is not that useful if you
> don't know how to reproduce that error locally.
>
> Best Regards,
>
> *George Gastaldi*
>
> https://onename.com/gastaldi
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Len DiMaggio (ldimaggi at redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886  USA
tel:  978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/630f1cb4/attachment.html 

From alkazako at redhat.com  Mon Jul 11 12:44:19 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 11 Jul 2016 12:44:19 -0400
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
 issues?
In-Reply-To: <CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
Message-ID: <5783CCE3.2030805@redhat.com>

George, AFAIK these JIRAs are not created automatically. If you see a 
JIRA created by AERI then someone created it via AERI web interface when 
reviewing reports.
And as Len said, every component lead is supposed to review the reports 
weekly and create JIRAs/close reports for his/her components.
If you someone doesn't have access to AERI then please let us know.

On 07/11/2016 12:34 PM, Leonard Dimaggio wrote:
> I thought that we had agreed that Dev + QE component leads would 
> review the (weekly) reports from AERI and then log JIRAs....selectively.
>
> -- Len
>
> On Mon, Jul 11, 2016 at 12:22 PM, George Gastaldi <ggastald at redhat.com 
> <mailto:ggastald at redhat.com>> wrote:
>
>     Hi,
>
>     I noticed that the AERI bot opens some JIRA according to the
>     issues reported by the users. I am having a hard time trying to
>     reproduce these errors, mostly because I don't know what the user
>     did to make that happen. How can I have access to the steps
>     performed by the user when the error occurred?
>
>     I think that opening an issue with a Stacktrace is not that useful
>     if you don't know how to reproduce that error locally.
>
>     Best Regards,
>
>     *George Gastaldi*
>
>     https://onename.com/gastaldi
>
>     _______________________________________________
>     jbosstools-dev mailing list
>     jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
>
> -- 
> Len DiMaggio (ldimaggi at redhat.com <mailto:ldimaggi at redhat.com>)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/4205553e/attachment.html 

From ggastald at redhat.com  Mon Jul 11 12:49:23 2016
From: ggastald at redhat.com (George Gastaldi)
Date: Mon, 11 Jul 2016 13:49:23 -0300
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
	issues?
In-Reply-To: <5783CCE3.2030805@redhat.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
Message-ID: <CAMmsnJigEmUU55hioSrHNHfH8nC-_h82+EAsgPxnjR+Be4HeOw@mail.gmail.com>

Thanks Alexey,

The issues I was referring to were:
https://issues.jboss.org/browse/JBIDE-22705 and
https://issues.jboss.org/browse/JBIDE-22706
I don't remember creating those issues through the web interface, perhaps
someone else did it? Anyway, I was just wondering if there is some way to
have the user steps used to reproduce those exceptions from AERI, otherwise
I'll just close them as Cannot Reproduce.

Thank you

*George Gastaldi*

https://onename.com/gastaldi

On Mon, Jul 11, 2016 at 1:44 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

> George, AFAIK these JIRAs are not created automatically. If you see a JIRA
> created by AERI then someone created it via AERI web interface when
> reviewing reports.
> And as Len said, every component lead is supposed to review the reports
> weekly and create JIRAs/close reports for his/her components.
> If you someone doesn't have access to AERI then please let us know.
>
> On 07/11/2016 12:34 PM, Leonard Dimaggio wrote:
>
> I thought that we had agreed that Dev + QE component leads would review
> the (weekly) reports from AERI and then log JIRAs....selectively.
>
> -- Len
>
> On Mon, Jul 11, 2016 at 12:22 PM, George Gastaldi <ggastald at redhat.com>
> wrote:
>
>> Hi,
>>
>> I noticed that the AERI bot opens some JIRA according to the issues
>> reported by the users. I am having a hard time trying to reproduce these
>> errors, mostly because I don't know what the user did to make that happen.
>> How can I have access to the steps performed by the user when the error
>> occurred?
>>
>> I think that opening an issue with a Stacktrace is not that useful if you
>> don't know how to reproduce that error locally.
>>
>> Best Regards,
>>
>> *George Gastaldi*
>>
>> https://onename.com/gastaldi
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
>
> --
> Len DiMaggio (ldimaggi at redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing listjbosstools-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/aecb46bc/attachment-0001.html 

From alkazako at redhat.com  Mon Jul 11 13:00:00 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 11 Jul 2016 13:00:00 -0400
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
 issues?
In-Reply-To: <CAMmsnJigEmUU55hioSrHNHfH8nC-_h82+EAsgPxnjR+Be4HeOw@mail.gmail.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
	<CAMmsnJigEmUU55hioSrHNHfH8nC-_h82+EAsgPxnjR+Be4HeOw@mail.gmail.com>
Message-ID: <5783D090.2040802@redhat.com>


On 07/11/2016 12:49 PM, George Gastaldi wrote:
> Thanks Alexey,
>
> The issues I was referring to were: 
> https://issues.jboss.org/browse/JBIDE-22705 and 
> https://issues.jboss.org/browse/JBIDE-22706
> I don't remember creating those issues through the web interface, 
> perhaps someone else did it?

Maybe someone from QE?

> Anyway, I was just wondering if there is some way to have the user 
> steps used to reproduce those exceptions from AERI, otherwise I'll 
> just close them as Cannot Reproduce.

If these exceptions do not reported often and you don't see what could 
be the reason for that then I'm not sure there is something we can do 
with such reports.
But if they are reported often by different users then it worth a deep 
investigation.
Marcel, is there any way to interact with reporters after submitting a 
report?

Thanks.

>
> Thank you
>
> *George Gastaldi*
>
> https://onename.com/gastaldi
>
> On Mon, Jul 11, 2016 at 1:44 PM, Alexey Kazakov <alkazako at redhat.com 
> <mailto:alkazako at redhat.com>> wrote:
>
>     George, AFAIK these JIRAs are not created automatically. If you
>     see a JIRA created by AERI then someone created it via AERI web
>     interface when reviewing reports.
>     And as Len said, every component lead is supposed to review the
>     reports weekly and create JIRAs/close reports for his/her components.
>     If you someone doesn't have access to AERI then please let us know.
>
>     On 07/11/2016 12:34 PM, Leonard Dimaggio wrote:
>>     I thought that we had agreed that Dev + QE component leads would
>>     review the (weekly) reports from AERI and then log
>>     JIRAs....selectively.
>>
>>     -- Len
>>
>>     On Mon, Jul 11, 2016 at 12:22 PM, George Gastaldi
>>     <ggastald at redhat.com <mailto:ggastald at redhat.com>> wrote:
>>
>>         Hi,
>>
>>         I noticed that the AERI bot opens some JIRA according to the
>>         issues reported by the users. I am having a hard time trying
>>         to reproduce these errors, mostly because I don't know what
>>         the user did to make that happen. How can I have access to
>>         the steps performed by the user when the error occurred?
>>
>>         I think that opening an issue with a Stacktrace is not that
>>         useful if you don't know how to reproduce that error locally.
>>
>>         Best Regards,
>>
>>         *George Gastaldi*
>>
>>         https://onename.com/gastaldi
>>
>>         _______________________________________________
>>         jbosstools-dev mailing list
>>         jbosstools-dev at lists.jboss.org
>>         <mailto:jbosstools-dev at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>>
>>     -- 
>>     Len DiMaggio (ldimaggi at redhat.com <mailto:ldimaggi at redhat.com>)
>>     JBoss by Red Hat
>>     314 Littleton Road
>>     Westford, MA 01886  USA
>>     tel: 978.392.3179 <tel:978.392.3179>
>>     cell: 781.472.9912 <tel:781.472.9912>
>>     http://www.redhat.com
>>     http://community.jboss.org/people/ldimaggio
>>
>>
>>
>>
>>     _______________________________________________
>>     jbosstools-dev mailing list
>>     jbosstools-dev at lists.jboss.org
>>     <mailto:jbosstools-dev at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/6c0a88fb/attachment.html 

From ldimaggi at redhat.com  Mon Jul 11 13:06:47 2016
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Mon, 11 Jul 2016 13:06:47 -0400
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
	issues?
In-Reply-To: <5783D090.2040802@redhat.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
	<CAMmsnJigEmUU55hioSrHNHfH8nC-_h82+EAsgPxnjR+Be4HeOw@mail.gmail.com>
	<5783D090.2040802@redhat.com>
Message-ID: <CA+qK+9mO1tD08OTnb2zqKA42M70GFhraXfMM_-NDZm7XY=eY7A@mail.gmail.com>

I don't think it was QE - but - I was out all last week - maybe someone did
something....   ;-)

On Mon, Jul 11, 2016 at 1:00 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

>
> On 07/11/2016 12:49 PM, George Gastaldi wrote:
>
> Thanks Alexey,
>
> The issues I was referring to were:
> <https://issues.jboss.org/browse/JBIDE-22705>
> https://issues.jboss.org/browse/JBIDE-22705 and
> https://issues.jboss.org/browse/JBIDE-22706
> I don't remember creating those issues through the web interface, perhaps
> someone else did it?
>
>
> Maybe someone from QE?
>
> Anyway, I was just wondering if there is some way to have the user steps
> used to reproduce those exceptions from AERI, otherwise I'll just close
> them as Cannot Reproduce.
>
>
> If these exceptions do not reported often and you don't see what could be
> the reason for that then I'm not sure there is something we can do with
> such reports.
> But if they are reported often by different users then it worth a deep
> investigation.
> Marcel, is there any way to interact with reporters after submitting a
> report?
>
> Thanks.
>
>
>
> Thank you
>
> *George Gastaldi*
>
> https://onename.com/gastaldi
>
> On Mon, Jul 11, 2016 at 1:44 PM, Alexey Kazakov <alkazako at redhat.com>
> wrote:
>
>> George, AFAIK these JIRAs are not created automatically. If you see a
>> JIRA created by AERI then someone created it via AERI web interface when
>> reviewing reports.
>> And as Len said, every component lead is supposed to review the reports
>> weekly and create JIRAs/close reports for his/her components.
>> If you someone doesn't have access to AERI then please let us know.
>>
>> On 07/11/2016 12:34 PM, Leonard Dimaggio wrote:
>>
>> I thought that we had agreed that Dev + QE component leads would review
>> the (weekly) reports from AERI and then log JIRAs....selectively.
>>
>> -- Len
>>
>> On Mon, Jul 11, 2016 at 12:22 PM, George Gastaldi < <ggastald at redhat.com>
>> ggastald at redhat.com> wrote:
>>
>>> Hi,
>>>
>>> I noticed that the AERI bot opens some JIRA according to the issues
>>> reported by the users. I am having a hard time trying to reproduce these
>>> errors, mostly because I don't know what the user did to make that happen.
>>> How can I have access to the steps performed by the user when the error
>>> occurred?
>>>
>>> I think that opening an issue with a Stacktrace is not that useful if
>>> you don't know how to reproduce that error locally.
>>>
>>> Best Regards,
>>>
>>> *George Gastaldi*
>>>
>>> <https://onename.com/gastaldi>https://onename.com/gastaldi
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>>
>>
>> --
>> Len DiMaggio ( <ldimaggi at redhat.com>ldimaggi at redhat.com)
>> JBoss by Red Hat
>> 314 Littleton Road
>> Westford, MA 01886  USA
>> tel:  978.392.3179
>> cell: 781.472.9912
>> http://www.redhat.com
>> http://community.jboss.org/people/ldimaggio
>>
>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing listjbosstools-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>
>


-- 
Len DiMaggio (ldimaggi at redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886  USA
tel:  978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/22f28855/attachment-0001.html 

From ibuziuk at redhat.com  Mon Jul 11 14:06:02 2016
From: ibuziuk at redhat.com (Ilya Buziuk)
Date: Mon, 11 Jul 2016 20:06:02 +0200
Subject: [jbosstools-dev] Zero AERI repports for BrowserSim / CordovaSim /
	VPE components
Message-ID: <CACrcdncrP0ps=8bmy66c=NuTq3B7uCEf_PXEX4YOjqo=k-_NYQ@mail.gmail.com>

Hi, Marcel
I was not able to find any AERI reports for BrowserSim / CordovaSim / VPE
components which is quite suspicious taking in consideration the size of
the code base. Could you please check if AERI is setup correctly for those
components ?
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/412f8292/attachment.html 

From marcel.bruch at codetrails.com  Mon Jul 11 14:48:57 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Mon, 11 Jul 2016 20:48:57 +0200
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
	issues?
In-Reply-To: <5783D090.2040802@redhat.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
	<CAMmsnJigEmUU55hioSrHNHfH8nC-_h82+EAsgPxnjR+Be4HeOw@mail.gmail.com>
	<5783D090.2040802@redhat.com>
Message-ID: <B5DD59A8-4B8D-4E18-94A1-A4BDDA0BA934@codetrails.com>


> On 11 Jul 2016, at 19:00, Alexey Kazakov <alkazako at redhat.com> wrote:
> 
> Marcel, is there any way to interact with reporters after submitting a report?

Yes. Multiple ways.


1. If the reporter left an email address, you can contact them by email. See the ?Contact X reporters?? link on the ?reporters? panel on the problem page. This, however, only makes sense when the problem is relatively new b/c users usually can?t remember what they did 4 weeks in the past to (re)produce the error.



2. If a problem is turned into a bug report, there is a checkbox whether to inform all reporters about the newly crelated bug report. If the comment in Jira states something like ?need steps to reproduce?, users may help. In addition, every new reporter will be pointed to this bug report when he/she experiences this problem on his machine. This increases the likelihood that a user provides further details (but after the bug is created).




3. Set the problem resolution (w/ or w/o JIRA ticket) to ?cannot reproduce? and set an additional ?custom resolution message?. These messages are displayed to new users when the submit an error report that matched this problem.




4. Set one (or more) needinfo flags. Problems tagged with needinfo are more displayed differently / attract the users attention with special icons etc.:









FWIW, the next version of the error reporter will offer a rich feature-set of needinfo flags for different purposes. E.g. for classloading problems AERI will run a local classpath analysis *before submission* and attach it to the error report and a few things more. I?ll send a longer description later this week.


For now, I?d go with approach 3, ?close" with ?cannot reproduce?. 

If you wish, I can prepare a monthly email digests that summarizes all those problems in a separate email for further review. I can also set up an automated action that ?reopens" these problems whenever a new user comment arrives. WDYT?

Marcel




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/0691d354/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-07-11 at 19.56.28.png
Type: image/png
Size: 38925 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/0691d354/attachment-0004.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-07-11 at 19.58.23.png
Type: image/png
Size: 46855 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/0691d354/attachment-0005.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-07-11 at 20.06.24.png
Type: image/png
Size: 35977 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/0691d354/attachment-0006.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-07-11 at 20.07.00.png
Type: image/png
Size: 18401 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/0691d354/attachment-0007.png 

From ggastald at redhat.com  Mon Jul 11 14:53:58 2016
From: ggastald at redhat.com (George Gastaldi)
Date: Mon, 11 Jul 2016 15:53:58 -0300
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
	issues?
In-Reply-To: <B5DD59A8-4B8D-4E18-94A1-A4BDDA0BA934@codetrails.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
	<CAMmsnJigEmUU55hioSrHNHfH8nC-_h82+EAsgPxnjR+Be4HeOw@mail.gmail.com>
	<5783D090.2040802@redhat.com>
	<B5DD59A8-4B8D-4E18-94A1-A4BDDA0BA934@codetrails.com>
Message-ID: <CAMmsnJhXLZBkK3gn32Y-7x1Nr6-L4rz4evDP-Ted_CU7p8WQ6A@mail.gmail.com>

That looks awesome. Is there any way to get in touch with the original
reporter? How would the needinfo flags help in this case?
Em 11 de jul de 2016 15:49, "Marcel Bruch" <marcel.bruch at codetrails.com>
escreveu:

>
> On 11 Jul 2016, at 19:00, Alexey Kazakov <alkazako at redhat.com> wrote:
>
> Marcel, is there any way to interact with reporters after submitting a
> report?
>
>
> Yes. Multiple ways.
>
>
> 1. If the reporter left an email address, you can contact them by email.
> See the ?Contact X reporters?? link on the ?reporters? panel on the problem
> page. This, however, only makes sense when the problem is relatively new
> b/c users usually can?t remember what they did 4 weeks in the past to
> (re)produce the error.
>
>
>
> 2. If a problem is turned into a bug report, there is a checkbox whether
> to inform all reporters about the newly crelated bug report. If the comment
> in Jira states something like ?need steps to reproduce?, users may help. In
> addition, every new reporter will be pointed to this bug report when he/she
> experiences this problem on his machine. This increases the likelihood that
> a user provides further details (but after the bug is created).
>
>
>
> 3. Set the problem resolution (w/ or w/o JIRA ticket) to ?cannot
> reproduce? and set an additional ?custom resolution message?. These
> messages are displayed to new users when the submit an error report that
> matched this problem.
>
>
>
> 4. Set one (or more) needinfo flags. Problems tagged with needinfo are
> more displayed differently / attract the users attention with special icons
> etc.:
>
>
>
>
>
>
>
>
> FWIW, the next version of the error reporter will offer a rich feature-set
> of needinfo flags for different purposes. E.g. for classloading problems
> AERI will run a local classpath analysis *before submission* and attach it
> to the error report and a few things more. I?ll send a longer description
> later this week.
>
>
> For now, I?d go with approach 3, ?close" with ?cannot reproduce?.
>
> If you wish, I can prepare a monthly email digests that summarizes all
> those problems in a separate email for further review. I can also set up an
> automated action that ?reopens" these problems whenever a new user comment
> arrives. WDYT?
>
> Marcel
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/69cff78a/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-07-11 at 20.06.24.png
Type: image/png
Size: 35977 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/69cff78a/attachment-0004.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-07-11 at 20.07.00.png
Type: image/png
Size: 18401 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/69cff78a/attachment-0005.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-07-11 at 19.58.23.png
Type: image/png
Size: 46855 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/69cff78a/attachment-0006.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-07-11 at 19.56.28.png
Type: image/png
Size: 38925 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/69cff78a/attachment-0007.png 

From alkazako at redhat.com  Mon Jul 11 14:54:55 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 11 Jul 2016 14:54:55 -0400
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
 issues?
In-Reply-To: <B5DD59A8-4B8D-4E18-94A1-A4BDDA0BA934@codetrails.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
	<CAMmsnJigEmUU55hioSrHNHfH8nC-_h82+EAsgPxnjR+Be4HeOw@mail.gmail.com>
	<5783D090.2040802@redhat.com>
	<B5DD59A8-4B8D-4E18-94A1-A4BDDA0BA934@codetrails.com>
Message-ID: <5783EB7F.1020606@redhat.com>

Thank you Marcel! Very helpful.

On 07/11/2016 02:48 PM, Marcel Bruch wrote:
> If you wish, I can prepare a monthly email digests that summarizes all 
> those problems in a separate email for further review.
Maybe later. I don't think we need more emails from AERI at this point.

> I can also set up an automated action that ?reopens" these problems 
> whenever a new user comment arrives. WDYT?
Yes please. This would be helpful.

>
> Marcel
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/a18e360b/attachment.html 

From apupier at redhat.com  Mon Jul 11 14:36:57 2016
From: apupier at redhat.com (Aurelien Pupier)
Date: Mon, 11 Jul 2016 20:36:57 +0200
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
	issues?
In-Reply-To: <CA+qK+9mO1tD08OTnb2zqKA42M70GFhraXfMM_-NDZm7XY=eY7A@mail.gmail.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
	<CAMmsnJigEmUU55hioSrHNHfH8nC-_h82+EAsgPxnjR+Be4HeOw@mail.gmail.com>
	<5783D090.2040802@redhat.com>
	<CA+qK+9mO1tD08OTnb2zqKA42M70GFhraXfMM_-NDZm7XY=eY7A@mail.gmail.com>
Message-ID: <CAFNb52eG7aYoUTu1_AEL5su-US8BE6vB+hTt00q25Uvoai=16Q@mail.gmail.com>

Hi,

through AERi interface:
- if user has provided his email, you can send him an e-mail
[image: Inline image 3]
- Otherwise, you can change the status of the incident and ask for more
details in Needinfos field
[image: Inline image 2]

On Mon, Jul 11, 2016 at 7:06 PM, Leonard Dimaggio <ldimaggi at redhat.com>
wrote:

> I don't think it was QE - but - I was out all last week - maybe someone
> did something....   ;-)
>
> On Mon, Jul 11, 2016 at 1:00 PM, Alexey Kazakov <alkazako at redhat.com>
> wrote:
>
>>
>> On 07/11/2016 12:49 PM, George Gastaldi wrote:
>>
>> Thanks Alexey,
>>
>> The issues I was referring to were:
>> <https://issues.jboss.org/browse/JBIDE-22705>
>> https://issues.jboss.org/browse/JBIDE-22705 and
>> https://issues.jboss.org/browse/JBIDE-22706
>> I don't remember creating those issues through the web interface, perhaps
>> someone else did it?
>>
>>
>> Maybe someone from QE?
>>
>> Anyway, I was just wondering if there is some way to have the user steps
>> used to reproduce those exceptions from AERI, otherwise I'll just close
>> them as Cannot Reproduce.
>>
>>
>> If these exceptions do not reported often and you don't see what could be
>> the reason for that then I'm not sure there is something we can do with
>> such reports.
>> But if they are reported often by different users then it worth a deep
>> investigation.
>> Marcel, is there any way to interact with reporters after submitting a
>> report?
>>
>> Thanks.
>>
>>
>>
>> Thank you
>>
>> *George Gastaldi*
>>
>> https://onename.com/gastaldi
>>
>> On Mon, Jul 11, 2016 at 1:44 PM, Alexey Kazakov <alkazako at redhat.com>
>> wrote:
>>
>>> George, AFAIK these JIRAs are not created automatically. If you see a
>>> JIRA created by AERI then someone created it via AERI web interface when
>>> reviewing reports.
>>> And as Len said, every component lead is supposed to review the reports
>>> weekly and create JIRAs/close reports for his/her components.
>>> If you someone doesn't have access to AERI then please let us know.
>>>
>>> On 07/11/2016 12:34 PM, Leonard Dimaggio wrote:
>>>
>>> I thought that we had agreed that Dev + QE component leads would review
>>> the (weekly) reports from AERI and then log JIRAs....selectively.
>>>
>>> -- Len
>>>
>>> On Mon, Jul 11, 2016 at 12:22 PM, George Gastaldi <
>>> <ggastald at redhat.com>ggastald at redhat.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I noticed that the AERI bot opens some JIRA according to the issues
>>>> reported by the users. I am having a hard time trying to reproduce these
>>>> errors, mostly because I don't know what the user did to make that happen.
>>>> How can I have access to the steps performed by the user when the error
>>>> occurred?
>>>>
>>>> I think that opening an issue with a Stacktrace is not that useful if
>>>> you don't know how to reproduce that error locally.
>>>>
>>>> Best Regards,
>>>>
>>>> *George Gastaldi*
>>>>
>>>> <https://onename.com/gastaldi>https://onename.com/gastaldi
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Len DiMaggio ( <ldimaggi at redhat.com>ldimaggi at redhat.com)
>>> JBoss by Red Hat
>>> 314 Littleton Road
>>> Westford, MA 01886  USA
>>> tel:  978.392.3179
>>> cell: 781.472.9912
>>> http://www.redhat.com
>>> http://community.jboss.org/people/ldimaggio
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing listjbosstools-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>>>
>>
>>
>
>
> --
> Len DiMaggio (ldimaggi at redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Aurelien Pupier
Senior Software Engineer in JBoss Fuse Tooling team
@apupier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/ea9b8de0/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 250183 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/ea9b8de0/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 251810 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/ea9b8de0/attachment-0003.png 

From marcel.bruch at codetrails.com  Mon Jul 11 15:00:45 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Mon, 11 Jul 2016 21:00:45 +0200
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
	issues?
In-Reply-To: <5783CCE3.2030805@redhat.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
Message-ID: <30A6026A-1DE9-4156-B4E2-DD8DD4186493@codetrails.com>


> On 11 Jul 2016, at 18:44, Alexey Kazakov <alkazako at redhat.com> wrote:
> 
> George, AFAIK these JIRAs are not created automatically.

Correct. 
Although the automated error reporter *can* automatically create JIRA tickets (e.g. when certain thresholds like number of reporters > 10) are reached, there is no such rule active for JBoss tools yet.

At Eclipse we have a login per user (not a one-for-all login as for JBoss tools). There we append a footer ?This bug report was created on behalf of <username>?. 

For JBoss we?d need to set up a comparable authentication mechanism. Preferably one that works well for all committers and does not require creating yet another account. Is there such system which we could use to authenticate your committers against?

Marcel

From ggastald at redhat.com  Mon Jul 11 15:02:39 2016
From: ggastald at redhat.com (George Gastaldi)
Date: Mon, 11 Jul 2016 16:02:39 -0300
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
	issues?
In-Reply-To: <30A6026A-1DE9-4156-B4E2-DD8DD4186493@codetrails.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
	<30A6026A-1DE9-4156-B4E2-DD8DD4186493@codetrails.com>
Message-ID: <CAMmsnJgW2K3siU39Wjgv-5nXEOwB=0fLngwHNwQ5UujEKoeeeA@mail.gmail.com>

Would it be possible to use our SAML system: https://saml.redhat.com/idp/ ?

That would be cool.


*George Gastaldi*

https://onename.com/gastaldi

On Mon, Jul 11, 2016 at 4:00 PM, Marcel Bruch <marcel.bruch at codetrails.com>
wrote:

>
> > On 11 Jul 2016, at 18:44, Alexey Kazakov <alkazako at redhat.com> wrote:
> >
> > George, AFAIK these JIRAs are not created automatically.
>
> Correct.
> Although the automated error reporter *can* automatically create JIRA
> tickets (e.g. when certain thresholds like number of reporters > 10) are
> reached, there is no such rule active for JBoss tools yet.
>
> At Eclipse we have a login per user (not a one-for-all login as for JBoss
> tools). There we append a footer ?This bug report was created on behalf of
> <username>?.
>
> For JBoss we?d need to set up a comparable authentication mechanism.
> Preferably one that works well for all committers and does not require
> creating yet another account. Is there such system which we could use to
> authenticate your committers against?
>
> Marcel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/6052516a/attachment.html 

From ldimaggi at redhat.com  Mon Jul 11 15:04:29 2016
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Mon, 11 Jul 2016 15:04:29 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <577FF44F.50709@redhat.com>
References: <577FF44F.50709@redhat.com>
Message-ID: <CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>

Hi Alexey,

It wasn't possible to do this due to all the holidays and PTO last week,
but for future sprints (starting with 117), will we have a pre-release
review? It's not really a go/no-go meeting as the default is "go" - but it
would be good to have a sprint wrap-up review. Maybe we can combine this
with the retrospective?

Thanks!,
Len









On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

> Hi all,
>
> Just a reminder that our initial plan was to release milestones of JBoss
> Tools after every sprint and work on automation of this process so it
> doesn't require a lot of efforts any manual work.
> But because of holidays in Canada, USA and Czech Republic plus busy Red
> Hat Summit week before that we skipped public release of JBoss Tools
> 4.4.1.AM1.
> Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with
> codefreeze on July 21 (Thursday). This will be our first public
> milestone release for JBT 4.4.1.
> The release schedule is available here -
>
> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>
> Thank you.
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Len DiMaggio (ldimaggi at redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886  USA
tel:  978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/292b8696/attachment.html 

From marcel.bruch at codetrails.com  Mon Jul 11 15:06:45 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Mon, 11 Jul 2016 21:06:45 +0200
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
	issues?
In-Reply-To: <CAMmsnJhXLZBkK3gn32Y-7x1Nr6-L4rz4evDP-Ted_CU7p8WQ6A@mail.gmail.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
	<CAMmsnJigEmUU55hioSrHNHfH8nC-_h82+EAsgPxnjR+Be4HeOw@mail.gmail.com>
	<5783D090.2040802@redhat.com>
	<B5DD59A8-4B8D-4E18-94A1-A4BDDA0BA934@codetrails.com>
	<CAMmsnJhXLZBkK3gn32Y-7x1Nr6-L4rz4evDP-Ted_CU7p8WQ6A@mail.gmail.com>
Message-ID: <17BAA288-B124-41C6-98A8-484625B97728@codetrails.com>


> On 11 Jul 2016, at 20:53, George Gastaldi <ggastald at redhat.com> wrote:
> 
> That looks awesome. Is there any way to get in touch with the original reporter?
> 

Just click on the link. This will open your email client and the reporter?s email addresses will be in the to-line of your email.

> How would the needinfo flags help in this case?
> 
> 

First, setting the resolution to Cannot Reproduce will create the following message in the popup notification *after it was send*:

You hit a problem were the stack trace and log message alone do not provide enough context to triage this issue.
<#if resolutionNotes>
${problem.resolutionNotes}
<#elseif bug>
A reviewer requested further information before processing this problem. Please visit visit {link,rel=bug;title=${problem.bug.key}} and see whether you can add missing details.
<#elseif needinfo>
A reviewer requested further information before processing this request. Please visit {link,rel=submission;title=your submission} and see whether you can add missing details.
</#if>


With needinfo flag set, the message will be presented in the error notification *before* the user sends the report. Then the user knows immediately that his assistance is needed and hopefully takes more time to create a helpful error report / comment.

Marcel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/77f63752/attachment.html 

From marcel.bruch at codetrails.com  Mon Jul 11 15:07:42 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Mon, 11 Jul 2016 21:07:42 +0200
Subject: [jbosstools-dev] Zero AERI repports for BrowserSim / CordovaSim
	/ VPE components
In-Reply-To: <CACrcdncrP0ps=8bmy66c=NuTq3B7uCEf_PXEX4YOjqo=k-_NYQ@mail.gmail.com>
References: <CACrcdncrP0ps=8bmy66c=NuTq3B7uCEf_PXEX4YOjqo=k-_NYQ@mail.gmail.com>
Message-ID: <CBD0EBCF-C0F1-4765-B808-53EE3CB88188@codetrails.com>

Please send me the list of package prefixes. I?ll then check the configuration. Thanks, Marcel

> On 11 Jul 2016, at 20:06, Ilya Buziuk <ibuziuk at redhat.com> wrote:
> 
> Hi, Marcel 
> I was not able to find any AERI reports for BrowserSim / CordovaSim / VPE components which is quite suspicious taking in consideration the size of the code base. Could you please check if AERI is setup correctly for those components ?
> Thanks
> 

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/0c633959/attachment-0001.html 

From alkazako at redhat.com  Mon Jul 11 15:10:06 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 11 Jul 2016 15:10:06 -0400
Subject: [jbosstools-dev] Steps to reproduce Automated Error Report bot
 issues?
In-Reply-To: <CAMmsnJgW2K3siU39Wjgv-5nXEOwB=0fLngwHNwQ5UujEKoeeeA@mail.gmail.com>
References: <CAMmsnJjU-UdK_MHzmzzokzGe36jG5M7iS13aHWickb_u+GdPQQ@mail.gmail.com>
	<CA+qK+9=ETHg3==Y1KJjJjOc-1+_JqhkfwSaSdaKLMiV=6VNwwA@mail.gmail.com>
	<5783CCE3.2030805@redhat.com>
	<30A6026A-1DE9-4156-B4E2-DD8DD4186493@codetrails.com>
	<CAMmsnJgW2K3siU39Wjgv-5nXEOwB=0fLngwHNwQ5UujEKoeeeA@mail.gmail.com>
Message-ID: <5783EF0E.9040900@redhat.com>

Or JIRA (issues.jboss.org)?
If it's possible to limit access for certain JIRA accounts.
Or github (jboss tools team)?

On 07/11/2016 03:02 PM, George Gastaldi wrote:
> Would it be possible to use our SAML system: 
> https://saml.redhat.com/idp/ ?
>
> That would be cool.
>
>
> *George Gastaldi*
>
> https://onename.com/gastaldi
>
> On Mon, Jul 11, 2016 at 4:00 PM, Marcel Bruch 
> <marcel.bruch at codetrails.com <mailto:marcel.bruch at codetrails.com>> wrote:
>
>
>     > On 11 Jul 2016, at 18:44, Alexey Kazakov <alkazako at redhat.com
>     <mailto:alkazako at redhat.com>> wrote:
>     >
>     > George, AFAIK these JIRAs are not created automatically.
>
>     Correct.
>     Although the automated error reporter *can* automatically create
>     JIRA tickets (e.g. when certain thresholds like number of
>     reporters > 10) are reached, there is no such rule active for
>     JBoss tools yet.
>
>     At Eclipse we have a login per user (not a one-for-all login as
>     for JBoss tools). There we append a footer ?This bug report was
>     created on behalf of <username>?.
>
>     For JBoss we?d need to set up a comparable authentication
>     mechanism. Preferably one that works well for all committers and
>     does not require creating yet another account. Is there such
>     system which we could use to authenticate your committers against?
>
>     Marcel
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/cf9be166/attachment.html 

From alkazako at redhat.com  Mon Jul 11 15:15:52 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 11 Jul 2016 15:15:52 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>
References: <577FF44F.50709@redhat.com>
	<CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>
Message-ID: <5783F068.9030608@redhat.com>

Yes we can try to combine it with the retrospective. But we will need 
someone from QE to present on the retrospective then ;)

On 07/11/2016 03:04 PM, Leonard Dimaggio wrote:
> Hi Alexey,
>
> It wasn't possible to do this due to all the holidays and PTO last 
> week, but for future sprints (starting with 117), will we have a 
> pre-release review? It's not really a go/no-go meeting as the default 
> is "go" - but it would be good to have a sprint wrap-up review. Maybe 
> we can combine this with the retrospective?
>
> Thanks!,
> Len
>
>
>
>
>
>
>
>
>
> On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov <alkazako at redhat.com 
> <mailto:alkazako at redhat.com>> wrote:
>
>     Hi all,
>
>     Just a reminder that our initial plan was to release milestones of
>     JBoss
>     Tools after every sprint and work on automation of this process so it
>     doesn't require a lot of efforts any manual work.
>     But because of holidays in Canada, USA and Czech Republic plus
>     busy Red
>     Hat Summit week before that we skipped public release of JBoss Tools
>     4.4.1.AM1.
>     Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with
>     codefreeze on July 21 (Thursday). This will be our first public
>     milestone release for JBT 4.4.1.
>     The release schedule is available here -
>     https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>
>     Thank you.
>     _______________________________________________
>     jbosstools-dev mailing list
>     jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
>
> -- 
> Len DiMaggio (ldimaggi at redhat.com <mailto:ldimaggi at redhat.com>)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/026f3d15/attachment.html 

From ldimaggi at redhat.com  Mon Jul 11 15:24:45 2016
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Mon, 11 Jul 2016 15:24:45 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <5783F068.9030608@redhat.com>
References: <577FF44F.50709@redhat.com>
	<CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>
	<5783F068.9030608@redhat.com>
Message-ID: <CA+qK+9ne_ttkYH0HA_w1yNsvcHHwZ3EUf8hM8NM7tWzc+Wq13Q@mail.gmail.com>

I volunteer! (Just not when I am on PTO.  ;-)

-- Len

On Mon, Jul 11, 2016 at 3:15 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

> Yes we can try to combine it with the retrospective. But we will need
> someone from QE to present on the retrospective then ;)
>
>
> On 07/11/2016 03:04 PM, Leonard Dimaggio wrote:
>
> Hi Alexey,
>
> It wasn't possible to do this due to all the holidays and PTO last week,
> but for future sprints (starting with 117), will we have a pre-release
> review? It's not really a go/no-go meeting as the default is "go" - but it
> would be good to have a sprint wrap-up review. Maybe we can combine this
> with the retrospective?
>
> Thanks!,
> Len
>
>
>
>
>
>
>
>
>
> On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov <alkazako at redhat.com>
> wrote:
>
>> Hi all,
>>
>> Just a reminder that our initial plan was to release milestones of JBoss
>> Tools after every sprint and work on automation of this process so it
>> doesn't require a lot of efforts any manual work.
>> But because of holidays in Canada, USA and Czech Republic plus busy Red
>> Hat Summit week before that we skipped public release of JBoss Tools
>> 4.4.1.AM1.
>> Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with
>> codefreeze on July 21 (Thursday). This will be our first public
>> milestone release for JBT 4.4.1.
>> The release schedule is available here -
>>
>> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>>
>> Thank you.
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
>
> --
> Len DiMaggio (ldimaggi at redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>
>
>


-- 
Len DiMaggio (ldimaggi at redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886  USA
tel:  978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/c8e28f5f/attachment.html 

From alkazako at redhat.com  Mon Jul 11 15:27:00 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 11 Jul 2016 15:27:00 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <CA+qK+9ne_ttkYH0HA_w1yNsvcHHwZ3EUf8hM8NM7tWzc+Wq13Q@mail.gmail.com>
References: <577FF44F.50709@redhat.com>
	<CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>
	<5783F068.9030608@redhat.com>
	<CA+qK+9ne_ttkYH0HA_w1yNsvcHHwZ3EUf8hM8NM7tWzc+Wq13Q@mail.gmail.com>
Message-ID: <5783F304.9090809@redhat.com>

I added your to the google event.

On 07/11/2016 03:24 PM, Leonard Dimaggio wrote:
> I volunteer! (Just not when I am on PTO.  ;-)
>
> -- Len
>
> On Mon, Jul 11, 2016 at 3:15 PM, Alexey Kazakov <alkazako at redhat.com 
> <mailto:alkazako at redhat.com>> wrote:
>
>     Yes we can try to combine it with the retrospective. But we will
>     need someone from QE to present on the retrospective then ;)
>
>
>     On 07/11/2016 03:04 PM, Leonard Dimaggio wrote:
>>     Hi Alexey,
>>
>>     It wasn't possible to do this due to all the holidays and PTO
>>     last week, but for future sprints (starting with 117), will we
>>     have a pre-release review? It's not really a go/no-go meeting as
>>     the default is "go" - but it would be good to have a sprint
>>     wrap-up review. Maybe we can combine this with the retrospective?
>>
>>     Thanks!,
>>     Len
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>     On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov
>>     <alkazako at redhat.com <mailto:alkazako at redhat.com>> wrote:
>>
>>         Hi all,
>>
>>         Just a reminder that our initial plan was to release
>>         milestones of JBoss
>>         Tools after every sprint and work on automation of this
>>         process so it
>>         doesn't require a lot of efforts any manual work.
>>         But because of holidays in Canada, USA and Czech Republic
>>         plus busy Red
>>         Hat Summit week before that we skipped public release of
>>         JBoss Tools
>>         4.4.1.AM1.
>>         Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with
>>         codefreeze on July 21 (Thursday). This will be our first public
>>         milestone release for JBT 4.4.1.
>>         The release schedule is available here -
>>         https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>>
>>         Thank you.
>>         _______________________________________________
>>         jbosstools-dev mailing list
>>         jbosstools-dev at lists.jboss.org
>>         <mailto:jbosstools-dev at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>>
>>     -- 
>>     Len DiMaggio (ldimaggi at redhat.com <mailto:ldimaggi at redhat.com>)
>>     JBoss by Red Hat
>>     314 Littleton Road
>>     Westford, MA 01886  USA
>>     tel: 978.392.3179 <tel:978.392.3179>
>>     cell: 781.472.9912 <tel:781.472.9912>
>>     http://www.redhat.com
>>     http://community.jboss.org/people/ldimaggio
>>
>>
>
>
>
>
> -- 
> Len DiMaggio (ldimaggi at redhat.com <mailto:ldimaggi at redhat.com>)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/968fb2d6/attachment-0001.html 

From ggastald at redhat.com  Mon Jul 11 15:29:02 2016
From: ggastald at redhat.com (George Gastaldi)
Date: Mon, 11 Jul 2016 16:29:02 -0300
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <5783F304.9090809@redhat.com>
References: <577FF44F.50709@redhat.com>
	<CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>
	<5783F068.9030608@redhat.com>
	<CA+qK+9ne_ttkYH0HA_w1yNsvcHHwZ3EUf8hM8NM7tWzc+Wq13Q@mail.gmail.com>
	<5783F304.9090809@redhat.com>
Message-ID: <CAMmsnJiYz=SsH3dB3S1HFnxsZknokNRmfYG0-a5-BTfsFPH9UQ@mail.gmail.com>

Are component leads also required to attend the event? I don't see it in my
calendar.

*George Gastaldi*

https://onename.com/gastaldi

On Mon, Jul 11, 2016 at 4:27 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

> I added your to the google event.
>
> On 07/11/2016 03:24 PM, Leonard Dimaggio wrote:
>
> I volunteer! (Just not when I am on PTO.  ;-)
>
> -- Len
>
> On Mon, Jul 11, 2016 at 3:15 PM, Alexey Kazakov <alkazako at redhat.com>
> wrote:
>
>> Yes we can try to combine it with the retrospective. But we will need
>> someone from QE to present on the retrospective then ;)
>>
>>
>> On 07/11/2016 03:04 PM, Leonard Dimaggio wrote:
>>
>> Hi Alexey,
>>
>> It wasn't possible to do this due to all the holidays and PTO last week,
>> but for future sprints (starting with 117), will we have a pre-release
>> review? It's not really a go/no-go meeting as the default is "go" - but it
>> would be good to have a sprint wrap-up review. Maybe we can combine this
>> with the retrospective?
>>
>> Thanks!,
>> Len
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov < <alkazako at redhat.com>
>> alkazako at redhat.com> wrote:
>>
>>> Hi all,
>>>
>>> Just a reminder that our initial plan was to release milestones of JBoss
>>> Tools after every sprint and work on automation of this process so it
>>> doesn't require a lot of efforts any manual work.
>>> But because of holidays in Canada, USA and Czech Republic plus busy Red
>>> Hat Summit week before that we skipped public release of JBoss Tools
>>> 4.4.1.AM1.
>>> Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with
>>> codefreeze on July 21 (Thursday). This will be our first public
>>> milestone release for JBT 4.4.1.
>>> The release schedule is available here -
>>>
>>> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>>>
>>> Thank you.
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>>
>>
>> --
>> Len DiMaggio ( <ldimaggi at redhat.com>ldimaggi at redhat.com)
>> JBoss by Red Hat
>> 314 Littleton Road
>> Westford, MA 01886  USA
>> tel:  978.392.3179
>> cell: 781.472.9912
>> http://www.redhat.com
>> http://community.jboss.org/people/ldimaggio
>>
>>
>>
>>
>
>
> --
> Len DiMaggio (ldimaggi at redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/755d031a/attachment.html 

From mistria at redhat.com  Mon Jul 11 16:05:33 2016
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 11 Jul 2016 22:05:33 +0200
Subject: [jbosstools-dev] Firefox for Windows 64 bits
Message-ID: <da055f19-b9cf-e5c1-b781-dd059d212cb2@redhat.com>

Hi all,

I was following some mozilla bugs related to Windows 64 bits support. 
IIRC, those were interesting for JBoss Tools VPE or BrowserSim at some 
point, however, I cannot remember the details. Anyway, some of those 
bugs were marked as fixed recently, such as 
https://bugzilla.mozilla.org/show_bug.cgi?id=482143#c15 .

Not sure whether this is any helpful for us, but I thought it might be 
worth sharing.

Cheers,

-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/7a2a5fdb/attachment.html 

From ibuziuk at redhat.com  Mon Jul 11 16:47:05 2016
From: ibuziuk at redhat.com (Ilya Buziuk)
Date: Mon, 11 Jul 2016 22:47:05 +0200
Subject: [jbosstools-dev] Zero AERI repports for BrowserSim / CordovaSim
	/ VPE components
In-Reply-To: <AC9FFFF6-BE31-4F67-A577-3EFC4F44322C@codetrails.com>
References: <CACrcdncrP0ps=8bmy66c=NuTq3B7uCEf_PXEX4YOjqo=k-_NYQ@mail.gmail.com>
	<CBD0EBCF-C0F1-4765-B808-53EE3CB88188@codetrails.com>
	<AC9FFFF6-BE31-4F67-A577-3EFC4F44322C@codetrails.com>
Message-ID: <CACrcdncDKhDLnaK24zhL3dogv12F2UX-P4__9GRwE8eniVSrVg@mail.gmail.com>

It is three different projects. The prefixes are:
- org.jboss.tools.vpe [1]
- org.jboss.tools.browsersim [2]
- org.jboss.tools.cordovasim  [3] (CordovaSim is a part
of jbosstools-aerogear repo)

[1] https://github.com/jbosstools/jbosstools-vpe
[2] https://github.com/jbosstools/jbosstools-browsersim
[3] https://github.com/jbosstools/jbosstools-aerogear/tree/master/cordovasim



On Mon, Jul 11, 2016 at 9:54 PM, Marcel Bruch <marcel.bruch at codetrails.com>
wrote:

> I just looked at the projects list and could not find anything that seems
> related to BrowserSim, CordovaSim or VPE. It seems that no-one requested to
> set up error reporting for those projects yet.
>
> Is it ?one project? or do we have to split them into three?
>
> What are the package prefixes assigned to above projects? We use them for
> assigned stack traces to your projects.
>
> Thanks,
> Marcel
>
>
> On 11 Jul 2016, at 21:07, Marcel Bruch <marcel.bruch at codetrails.com>
> wrote:
>
> Please send me the list of package prefixes. I?ll then check the
> configuration. Thanks, Marcel
>
> On 11 Jul 2016, at 20:06, Ilya Buziuk <ibuziuk at redhat.com> wrote:
>
> Hi, Marcel
> I was not able to find any AERI reports for BrowserSim / CordovaSim / VPE
> components which is quite suspicious taking in consideration the size of
> the code base. Could you please check if AERI is setup correctly for those
> components ?
> Thanks
>
>
> --
> Codetrails GmbH
> The knowledge transfer company
>
> Robert-Bosch-Str. 7, 64293 Darmstadt
> Phone: +49-6151-276-7092
> Mobile: +49-179-131-7721
> http://www.codetrails.com/
>
> Managing Director: Dr. Marcel Bruch
> Handelsregister: Darmstadt HRB 91940
>
>
> --
> Codetrails GmbH
> The knowledge transfer company
>
> Robert-Bosch-Str. 7, 64293 Darmstadt
> Phone: +49-6151-276-7092
> Mobile: +49-179-131-7721
> http://www.codetrails.com/
>
> Managing Director: Dr. Marcel Bruch
> Handelsregister: Darmstadt HRB 91940
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/4ebbd6dc/attachment.html 

From alkazako at redhat.com  Mon Jul 11 17:32:11 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Mon, 11 Jul 2016 17:32:11 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <CAMmsnJiYz=SsH3dB3S1HFnxsZknokNRmfYG0-a5-BTfsFPH9UQ@mail.gmail.com>
References: <577FF44F.50709@redhat.com>
	<CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>
	<5783F068.9030608@redhat.com>
	<CA+qK+9ne_ttkYH0HA_w1yNsvcHHwZ3EUf8hM8NM7tWzc+Wq13Q@mail.gmail.com>
	<5783F304.9090809@redhat.com>
	<CAMmsnJiYz=SsH3dB3S1HFnxsZknokNRmfYG0-a5-BTfsFPH9UQ@mail.gmail.com>
Message-ID: <5784105B.7070807@redhat.com>

It's not only for JBoss Tools but for entire group 2 (code) of the 
devtools team. It includes Eclipse DTS and others.
This event is in devtools calendar and publicly available but I can add 
you to the event if you want.

Thanks.

On 07/11/2016 03:29 PM, George Gastaldi wrote:
> Are component leads also required to attend the event? I don't see it 
> in my calendar.
>
> *George Gastaldi*
>
> https://onename.com/gastaldi
>
> On Mon, Jul 11, 2016 at 4:27 PM, Alexey Kazakov <alkazako at redhat.com 
> <mailto:alkazako at redhat.com>> wrote:
>
>     I added your to the google event.
>
>     On 07/11/2016 03:24 PM, Leonard Dimaggio wrote:
>>     I volunteer! (Just not when I am on PTO.  ;-)
>>
>>     -- Len
>>
>>     On Mon, Jul 11, 2016 at 3:15 PM, Alexey Kazakov
>>     <alkazako at redhat.com <mailto:alkazako at redhat.com>> wrote:
>>
>>         Yes we can try to combine it with the retrospective. But we
>>         will need someone from QE to present on the retrospective
>>         then ;)
>>
>>
>>         On 07/11/2016 03:04 PM, Leonard Dimaggio wrote:
>>>         Hi Alexey,
>>>
>>>         It wasn't possible to do this due to all the holidays and
>>>         PTO last week, but for future sprints (starting with 117),
>>>         will we have a pre-release review? It's not really a
>>>         go/no-go meeting as the default is "go" - but it would be
>>>         good to have a sprint wrap-up review. Maybe we can combine
>>>         this with the retrospective?
>>>
>>>         Thanks!,
>>>         Len
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>         On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov
>>>         <alkazako at redhat.com <mailto:alkazako at redhat.com>> wrote:
>>>
>>>             Hi all,
>>>
>>>             Just a reminder that our initial plan was to release
>>>             milestones of JBoss
>>>             Tools after every sprint and work on automation of this
>>>             process so it
>>>             doesn't require a lot of efforts any manual work.
>>>             But because of holidays in Canada, USA and Czech
>>>             Republic plus busy Red
>>>             Hat Summit week before that we skipped public release of
>>>             JBoss Tools
>>>             4.4.1.AM1.
>>>             Our next (4.4.1.AM2) release will be on July 26
>>>             (Tuesday) with
>>>             codefreeze on July 21 (Thursday). This will be our first
>>>             public
>>>             milestone release for JBT 4.4.1.
>>>             The release schedule is available here -
>>>             https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>>>
>>>             Thank you.
>>>             _______________________________________________
>>>             jbosstools-dev mailing list
>>>             jbosstools-dev at lists.jboss.org
>>>             <mailto:jbosstools-dev at lists.jboss.org>
>>>             https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>>
>>>
>>>
>>>         -- 
>>>         Len DiMaggio (ldimaggi at redhat.com <mailto:ldimaggi at redhat.com>)
>>>         JBoss by Red Hat
>>>         314 Littleton Road
>>>         Westford, MA 01886  USA
>>>         tel: 978.392.3179 <tel:978.392.3179>
>>>         cell: 781.472.9912 <tel:781.472.9912>
>>>         http://www.redhat.com
>>>         http://community.jboss.org/people/ldimaggio
>>>
>>>
>>
>>
>>
>>
>>     -- 
>>     Len DiMaggio (ldimaggi at redhat.com <mailto:ldimaggi at redhat.com>)
>>     JBoss by Red Hat
>>     314 Littleton Road
>>     Westford, MA 01886  USA
>>     tel: 978.392.3179 <tel:978.392.3179>
>>     cell: 781.472.9912 <tel:781.472.9912>
>>     http://www.redhat.com
>>     http://community.jboss.org/people/ldimaggio
>>
>>
>
>
>     _______________________________________________
>     jbosstools-dev mailing list
>     jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160711/a8068739/attachment-0001.html 

From marcel.bruch at codetrails.com  Tue Jul 12 04:51:07 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Tue, 12 Jul 2016 10:51:07 +0200
Subject: [jbosstools-dev] Zero AERI repports for BrowserSim / CordovaSim
	/ VPE components
In-Reply-To: <CACrcdncDKhDLnaK24zhL3dogv12F2UX-P4__9GRwE8eniVSrVg@mail.gmail.com>
References: <CACrcdncrP0ps=8bmy66c=NuTq3B7uCEf_PXEX4YOjqo=k-_NYQ@mail.gmail.com>
	<CBD0EBCF-C0F1-4765-B808-53EE3CB88188@codetrails.com>
	<AC9FFFF6-BE31-4F67-A577-3EFC4F44322C@codetrails.com>
	<CACrcdncDKhDLnaK24zhL3dogv12F2UX-P4__9GRwE8eniVSrVg@mail.gmail.com>
Message-ID: <F64CEF92-E544-4EE4-8C0A-15D1BA9559C8@codetrails.com>

Ilya,

I created these projects and re-run the automated project assignments. VPE now got 37 problems to review [1,2]. Browsersim and Aerogear have few items (<3) only.

 Does that make sense - or would you expect more for Browsersim and Aerogear? If so, I?ve to take a closer look.

Thanks,
Marcel

[1] https://redhat.ctrlflow.com/reviewers/#!/projects/5784ad7ae4b07f3dc268e328/dashboard <https://redhat.ctrlflow.com/reviewers/#!/projects/5784ad7ae4b07f3dc268e328/dashboard>
[2] https://redhat.ctrlflow.com/reviewers/#!/problems/?c:!((t:project,op:contains_any_of,val:!(vpe))),sort:!((prop:modifiedOn,dir:DESCENDING)) <https://redhat.ctrlflow.com/reviewers/#!/problems/?c:!((t:project,op:contains_any_of,val:!(vpe))),sort:!((prop:modifiedOn,dir:DESCENDING))>



> On 11 Jul 2016, at 22:47, Ilya Buziuk <ibuziuk at redhat.com> wrote:
> 
> It is three different projects. The prefixes are: 
> - org.jboss.tools.vpe [1]
> - org.jboss.tools.browsersim [2]
> - org.jboss.tools.cordovasim  [3] (CordovaSim is a part of jbosstools-aerogear repo)
> 
> [1] https://github.com/jbosstools/jbosstools-vpe <https://github.com/jbosstools/jbosstools-vpe>
> [2] https://github.com/jbosstools/jbosstools-browsersim <https://github.com/jbosstools/jbosstools-browsersim>
> [3] https://github.com/jbosstools/jbosstools-aerogear/tree/master/cordovasim <https://github.com/jbosstools/jbosstools-aerogear/tree/master/cordovasim>
> 
> 
> 
> On Mon, Jul 11, 2016 at 9:54 PM, Marcel Bruch <marcel.bruch at codetrails.com <mailto:marcel.bruch at codetrails.com>> wrote:
> I just looked at the projects list and could not find anything that seems related to BrowserSim, CordovaSim or VPE. It seems that no-one requested to set up error reporting for those projects yet.
> 
> Is it ?one project? or do we have to split them into three?
> 
> What are the package prefixes assigned to above projects? We use them for assigned stack traces to your projects.
> 
> Thanks,
> Marcel
> 
> 
>> On 11 Jul 2016, at 21:07, Marcel Bruch <marcel.bruch at codetrails.com <mailto:marcel.bruch at codetrails.com>> wrote:
>> 
>> Please send me the list of package prefixes. I?ll then check the configuration. Thanks, Marcel
>> 
>>> On 11 Jul 2016, at 20:06, Ilya Buziuk <ibuziuk at redhat.com <mailto:ibuziuk at redhat.com>> wrote:
>>> 
>>> Hi, Marcel 
>>> I was not able to find any AERI reports for BrowserSim / CordovaSim / VPE components which is quite suspicious taking in consideration the size of the code base. Could you please check if AERI is setup correctly for those components ?
>>> Thanks
>>> 
>> 
>> -- 
>> Codetrails GmbH
>> The knowledge transfer company
>> 
>> Robert-Bosch-Str. 7, 64293 Darmstadt
>> Phone: +49-6151-276-7092 <tel:%2B49-6151-276-7092>
>> Mobile: +49-179-131-7721 <tel:%2B49-179-131-7721>
>> http://www.codetrails.com/ <http://www.codetrails.com/>
>> 
>> Managing Director: Dr. Marcel Bruch
>> Handelsregister: Darmstadt HRB 91940
>> 
> 
> -- 
> Codetrails GmbH
> The knowledge transfer company
> 
> Robert-Bosch-Str. 7, 64293 Darmstadt
> Phone: +49-6151-276-7092 <tel:%2B49-6151-276-7092>
> Mobile: +49-179-131-7721 <tel:%2B49-179-131-7721>
> http://www.codetrails.com/ <http://www.codetrails.com/>
> 
> Managing Director: Dr. Marcel Bruch
> Handelsregister: Darmstadt HRB 91940
> 
> 

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160712/3ef79bad/attachment.html 

From ibuziuk at redhat.com  Tue Jul 12 06:16:15 2016
From: ibuziuk at redhat.com (Ilya Buziuk)
Date: Tue, 12 Jul 2016 12:16:15 +0200
Subject: [jbosstools-dev] Zero AERI repports for BrowserSim / CordovaSim
	/ VPE components
In-Reply-To: <F64CEF92-E544-4EE4-8C0A-15D1BA9559C8@codetrails.com>
References: <CACrcdncrP0ps=8bmy66c=NuTq3B7uCEf_PXEX4YOjqo=k-_NYQ@mail.gmail.com>
	<CBD0EBCF-C0F1-4765-B808-53EE3CB88188@codetrails.com>
	<AC9FFFF6-BE31-4F67-A577-3EFC4F44322C@codetrails.com>
	<CACrcdncDKhDLnaK24zhL3dogv12F2UX-P4__9GRwE8eniVSrVg@mail.gmail.com>
	<F64CEF92-E544-4EE4-8C0A-15D1BA9559C8@codetrails.com>
Message-ID: <CACrcdndqt8tA3oOQkTnv81-pLq4UpmC5oS2nqGmBu+Lmt2SW5Q@mail.gmail.com>

Thanks, Marcel
The item number per project looks relevant for me. Just one notice to be
sure that we are on the same page - even though CordovaSim is located in
Aerogear repo it is a separate project with 'org.jboss.tools.cordovasim'
prefix and should be tracked separately. Also, I am not able to login to
[1] & [2] (using kerberos credentials) Should I request access somehow ?

On Tue, Jul 12, 2016 at 10:51 AM, Marcel Bruch <marcel.bruch at codetrails.com>
wrote:

> Ilya,
>
> I created these projects and re-run the automated project assignments. VPE
> now got 37 problems to review [1,2]. Browsersim and Aerogear have few items
> (<3) only.
>
>  Does that make sense - or would you expect more for Browsersim and
> Aerogear? If so, I?ve to take a closer look.
>
> Thanks,
> Marcel
>
> [1]
> https://redhat.ctrlflow.com/reviewers/#!/projects/5784ad7ae4b07f3dc268e328/dashboard
> [2]
> https://redhat.ctrlflow.com/reviewers/#!/problems/?c:!((t:project,op:contains_any_of,val:!(vpe))),sort:!((prop:modifiedOn,dir:DESCENDING))
>
>
>
> On 11 Jul 2016, at 22:47, Ilya Buziuk <ibuziuk at redhat.com> wrote:
>
> It is three different projects. The prefixes are:
> - org.jboss.tools.vpe [1]
> - org.jboss.tools.browsersim [2]
> - org.jboss.tools.cordovasim  [3] (CordovaSim is a part
> of jbosstools-aerogear repo)
>
> [1] https://github.com/jbosstools/jbosstools-vpe
> [2] https://github.com/jbosstools/jbosstools-browsersim
> [3]
> https://github.com/jbosstools/jbosstools-aerogear/tree/master/cordovasim
>
>
>
> On Mon, Jul 11, 2016 at 9:54 PM, Marcel Bruch <marcel.bruch at codetrails.com
> > wrote:
>
>> I just looked at the projects list and could not find anything that seems
>> related to BrowserSim, CordovaSim or VPE. It seems that no-one requested to
>> set up error reporting for those projects yet.
>>
>> Is it ?one project? or do we have to split them into three?
>>
>> What are the package prefixes assigned to above projects? We use them for
>> assigned stack traces to your projects.
>>
>> Thanks,
>> Marcel
>>
>>
>> On 11 Jul 2016, at 21:07, Marcel Bruch <marcel.bruch at codetrails.com>
>> wrote:
>>
>> Please send me the list of package prefixes. I?ll then check the
>> configuration. Thanks, Marcel
>>
>> On 11 Jul 2016, at 20:06, Ilya Buziuk <ibuziuk at redhat.com> wrote:
>>
>> Hi, Marcel
>> I was not able to find any AERI reports for BrowserSim / CordovaSim / VPE
>> components which is quite suspicious taking in consideration the size of
>> the code base. Could you please check if AERI is setup correctly for those
>> components ?
>> Thanks
>>
>>
>> --
>> Codetrails GmbH
>> The knowledge transfer company
>>
>> Robert-Bosch-Str. 7, 64293 Darmstadt
>> Phone: +49-6151-276-7092
>> Mobile: +49-179-131-7721
>> http://www.codetrails.com/
>>
>> Managing Director: Dr. Marcel Bruch
>> Handelsregister: Darmstadt HRB 91940
>>
>>
>> --
>> Codetrails GmbH
>> The knowledge transfer company
>>
>> Robert-Bosch-Str. 7, 64293 Darmstadt
>> Phone: +49-6151-276-7092
>> Mobile: +49-179-131-7721
>> http://www.codetrails.com/
>>
>> Managing Director: Dr. Marcel Bruch
>> Handelsregister: Darmstadt HRB 91940
>>
>>
>
> --
> Codetrails GmbH
> The knowledge transfer company
>
> Robert-Bosch-Str. 7, 64293 Darmstadt
> Phone: +49-6151-276-7092
> Mobile: +49-179-131-7721
> http://www.codetrails.com/
>
> Managing Director: Dr. Marcel Bruch
> Handelsregister: Darmstadt HRB 91940
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160712/7d1a79c5/attachment-0001.html 

From marcel.bruch at codetrails.com  Tue Jul 12 06:47:21 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Tue, 12 Jul 2016 12:47:21 +0200
Subject: [jbosstools-dev] Zero AERI repports for BrowserSim / CordovaSim
	/ VPE components
In-Reply-To: <CACrcdndqt8tA3oOQkTnv81-pLq4UpmC5oS2nqGmBu+Lmt2SW5Q@mail.gmail.com>
References: <CACrcdncrP0ps=8bmy66c=NuTq3B7uCEf_PXEX4YOjqo=k-_NYQ@mail.gmail.com>
	<CBD0EBCF-C0F1-4765-B808-53EE3CB88188@codetrails.com>
	<AC9FFFF6-BE31-4F67-A577-3EFC4F44322C@codetrails.com>
	<CACrcdncDKhDLnaK24zhL3dogv12F2UX-P4__9GRwE8eniVSrVg@mail.gmail.com>
	<F64CEF92-E544-4EE4-8C0A-15D1BA9559C8@codetrails.com>
	<CACrcdndqt8tA3oOQkTnv81-pLq4UpmC5oS2nqGmBu+Lmt2SW5Q@mail.gmail.com>
Message-ID: <4E9FDC85-4E01-43D0-8056-A1003FB3F9D8@codetrails.com>


> On 12 Jul 2016, at 12:16, Ilya Buziuk <ibuziuk at redhat.com> wrote:
> 
> Thanks, Marcel
> The item number per project looks relevant for me. Just one notice to be sure that we are on the same page - even though CordovaSim is located in Aerogear repo it is a separate project with 'org.jboss.tools.cordovasim' prefix and should be tracked separately.


Ok. I created a separate project ?CordovaSim?. There are now three new projects (in addition Aerogear): BrowserSim, CordovaSim, and VPE. They will show up on the weekly digest email but you can query your project issues via the UI at any time.


> Also, I am not able to login to [1] & [2] (using kerberos credentials) Should I request access somehow ?

It?s not using Kerberos. The credentials for accessing the automated error reporting server UI were passed around internally by Max and/or Alexey. 

Alexey, 
can you help out where Ilya finds them?



FWIW, 
we will start working on Github oAuth at the beginning of next week. I?ll send a note when it?s ready.

Marcel



From alkazako at redhat.com  Tue Jul 12 09:19:52 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Tue, 12 Jul 2016 09:19:52 -0400
Subject: [jbosstools-dev] Zero AERI repports for BrowserSim / CordovaSim
 / VPE components
In-Reply-To: <4E9FDC85-4E01-43D0-8056-A1003FB3F9D8@codetrails.com>
References: <CACrcdncrP0ps=8bmy66c=NuTq3B7uCEf_PXEX4YOjqo=k-_NYQ@mail.gmail.com>
	<CBD0EBCF-C0F1-4765-B808-53EE3CB88188@codetrails.com>
	<AC9FFFF6-BE31-4F67-A577-3EFC4F44322C@codetrails.com>
	<CACrcdncDKhDLnaK24zhL3dogv12F2UX-P4__9GRwE8eniVSrVg@mail.gmail.com>
	<F64CEF92-E544-4EE4-8C0A-15D1BA9559C8@codetrails.com>
	<CACrcdndqt8tA3oOQkTnv81-pLq4UpmC5oS2nqGmBu+Lmt2SW5Q@mail.gmail.com>
	<4E9FDC85-4E01-43D0-8056-A1003FB3F9D8@codetrails.com>
Message-ID: <5784EE78.8020203@redhat.com>



On 07/12/2016 06:47 AM, Marcel Bruch wrote:
>> On 12 Jul 2016, at 12:16, Ilya Buziuk <ibuziuk at redhat.com> wrote:
>>
>> Thanks, Marcel
>> The item number per project looks relevant for me. Just one notice to be sure that we are on the same page - even though CordovaSim is located in Aerogear repo it is a separate project with 'org.jboss.tools.cordovasim' prefix and should be tracked separately.
>
> Ok. I created a separate project ?CordovaSim?. There are now three new projects (in addition Aerogear): BrowserSim, CordovaSim, and VPE. They will show up on the weekly digest email but you can query your project issues via the UI at any time.
>
>
>> Also, I am not able to login to [1] & [2] (using kerberos credentials) Should I request access somehow ?
> It?s not using Kerberos. The credentials for accessing the automated error reporting server UI were passed around internally by Max and/or Alexey.
>
> Alexey,
> can you help out where Ilya finds them?

Sent credentials to Ilya off-list.

>
>
>
> FWIW,
> we will start working on Github oAuth at the beginning of next week. I?ll send a note when it?s ready.
>
> Marcel
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From ibuziuk at redhat.com  Tue Jul 12 09:37:49 2016
From: ibuziuk at redhat.com (Ilya Buziuk)
Date: Tue, 12 Jul 2016 15:37:49 +0200
Subject: [jbosstools-dev] Zero AERI repports for BrowserSim / CordovaSim
 / VPE components
In-Reply-To: <5784EE78.8020203@redhat.com>
References: <CACrcdncrP0ps=8bmy66c=NuTq3B7uCEf_PXEX4YOjqo=k-_NYQ@mail.gmail.com>
	<CBD0EBCF-C0F1-4765-B808-53EE3CB88188@codetrails.com>
	<AC9FFFF6-BE31-4F67-A577-3EFC4F44322C@codetrails.com>
	<CACrcdncDKhDLnaK24zhL3dogv12F2UX-P4__9GRwE8eniVSrVg@mail.gmail.com>
	<F64CEF92-E544-4EE4-8C0A-15D1BA9559C8@codetrails.com>
	<CACrcdndqt8tA3oOQkTnv81-pLq4UpmC5oS2nqGmBu+Lmt2SW5Q@mail.gmail.com>
	<4E9FDC85-4E01-43D0-8056-A1003FB3F9D8@codetrails.com>
	<5784EE78.8020203@redhat.com>
Message-ID: <CACrcdnfM5SEXKY7Frm_=j45oPhEsF5wiWy=_n_7W8veQAn7KSA@mail.gmail.com>

Thanks, guys
Now I have access to AERI

On Tue, Jul 12, 2016 at 3:19 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

>
>
> On 07/12/2016 06:47 AM, Marcel Bruch wrote:
>
>> On 12 Jul 2016, at 12:16, Ilya Buziuk <ibuziuk at redhat.com> wrote:
>>>
>>> Thanks, Marcel
>>> The item number per project looks relevant for me. Just one notice to be
>>> sure that we are on the same page - even though CordovaSim is located in
>>> Aerogear repo it is a separate project with 'org.jboss.tools.cordovasim'
>>> prefix and should be tracked separately.
>>>
>>
>> Ok. I created a separate project ?CordovaSim?. There are now three new
>> projects (in addition Aerogear): BrowserSim, CordovaSim, and VPE. They will
>> show up on the weekly digest email but you can query your project issues
>> via the UI at any time.
>>
>>
>> Also, I am not able to login to [1] & [2] (using kerberos credentials)
>>> Should I request access somehow ?
>>>
>> It?s not using Kerberos. The credentials for accessing the automated
>> error reporting server UI were passed around internally by Max and/or
>> Alexey.
>>
>> Alexey,
>> can you help out where Ilya finds them?
>>
>
> Sent credentials to Ilya off-list.
>
>
>>
>>
>> FWIW,
>> we will start working on Github oAuth at the beginning of next week. I?ll
>> send a note when it?s ready.
>>
>> Marcel
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160712/d8fab800/attachment.html 

From nboldt at redhat.com  Tue Jul 12 10:03:25 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 12 Jul 2016 10:03:25 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <5784105B.7070807@redhat.com>
References: <577FF44F.50709@redhat.com>
	<CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>
	<5783F068.9030608@redhat.com>
	<CA+qK+9ne_ttkYH0HA_w1yNsvcHHwZ3EUf8hM8NM7tWzc+Wq13Q@mail.gmail.com>
	<5783F304.9090809@redhat.com>
	<CAMmsnJiYz=SsH3dB3S1HFnxsZknokNRmfYG0-a5-BTfsFPH9UQ@mail.gmail.com>
	<5784105B.7070807@redhat.com>
Message-ID: <CA+QcL12sWy6xSWjBgv8ezU6ubC48V=9DB=awfDz9onF3FLBPNA@mail.gmail.com>

Forgive the dumb question, but if we do...

* TP freeze on the last Wed of the sprint,
* code freeze on the last Thurs of the sprint,
* stage a build to QE on the last Friday of the sprint...

then would this "go/no-go meeting" happen on the last Monday of the sprint,
so that we can release from staging -> production on the last Tuesday of
the sprint?

And isn't that the purpose of the mojo doc [1] & email [2] you produce
confirming that the build is ready to be released? Do we really need
ANOTHER meeting when a single email w/ link to mojo doc has worked for the
last bunch of releases?

[1] https://mojo.redhat.com/docs/DOC-1064660
[2]
https://post-office.corp.redhat.com/mailman/private/jboss-devstudio-list/2016-January/msg00050.html


Cheers,

Nick

On Mon, Jul 11, 2016 at 5:32 PM, Alexey Kazakov <alkazako at redhat.com> wrote:

> It's not only for JBoss Tools but for entire group 2 (code) of the
> devtools team. It includes Eclipse DTS and others.
> This event is in devtools calendar and publicly available but I can add
> you to the event if you want.
>
> Thanks.
>
>
> On 07/11/2016 03:29 PM, George Gastaldi wrote:
>
> Are component leads also required to attend the event? I don't see it in
> my calendar.
>
> *George Gastaldi*
>
> https://onename.com/gastaldi
>
> On Mon, Jul 11, 2016 at 4:27 PM, Alexey Kazakov <alkazako at redhat.com>
> wrote:
>
>> I added your to the google event.
>>
>> On 07/11/2016 03:24 PM, Leonard Dimaggio wrote:
>>
>> I volunteer! (Just not when I am on PTO.  ;-)
>>
>> -- Len
>>
>> On Mon, Jul 11, 2016 at 3:15 PM, Alexey Kazakov < <alkazako at redhat.com>
>> alkazako at redhat.com> wrote:
>>
>>> Yes we can try to combine it with the retrospective. But we will need
>>> someone from QE to present on the retrospective then ;)
>>>
>>>
>>> On 07/11/2016 03:04 PM, Leonard Dimaggio wrote:
>>>
>>> Hi Alexey,
>>>
>>> It wasn't possible to do this due to all the holidays and PTO last week,
>>> but for future sprints (starting with 117), will we have a pre-release
>>> review? It's not really a go/no-go meeting as the default is "go" - but it
>>> would be good to have a sprint wrap-up review. Maybe we can combine this
>>> with the retrospective?
>>>
>>> Thanks!,
>>> Len
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov < <alkazako at redhat.com>
>>> alkazako at redhat.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Just a reminder that our initial plan was to release milestones of JBoss
>>>> Tools after every sprint and work on automation of this process so it
>>>> doesn't require a lot of efforts any manual work.
>>>> But because of holidays in Canada, USA and Czech Republic plus busy Red
>>>> Hat Summit week before that we skipped public release of JBoss Tools
>>>> 4.4.1.AM1.
>>>> Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with
>>>> codefreeze on July 21 (Thursday). This will be our first public
>>>> milestone release for JBT 4.4.1.
>>>> The release schedule is available here -
>>>>
>>>> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>>>>
>>>> Thank you.
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Len DiMaggio ( <ldimaggi at redhat.com>ldimaggi at redhat.com)
>>> JBoss by Red Hat
>>> 314 Littleton Road
>>> Westford, MA 01886  USA
>>> tel:  978.392.3179
>>> cell: 781.472.9912
>>> http://www.redhat.com
>>> http://community.jboss.org/people/ldimaggio
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Len DiMaggio ( <ldimaggi at redhat.com>ldimaggi at redhat.com)
>> JBoss by Red Hat
>> 314 Littleton Road
>> Westford, MA 01886  USA
>> tel:  978.392.3179
>> cell: 781.472.9912
>> http://www.redhat.com
>> http://community.jboss.org/people/ldimaggio
>>
>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160712/b2b4c5bc/attachment-0001.html 

From ldimaggi at redhat.com  Tue Jul 12 10:22:27 2016
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Tue, 12 Jul 2016 10:22:27 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <CA+QcL12sWy6xSWjBgv8ezU6ubC48V=9DB=awfDz9onF3FLBPNA@mail.gmail.com>
References: <577FF44F.50709@redhat.com>
	<CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>
	<5783F068.9030608@redhat.com>
	<CA+qK+9ne_ttkYH0HA_w1yNsvcHHwZ3EUf8hM8NM7tWzc+Wq13Q@mail.gmail.com>
	<5783F304.9090809@redhat.com>
	<CAMmsnJiYz=SsH3dB3S1HFnxsZknokNRmfYG0-a5-BTfsFPH9UQ@mail.gmail.com>
	<5784105B.7070807@redhat.com>
	<CA+QcL12sWy6xSWjBgv8ezU6ubC48V=9DB=awfDz9onF3FLBPNA@mail.gmail.com>
Message-ID: <CA+qK+9kESSVDVcJK__NmTGD3sOgChbw1-E82MycdTrru4CGCAA@mail.gmail.com>

I'd hope that if there was a need (blocking bug) that would prevent the
release, that we'd see that bug in time for the Thursday 5x5 meeting (or
sooner!).

The Tuesday sprint review could then focus on being a sprint retrospective.

-- Len


On Tue, Jul 12, 2016 at 10:03 AM, Nick Boldt <nboldt at redhat.com> wrote:

> Forgive the dumb question, but if we do...
>
> * TP freeze on the last Wed of the sprint,
> * code freeze on the last Thurs of the sprint,
> * stage a build to QE on the last Friday of the sprint...
>
> then would this "go/no-go meeting" happen on the last Monday of the
> sprint, so that we can release from staging -> production on the last
> Tuesday of the sprint?
>
> And isn't that the purpose of the mojo doc [1] & email [2] you produce
> confirming that the build is ready to be released? Do we really need
> ANOTHER meeting when a single email w/ link to mojo doc has worked for the
> last bunch of releases?
>
> [1] https://mojo.redhat.com/docs/DOC-1064660
> [2]
> https://post-office.corp.redhat.com/mailman/private/jboss-devstudio-list/2016-January/msg00050.html
>
>
> Cheers,
>
> Nick
>
> On Mon, Jul 11, 2016 at 5:32 PM, Alexey Kazakov <alkazako at redhat.com>
> wrote:
>
>> It's not only for JBoss Tools but for entire group 2 (code) of the
>> devtools team. It includes Eclipse DTS and others.
>> This event is in devtools calendar and publicly available but I can add
>> you to the event if you want.
>>
>> Thanks.
>>
>>
>> On 07/11/2016 03:29 PM, George Gastaldi wrote:
>>
>> Are component leads also required to attend the event? I don't see it in
>> my calendar.
>>
>> *George Gastaldi*
>>
>> https://onename.com/gastaldi
>>
>> On Mon, Jul 11, 2016 at 4:27 PM, Alexey Kazakov <alkazako at redhat.com>
>> wrote:
>>
>>> I added your to the google event.
>>>
>>> On 07/11/2016 03:24 PM, Leonard Dimaggio wrote:
>>>
>>> I volunteer! (Just not when I am on PTO.  ;-)
>>>
>>> -- Len
>>>
>>> On Mon, Jul 11, 2016 at 3:15 PM, Alexey Kazakov < <alkazako at redhat.com>
>>> alkazako at redhat.com> wrote:
>>>
>>>> Yes we can try to combine it with the retrospective. But we will need
>>>> someone from QE to present on the retrospective then ;)
>>>>
>>>>
>>>> On 07/11/2016 03:04 PM, Leonard Dimaggio wrote:
>>>>
>>>> Hi Alexey,
>>>>
>>>> It wasn't possible to do this due to all the holidays and PTO last
>>>> week, but for future sprints (starting with 117), will we have a
>>>> pre-release review? It's not really a go/no-go meeting as the default is
>>>> "go" - but it would be good to have a sprint wrap-up review. Maybe we can
>>>> combine this with the retrospective?
>>>>
>>>> Thanks!,
>>>> Len
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov < <alkazako at redhat.com>
>>>> alkazako at redhat.com> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Just a reminder that our initial plan was to release milestones of
>>>>> JBoss
>>>>> Tools after every sprint and work on automation of this process so it
>>>>> doesn't require a lot of efforts any manual work.
>>>>> But because of holidays in Canada, USA and Czech Republic plus busy Red
>>>>> Hat Summit week before that we skipped public release of JBoss Tools
>>>>> 4.4.1.AM1.
>>>>> Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with
>>>>> codefreeze on July 21 (Thursday). This will be our first public
>>>>> milestone release for JBT 4.4.1.
>>>>> The release schedule is available here -
>>>>>
>>>>> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>>>>>
>>>>> Thank you.
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Len DiMaggio ( <ldimaggi at redhat.com>ldimaggi at redhat.com)
>>>> JBoss by Red Hat
>>>> 314 Littleton Road
>>>> Westford, MA 01886  USA
>>>> tel:  978.392.3179
>>>> cell: 781.472.9912
>>>> http://www.redhat.com
>>>> http://community.jboss.org/people/ldimaggio
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Len DiMaggio ( <ldimaggi at redhat.com>ldimaggi at redhat.com)
>>> JBoss by Red Hat
>>> 314 Littleton Road
>>> Westford, MA 01886  USA
>>> tel:  978.392.3179
>>> cell: 781.472.9912
>>> http://www.redhat.com
>>> http://community.jboss.org/people/ldimaggio
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Len DiMaggio (ldimaggi at redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886  USA
tel:  978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160712/41d9c626/attachment.html 

From alkazako at redhat.com  Tue Jul 12 10:23:38 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Tue, 12 Jul 2016 10:23:38 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <CA+QcL12sWy6xSWjBgv8ezU6ubC48V=9DB=awfDz9onF3FLBPNA@mail.gmail.com>
References: <577FF44F.50709@redhat.com>
	<CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>
	<5783F068.9030608@redhat.com>
	<CA+qK+9ne_ttkYH0HA_w1yNsvcHHwZ3EUf8hM8NM7tWzc+Wq13Q@mail.gmail.com>
	<5783F304.9090809@redhat.com>
	<CAMmsnJiYz=SsH3dB3S1HFnxsZknokNRmfYG0-a5-BTfsFPH9UQ@mail.gmail.com>
	<5784105B.7070807@redhat.com>
	<CA+QcL12sWy6xSWjBgv8ezU6ubC48V=9DB=awfDz9onF3FLBPNA@mail.gmail.com>
Message-ID: <5784FD6A.9070607@redhat.com>

No, we are not going to add one more meeting. For now we will see if we 
can combine it with already scheduled retrospective meeting which 
happens on the last Tuesday of the sprint.

On 07/12/2016 10:03 AM, Nick Boldt wrote:
> Forgive the dumb question, but if we do...
>
> * TP freeze on the last Wed of the sprint,
> * code freeze on the last Thurs of the sprint,
> * stage a build to QE on the last Friday of the sprint...
>
> then would this "go/no-go meeting" happen on the last Monday of the 
> sprint, so that we can release from staging -> production on the last 
> Tuesday of the sprint?
>
> And isn't that the purpose of the mojo doc [1] & email [2] you produce 
> confirming that the build is ready to be released? Do we really need 
> ANOTHER meeting when a single email w/ link to mojo doc has worked for 
> the last bunch of releases?
>
> [1] https://mojo.redhat.com/docs/DOC-1064660
> [2] 
> https://post-office.corp.redhat.com/mailman/private/jboss-devstudio-list/2016-January/msg00050.html
>
>
> Cheers,
>
> Nick
>
> On Mon, Jul 11, 2016 at 5:32 PM, Alexey Kazakov <alkazako at redhat.com 
> <mailto:alkazako at redhat.com>> wrote:
>
>     It's not only for JBoss Tools but for entire group 2 (code) of the
>     devtools team. It includes Eclipse DTS and others.
>     This event is in devtools calendar and publicly available but I
>     can add you to the event if you want.
>
>     Thanks.
>
>
>     On 07/11/2016 03:29 PM, George Gastaldi wrote:
>>     Are component leads also required to attend the event? I don't
>>     see it in my calendar.
>>
>>     *George Gastaldi*
>>
>>     https://onename.com/gastaldi
>>
>>     On Mon, Jul 11, 2016 at 4:27 PM, Alexey Kazakov
>>     <alkazako at redhat.com <mailto:alkazako at redhat.com>> wrote:
>>
>>         I added your to the google event.
>>
>>         On 07/11/2016 03:24 PM, Leonard Dimaggio wrote:
>>>         I volunteer! (Just not when I am on PTO.  ;-)
>>>
>>>         -- Len
>>>
>>>         On Mon, Jul 11, 2016 at 3:15 PM, Alexey Kazakov
>>>         <alkazako at redhat.com <mailto:alkazako at redhat.com>> wrote:
>>>
>>>             Yes we can try to combine it with the retrospective. But
>>>             we will need someone from QE to present on the
>>>             retrospective then ;)
>>>
>>>
>>>             On 07/11/2016 03:04 PM, Leonard Dimaggio wrote:
>>>>             Hi Alexey,
>>>>
>>>>             It wasn't possible to do this due to all the holidays
>>>>             and PTO last week, but for future sprints (starting
>>>>             with 117), will we have a pre-release review? It's not
>>>>             really a go/no-go meeting as the default is "go" - but
>>>>             it would be good to have a sprint wrap-up review. Maybe
>>>>             we can combine this with the retrospective?
>>>>
>>>>             Thanks!,
>>>>             Len
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>             On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov
>>>>             <alkazako at redhat.com <mailto:alkazako at redhat.com>> wrote:
>>>>
>>>>                 Hi all,
>>>>
>>>>                 Just a reminder that our initial plan was to
>>>>                 release milestones of JBoss
>>>>                 Tools after every sprint and work on automation of
>>>>                 this process so it
>>>>                 doesn't require a lot of efforts any manual work.
>>>>                 But because of holidays in Canada, USA and Czech
>>>>                 Republic plus busy Red
>>>>                 Hat Summit week before that we skipped public
>>>>                 release of JBoss Tools
>>>>                 4.4.1.AM1.
>>>>                 Our next (4.4.1.AM2) release will be on July 26
>>>>                 (Tuesday) with
>>>>                 codefreeze on July 21 (Thursday). This will be our
>>>>                 first public
>>>>                 milestone release for JBT 4.4.1.
>>>>                 The release schedule is available here -
>>>>                 https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>>>>
>>>>                 Thank you.
>>>>                 _______________________________________________
>>>>                 jbosstools-dev mailing list
>>>>                 jbosstools-dev at lists.jboss.org
>>>>                 <mailto:jbosstools-dev at lists.jboss.org>
>>>>                 https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>>
>>>>
>>>>
>>>>             -- 
>>>>             Len DiMaggio (ldimaggi at redhat.com
>>>>             <mailto:ldimaggi at redhat.com>)
>>>>             JBoss by Red Hat
>>>>             314 Littleton Road
>>>>             Westford, MA 01886  USA
>>>>             tel: 978.392.3179 <tel:978.392.3179>
>>>>             cell: 781.472.9912 <tel:781.472.9912>
>>>>             http://www.redhat.com
>>>>             http://community.jboss.org/people/ldimaggio
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>         -- 
>>>         Len DiMaggio (ldimaggi at redhat.com <mailto:ldimaggi at redhat.com>)
>>>         JBoss by Red Hat
>>>         314 Littleton Road
>>>         Westford, MA 01886  USA
>>>         tel: 978.392.3179 <tel:978.392.3179>
>>>         cell: 781.472.9912 <tel:781.472.9912>
>>>         http://www.redhat.com
>>>         http://community.jboss.org/people/ldimaggio
>>>
>>>
>>
>>
>>         _______________________________________________
>>         jbosstools-dev mailing list
>>         jbosstools-dev at lists.jboss.org
>>         <mailto:jbosstools-dev at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>
>
>     _______________________________________________
>     jbosstools-dev mailing list
>     jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160712/2864d29b/attachment-0001.html 

From nboldt at redhat.com  Tue Jul 12 10:45:23 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 12 Jul 2016 10:45:23 -0400
Subject: [jbosstools-dev] JBoss Toos 4.4.1.AM2 release schedule
In-Reply-To: <CA+qK+9kESSVDVcJK__NmTGD3sOgChbw1-E82MycdTrru4CGCAA@mail.gmail.com>
References: <577FF44F.50709@redhat.com>
	<CA+qK+9n=psHCWgcoUEKARigaD8BFBRuWCYf1v2LC0a2Ubj2EPw@mail.gmail.com>
	<5783F068.9030608@redhat.com>
	<CA+qK+9ne_ttkYH0HA_w1yNsvcHHwZ3EUf8hM8NM7tWzc+Wq13Q@mail.gmail.com>
	<5783F304.9090809@redhat.com>
	<CAMmsnJiYz=SsH3dB3S1HFnxsZknokNRmfYG0-a5-BTfsFPH9UQ@mail.gmail.com>
	<5784105B.7070807@redhat.com>
	<CA+QcL12sWy6xSWjBgv8ezU6ubC48V=9DB=awfDz9onF3FLBPNA@mail.gmail.com>
	<CA+qK+9kESSVDVcJK__NmTGD3sOgChbw1-E82MycdTrru4CGCAA@mail.gmail.com>
Message-ID: <CA+QcL10+2OQHX7kH_ZpYG2iVjx6BtUMq3gCRDWONA13o_cUJHw@mail.gmail.com>

I would hope so too. To ensure that's the case, QE and dev need to be
closely working together and using the CI builds.

If a blocker is reported on the 5x5 call, that might impact the ability to
build over night on Thursday evening, in order to then have the bits staged
on Friday.

But since there's a whole day to fix it (8:30am EST -> 8pm EST) odds are
pretty good that whatever redness we experience Thurs morning will have
cleared up by Thurs night. :D



On Tue, Jul 12, 2016 at 10:22 AM, Leonard Dimaggio <ldimaggi at redhat.com>
wrote:

> I'd hope that if there was a need (blocking bug) that would prevent the
> release, that we'd see that bug in time for the Thursday 5x5 meeting (or
> sooner!).
>
> The Tuesday sprint review could then focus on being a sprint
> retrospective.
>
> -- Len
>
>
> On Tue, Jul 12, 2016 at 10:03 AM, Nick Boldt <nboldt at redhat.com> wrote:
>
>> Forgive the dumb question, but if we do...
>>
>> * TP freeze on the last Wed of the sprint,
>> * code freeze on the last Thurs of the sprint,
>> * stage a build to QE on the last Friday of the sprint...
>>
>> then would this "go/no-go meeting" happen on the last Monday of the
>> sprint, so that we can release from staging -> production on the last
>> Tuesday of the sprint?
>>
>> And isn't that the purpose of the mojo doc [1] & email [2] you produce
>> confirming that the build is ready to be released? Do we really need
>> ANOTHER meeting when a single email w/ link to mojo doc has worked for the
>> last bunch of releases?
>>
>> [1] https://mojo.redhat.com/docs/DOC-1064660
>> [2]
>> https://post-office.corp.redhat.com/mailman/private/jboss-devstudio-list/2016-January/msg00050.html
>>
>>
>> Cheers,
>>
>> Nick
>>
>> On Mon, Jul 11, 2016 at 5:32 PM, Alexey Kazakov <alkazako at redhat.com>
>> wrote:
>>
>>> It's not only for JBoss Tools but for entire group 2 (code) of the
>>> devtools team. It includes Eclipse DTS and others.
>>> This event is in devtools calendar and publicly available but I can add
>>> you to the event if you want.
>>>
>>> Thanks.
>>>
>>>
>>> On 07/11/2016 03:29 PM, George Gastaldi wrote:
>>>
>>> Are component leads also required to attend the event? I don't see it in
>>> my calendar.
>>>
>>> *George Gastaldi*
>>>
>>> https://onename.com/gastaldi
>>>
>>> On Mon, Jul 11, 2016 at 4:27 PM, Alexey Kazakov <alkazako at redhat.com>
>>> wrote:
>>>
>>>> I added your to the google event.
>>>>
>>>> On 07/11/2016 03:24 PM, Leonard Dimaggio wrote:
>>>>
>>>> I volunteer! (Just not when I am on PTO.  ;-)
>>>>
>>>> -- Len
>>>>
>>>> On Mon, Jul 11, 2016 at 3:15 PM, Alexey Kazakov < <alkazako at redhat.com>
>>>> alkazako at redhat.com> wrote:
>>>>
>>>>> Yes we can try to combine it with the retrospective. But we will need
>>>>> someone from QE to present on the retrospective then ;)
>>>>>
>>>>>
>>>>> On 07/11/2016 03:04 PM, Leonard Dimaggio wrote:
>>>>>
>>>>> Hi Alexey,
>>>>>
>>>>> It wasn't possible to do this due to all the holidays and PTO last
>>>>> week, but for future sprints (starting with 117), will we have a
>>>>> pre-release review? It's not really a go/no-go meeting as the default is
>>>>> "go" - but it would be good to have a sprint wrap-up review. Maybe we can
>>>>> combine this with the retrospective?
>>>>>
>>>>> Thanks!,
>>>>> Len
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov < <alkazako at redhat.com>
>>>>> alkazako at redhat.com> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Just a reminder that our initial plan was to release milestones of
>>>>>> JBoss
>>>>>> Tools after every sprint and work on automation of this process so it
>>>>>> doesn't require a lot of efforts any manual work.
>>>>>> But because of holidays in Canada, USA and Czech Republic plus busy
>>>>>> Red
>>>>>> Hat Summit week before that we skipped public release of JBoss Tools
>>>>>> 4.4.1.AM1.
>>>>>> Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with
>>>>>> codefreeze on July 21 (Thursday). This will be our first public
>>>>>> milestone release for JBT 4.4.1.
>>>>>> The release schedule is available here -
>>>>>>
>>>>>> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>>>>>>
>>>>>> Thank you.
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Len DiMaggio ( <ldimaggi at redhat.com>ldimaggi at redhat.com)
>>>>> JBoss by Red Hat
>>>>> 314 Littleton Road
>>>>> Westford, MA 01886  USA
>>>>> tel:  978.392.3179
>>>>> cell: 781.472.9912
>>>>> http://www.redhat.com
>>>>> http://community.jboss.org/people/ldimaggio
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Len DiMaggio ( <ldimaggi at redhat.com>ldimaggi at redhat.com)
>>>> JBoss by Red Hat
>>>> 314 Littleton Road
>>>> Westford, MA 01886  USA
>>>> tel:  978.392.3179
>>>> cell: 781.472.9912
>>>> http://www.redhat.com
>>>> http://community.jboss.org/people/ldimaggio
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>>
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
>
> --
> Len DiMaggio (ldimaggi at redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>
>


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160712/4b1ea7eb/attachment.html 

From ddekany at freemail.hu  Wed Jul 13 17:18:28 2016
From: ddekany at freemail.hu (Daniel Dekany)
Date: Wed, 13 Jul 2016 23:18:28 +0200
Subject: [jbosstools-dev] Any way to make FreeMarker IDE fixes available
	with less delay?
In-Reply-To: <1663741876.20160708085202@freemail.hu>
References: <1139481114.20160407233937@freemail.hu>
	<5706D873.2090503@redhat.com>
	<1564144359.20160408083434@freemail.hu>
	<58B67DA7-810A-4E7F-8427-1741A75E6B3C@redhat.com>
	<916097661.20160413023325@freemail.hu>
	<1067385354.20160707232724@freemail.hu>
	<577EEB11.7030601@redhat.com>
	<1663741876.20160708085202@freemail.hu>
Message-ID: <99414195.20160713231828@freemail.hu>

Friday, July 8, 2016, 8:52:02 AM, Daniel Dekany wrote:

> Friday, July 8, 2016, 1:51:45 AM, Alexey Kazakov wrote:
>
>> fix licenses in the headers of new classes

You have provided this example:
https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.cdk.server/src/org/jboss/tools/openshift/cdk/server/core/internal/CDKConstantUtility.java

I wonder if the "Contributors:" part is necessary, and if so then
should I mention JBoss there (and then with what wording, given the
initial API wasn't provided by JBoss), or only my name. I definitely
would prefer not having a Contributors section at all, especially not
one with my name (it's wrong on the same way as the @author JavaDoc
tag is), but then, it's up to the JBoss of course.

(Also, if the other headers should be replaced later too, consider
that then nobody will try figure out for each file who the
contributors were...)

-- 
Thanks,
 Daniel Dekany


From aer-bot at ctrlflow.com  Sun Jul 17 23:30:01 2016
From: aer-bot at ctrlflow.com (Automated Error Reporting Bot)
Date: Mon, 18 Jul 2016 03:30:01 +0000 (UTC)
Subject: [jbosstools-dev] [aeri] Weekly JBoss Tools Error Reports Digest
Message-ID: <178902307.0.1468812601293.JavaMail.ec2-user@aeri-rh>

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160718/6e8d7f79/attachment-0001.html 

From marcel.bruch at codetrails.com  Wed Jul 20 10:59:25 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Wed, 20 Jul 2016 16:59:25 +0200
Subject: [jbosstools-dev] [aeri] Automatically reopen (presumably) fixed
	problems
Message-ID: <42768517-3DFA-488D-B9EA-AD1805B2B579@codetrails.com>

Greetings jboss tools devs,

yesterday the question popped up whether AERI can automatically reopen problems that have been marked as fixed but still receive error reports for later versions of the software (see [1] for details).

AERI can, but it may not be obvious to everyone. I thus published a short blog post that illustrates how you can set up  an automated action for this specific scenario [2]. HTH.

In case you have further questions, please let me know.

Marcel

[1] https://issues.jboss.org/browse/JBIDE-22516 <https://issues.jboss.org/browse/JBIDE-22516>
[2] https://blog.ctrlflow.com/hidden-gems-auto-reopening-problems/ <https://blog.ctrlflow.com/hidden-gems-auto-reopening-problems/>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160720/72ee3a86/attachment.html 

From marcel.bruch at codetrails.com  Wed Jul 20 14:48:37 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Wed, 20 Jul 2016 20:48:37 +0200
Subject: [jbosstools-dev] [aeri] Introducing project dashboards
Message-ID: <05D7D17C-C7FF-4DDB-B11B-306E3A8EF22A@codetrails.com>

Greetings jbosstools-dev,

I?d like to announce the availability of project dashboards for all JBoss tools projects. Dashboards provide you a quick overview about your project?s key metrics. See the Openshift project dashboard [1] for an example. A detailed description of the dashboards is available at [2].


In case you have any questions about using dashboards or feature requests, please let me know.

Cheers,
Marcel


[1] https://redhat.ctrlflow.com/reviewers/#!/projects/56b73567e4b0a41ffccd2780/dashboard <https://redhat.ctrlflow.com/reviewers/#!/projects/56b73567e4b0a41ffccd2780/dashboard>
[2] https://blog.ctrlflow.com/project-dashboards/ <https://blog.ctrlflow.com/project-dashboards/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160720/7c67078b/attachment.html 

From nboldt at redhat.com  Wed Jul 20 15:06:20 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 20 Jul 2016 15:06:20 -0400
Subject: [jbosstools-dev] Schedule reminder: TP freeze, code freeze,
 and 4.4.1.AM2 / 10.0.1.AM2 release coming up soon!
Message-ID: <CA+QcL13ZexRKk71UvY8_x3mPkTOvLw9mODfttGAwsRZz4Emq-w@mail.gmail.com>

Just a reminder of upcoming dates:

Target Platform Freeze for 4.4.1.AM2 / 10.0.1.AM2 :: Today!
Code Freeze for 4.4.1.AM2 / 10.0.1.AM2 :: Tomorrow night Thu Jul 21
around 5pm. Need more time? Just ask!
QE Staging build of 4.4.1.AM2 / 10.0.1.AM2 :: Fri Jul 22
Public release of 4.4.1.AM2 (not 10.0.1.AM2) :: Tues Jul 26 (end of
the current sprint).

If you have questions about this, please don't hesitate to ask.

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From ldimaggi at redhat.com  Wed Jul 20 21:04:19 2016
From: ldimaggi at redhat.com (Leonard Dimaggio)
Date: Wed, 20 Jul 2016 21:04:19 -0400
Subject: [jbosstools-dev] Schedule reminder: TP freeze, code freeze,
 and 4.4.1.AM2 / 10.0.1.AM2 release coming up soon!
In-Reply-To: <CA+QcL13ZexRKk71UvY8_x3mPkTOvLw9mODfttGAwsRZz4Emq-w@mail.gmail.com>
References: <CA+QcL13ZexRKk71UvY8_x3mPkTOvLw9mODfttGAwsRZz4Emq-w@mail.gmail.com>
Message-ID: <CA+qK+9mYBPeF35TRCc0SXLukz+ou6wyNdYWFx37QVsjmxVb94w@mail.gmail.com>

We really need a fix for this one before the code freeze -
https://issues.jboss.org/browse/JBIDE-22766 - thanks!

On Wed, Jul 20, 2016 at 3:06 PM, Nick Boldt <nboldt at redhat.com> wrote:

> Just a reminder of upcoming dates:
>
> Target Platform Freeze for 4.4.1.AM2 / 10.0.1.AM2 :: Today!
> Code Freeze for 4.4.1.AM2 / 10.0.1.AM2 :: Tomorrow night Thu Jul 21
> around 5pm. Need more time? Just ask!
> QE Staging build of 4.4.1.AM2 / 10.0.1.AM2 :: Fri Jul 22
> Public release of 4.4.1.AM2 (not 10.0.1.AM2) :: Tues Jul 26 (end of
> the current sprint).
>
> If you have questions about this, please don't hesitate to ask.
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Len DiMaggio (ldimaggi at redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886  USA
tel:  978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160720/c87c4728/attachment.html 

From nboldt at redhat.com  Thu Jul 21 08:11:25 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 21 Jul 2016 08:11:25 -0400
Subject: [jbosstools-dev] Schedule reminder: TP freeze, code freeze,
 and 4.4.1.AM2 / 10.0.1.AM2 release coming up soon!
In-Reply-To: <CA+qK+9mYBPeF35TRCc0SXLukz+ou6wyNdYWFx37QVsjmxVb94w@mail.gmail.com>
References: <CA+QcL13ZexRKk71UvY8_x3mPkTOvLw9mODfttGAwsRZz4Emq-w@mail.gmail.com>
	<CA+qK+9mYBPeF35TRCc0SXLukz+ou6wyNdYWFx37QVsjmxVb94w@mail.gmail.com>
Message-ID: <CA+QcL12t4+UKErJGKqvk7L+tqAkjc-dUh6wSsMZUVk7b=2+EOw@mail.gmail.com>

All builds are currently blocked by
https://engineering.redhat.com/rt/Ticket/Display.html?id=412491 so I can't
fix the above issue, or confirm my other fixes have worked, until MW
Jenkins gets its ssh access back.

Hope this happens today.

Nick

On Jul 20, 2016 9:05 PM, "Leonard Dimaggio" <ldimaggi at redhat.com> wrote:

> We really need a fix for this one before the code freeze -
> https://issues.jboss.org/browse/JBIDE-22766 - thanks!
>
> On Wed, Jul 20, 2016 at 3:06 PM, Nick Boldt <nboldt at redhat.com> wrote:
>
>> Just a reminder of upcoming dates:
>>
>> Target Platform Freeze for 4.4.1.AM2 / 10.0.1.AM2 :: Today!
>> Code Freeze for 4.4.1.AM2 / 10.0.1.AM2 :: Tomorrow night Thu Jul 21
>> around 5pm. Need more time? Just ask!
>> QE Staging build of 4.4.1.AM2 / 10.0.1.AM2 :: Fri Jul 22
>> Public release of 4.4.1.AM2 (not 10.0.1.AM2) :: Tues Jul 26 (end of
>> the current sprint).
>>
>> If you have questions about this, please don't hesitate to ask.
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
>
> --
> Len DiMaggio (ldimaggi at redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160721/3ca8ecce/attachment-0001.html 

From nboldt at redhat.com  Thu Jul 21 17:07:24 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 21 Jul 2016 17:07:24 -0400
Subject: [jbosstools-dev] 4.4.1.AM2 build may not happen this week
Message-ID: <CA+QcL10m1P1iGrKSRxP9TcPa+WL11wbDt=0BN4sTy4vHJA-3cA@mail.gmail.com>

Please note that until this issue is resolved, we won't be able to
release 4.4.1.AM2 without some magic (read: lots of manual effort).

All Boston MW Jenkins jobs are currently experiencing "ssh: connect to
host filemgmt.jboss.org port 22: Connection refused". So until that's
fixed, CI builds are on hold.

Apologies,

Nick


---------- Forwarded message ----------
From: Nick Boldt <nboldt at redhat.com>
Date: Thu, Jul 21, 2016 at 12:26 PM
Subject: Re: [engineering.redhat.com #412491] Connection refused when
ssh'ing to filemgmt.jboss.org from Jenkins
To: eng-ops at redhat.com
Cc: Lars Heinemann <lheinema at redhat.com>


To clarify, this issue doesn't block JBIDE-22766. But it DOES block us
getting NEW builds published such that QE can test them.

Please escalate -- this is quite urgent.

On Thu, Jul 21, 2016 at 10:34 AM, Len DiMaggio via RT
<eng-ops at redhat.com> wrote:
> Ticket <URL: https://engineering.redhat.com/rt/Ticket/Display.html?id=412491 >
>
> Can this issue be escalated? This is blocking product release testing. Thanks!
>
> https://issues.jboss.org/browse/JBIDE-22766
>
>
>
>
>
> On Thu Jul 21 04:13:23 2016, pjanouse at redhat.com wrote:
>> @eng-ops
>>
>> It looks like the whole MW QA lab (VLAN?) lost its network connectivity at
>> least to the affected host filemgmt.jboss.org. Could you manage to fix it
>> please?
>>
>> Thank you,
>>
>> Pavel
>



--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From marcel.bruch at codetrails.com  Fri Jul 22 05:25:09 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Fri, 22 Jul 2016 11:25:09 +0200
Subject: [jbosstools-dev] [aeri] How To Automatically Create JIRA Issues
	from Error Reports
Message-ID: <4D01153F-42F1-423A-969C-0A2130EC2023@codetrails.com>

Greetings JBoss Tools Devs,

another question that was raised (and I think might be relevant to some of you) was, how to configure AERI to automatically create JIRA tickets for problems. I published a short blog post describing how projects can set up such an automated action here [1].

Regards,
Marcel


[1] https://blog.ctrlflow.com/hidden-gems-automatically-create-bugs-error-reports/ <https://blog.ctrlflow.com/hidden-gems-automatically-create-bugs-error-reports/>






-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160722/3df6f8ba/attachment.html 

From aer-bot at ctrlflow.com  Sun Jul 24 23:30:01 2016
From: aer-bot at ctrlflow.com (Automated Error Reporting Bot)
Date: Mon, 25 Jul 2016 03:30:01 +0000 (UTC)
Subject: [jbosstools-dev] [aeri] Weekly JBoss Tools Error Reports Digest
Message-ID: <196535827.0.1469417401234.JavaMail.ec2-user@aeri-rh>

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160725/48e96e93/attachment-0001.html 

From marcel.bruch at codetrails.com  Mon Jul 25 07:02:27 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Mon, 25 Jul 2016 13:02:27 +0200
Subject: [jbosstools-dev] [aeri] Now supports github logins
Message-ID: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>

Greetings JBosstools Devs,

as discussed last week, we AERI now supports GitHub authentication and authorization in addition to the previous username-password based authentication. That means you can now log in with your GitHub account. Your roles (reviewer, admin, or just reporter) are determined by your membership in the JBoss Tools GitHub organisation and teams. If you log in and are forwarded to a /reporter/ URL, please contact your GitHub org admins (e.g. Alexey or Fred) and ask them to review your team memberships.


Please note that you can still log in with the previous credentials. But this account may be shut down by your org admins soon. Thus, please switch over to GitHub authorization soon. Thank you.


If you experience insane login delays (say, 10 seconds and more) please let me know. There might be a few things to tweak.


Have a great week,
Marcel


-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160725/86705fd6/attachment.html 

From nboldt at redhat.com  Mon Jul 25 09:43:19 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 25 Jul 2016 09:43:19 -0400
Subject: [jbosstools-dev] 4.4.1.AM2 build may not happen this week
In-Reply-To: <CA+QcL10m1P1iGrKSRxP9TcPa+WL11wbDt=0BN4sTy4vHJA-3cA@mail.gmail.com>
References: <CA+QcL10m1P1iGrKSRxP9TcPa+WL11wbDt=0BN4sTy4vHJA-3cA@mail.gmail.com>
Message-ID: <CA+QcL108+pfZ0OqC=NMuFPbAn3EowpGSFtykQVFu22SDPntFvg@mail.gmail.com>

Ticket is now resolved. Something changed with firewalls and DNS
tables last week.

I'm building the stack now, to collect the changes that were stuck in
queue / unable to be published since Jul 20.

You can watch for new builds here, as they're created and published:

http://download.jboss.org/jbosstools/neon/snapshots/builds/?C=M;O=D

Hope to have something staged for QE this afternoon.


On Thu, Jul 21, 2016 at 5:07 PM, Nick Boldt <nboldt at redhat.com> wrote:
> Please note that until this issue is resolved, we won't be able to
> release 4.4.1.AM2 without some magic (read: lots of manual effort).
>
> All Boston MW Jenkins jobs are currently experiencing "ssh: connect to
> host filemgmt.jboss.org port 22: Connection refused". So until that's
> fixed, CI builds are on hold.
>
> Apologies,
>
> Nick
>
>
> ---------- Forwarded message ----------
> From: Nick Boldt <nboldt at redhat.com>
> Date: Thu, Jul 21, 2016 at 12:26 PM
> Subject: Re: [engineering.redhat.com #412491] Connection refused when
> ssh'ing to filemgmt.jboss.org from Jenkins
> To: eng-ops at redhat.com
> Cc: Lars Heinemann <lheinema at redhat.com>
>
>
> To clarify, this issue doesn't block JBIDE-22766. But it DOES block us
> getting NEW builds published such that QE can test them.
>
> Please escalate -- this is quite urgent.
>
> On Thu, Jul 21, 2016 at 10:34 AM, Len DiMaggio via RT
> <eng-ops at redhat.com> wrote:
>> Ticket <URL: https://engineering.redhat.com/rt/Ticket/Display.html?id=412491 >
>>
>> Can this issue be escalated? This is blocking product release testing. Thanks!
>>
>> https://issues.jboss.org/browse/JBIDE-22766
>>
>>
>>
>>
>>
>> On Thu Jul 21 04:13:23 2016, pjanouse at redhat.com wrote:
>>> @eng-ops
>>>
>>> It looks like the whole MW QA lab (VLAN?) lost its network connectivity at
>>> least to the affected host filemgmt.jboss.org. Could you manage to fix it
>>> please?
>>>
>>> Thank you,
>>>
>>> Pavel
>>
>
>
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
>
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com



-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From nboldt at redhat.com  Mon Jul 25 17:15:05 2016
From: nboldt at redhat.com (nboldt at redhat.com)
Date: Mon, 25 Jul 2016 17:15:05 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.4.1.AM2 bits available for QE
	testing
Message-ID: <201607252115.u6PLF58R032665@dev01.mw.lab.eng.bos.redhat.com>


These are not FINAL bits, but preliminary results for QE & community testing. Not for redistribution to customers or end users.

Update site: http://download.jboss.org/jbosstools/neon/staging/updates/

New + noteworthy (subject to change):
* https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
* http://tools.jboss.org/documentation/whatsnew/

Schedule: https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page

--

Additional update sites:
* http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.1.AM2/
* http://download.jboss.org/jbosstools/neon/staging/updates/coretests/4.4.1.AM2/

Target platforms:
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Final
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.1.AM1-SNAPSHOT

Discovery sites:
* http://download.jboss.org/jbosstools/neon/staging/updates/discovery.central/4.4.1.AM2/
* http://download.jboss.org/jbosstools/neon/staging/updates/discovery.earlyaccess/4.4.1.AM2/

Build folders (for build logs & update site zips):
* http://download.jboss.org/jbosstools/neon/staging/builds/


From marcel.bruch at codetrails.com  Tue Jul 26 05:06:02 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Tue, 26 Jul 2016 11:06:02 +0200
Subject: [jbosstools-dev] [aeri] Choosing a project dashboard as "starting
	page"
Message-ID: <AD0504A5-BDC9-44D3-A7B3-B683853DE513@codetrails.com>

Greetings JBoss Tools devs,

as requested by one project lead, I?m happy to announce that reviewers can now configure which project dashboard they?d like to see after log in.

Configuration is straight. Log in, go to the (new) user?s settings page and select the project you like to be redirected to after login:



If you have any questions or feature requests, please do not hesitate to contact me by email, twitter (@marcelbruch) or Skype (marcel_bruch).

Best,
Marcel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160726/63d9373c/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-07-26 at 10.58.53.png
Type: image/png
Size: 161616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160726/63d9373c/attachment-0001.png 

From manderse at redhat.com  Tue Jul 26 07:16:56 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 26 Jul 2016 13:16:56 +0200
Subject: [jbosstools-dev] Any way to make FreeMarker IDE fixes available
 with less delay?
In-Reply-To: <99414195.20160713231828@freemail.hu>
References: <1139481114.20160407233937@freemail.hu>
	<5706D873.2090503@redhat.com> <1564144359.20160408083434@freemail.hu>
	<58B67DA7-810A-4E7F-8427-1741A75E6B3C@redhat.com>
	<916097661.20160413023325@freemail.hu>
	<1067385354.20160707232724@freemail.hu> <577EEB11.7030601@redhat.com>
	<1663741876.20160708085202@freemail.hu>
	<99414195.20160713231828@freemail.hu>
Message-ID: <00AD098D-0BAA-4E65-97B0-C394BF3B92BA@redhat.com>

On 13 Jul 2016, at 23:18, Daniel Dekany wrote:

> Friday, July 8, 2016, 8:52:02 AM, Daniel Dekany wrote:
>
>> Friday, July 8, 2016, 1:51:45 AM, Alexey Kazakov wrote:
>>
>>> fix licenses in the headers of new classes
>
> You have provided this example:
> https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.cdk.server/src/org/jboss/tools/openshift/cdk/server/core/internal/CDKConstantUtility.java
>
> I wonder if the "Contributors:" part is necessary, and if so then
> should I mention JBoss there (and then with what wording, given the
> initial API wasn't provided by JBoss), or only my name. I definitely
> would prefer not having a Contributors section at all, especially not
> one with my name (it's wrong on the same way as the @author JavaDoc
> tag is), but then, it's up to the JBoss of course.
>
> (Also, if the other headers should be replaced later too, consider
> that then nobody will try figure out for each file who the
> contributors were...)

Heya, getting back from vacation thus sorry for delay in answer.

If you don't want to be listed in Contributors that is your choice.
It is not a requirement it is listed there - we just tend to do it
for new and when modifying things.

/max
http://about.me/maxandersen


From ddekany at freemail.hu  Tue Jul 26 13:00:04 2016
From: ddekany at freemail.hu (Daniel Dekany)
Date: Tue, 26 Jul 2016 19:00:04 +0200
Subject: [jbosstools-dev] Any way to make FreeMarker IDE fixes available
	with less delay?
In-Reply-To: <00AD098D-0BAA-4E65-97B0-C394BF3B92BA@redhat.com>
References: <1139481114.20160407233937@freemail.hu>
	<5706D873.2090503@redhat.com>
	<1564144359.20160408083434@freemail.hu>
	<58B67DA7-810A-4E7F-8427-1741A75E6B3C@redhat.com>
	<916097661.20160413023325@freemail.hu>
	<1067385354.20160707232724@freemail.hu>
	<577EEB11.7030601@redhat.com>
	<1663741876.20160708085202@freemail.hu>
	<99414195.20160713231828@freemail.hu>
	<00AD098D-0BAA-4E65-97B0-C394BF3B92BA@redhat.com>
Message-ID: <1862334389.20160726190004@freemail.hu>

So is the whole "Contributors" section omittable? Or should it be
there but left empty (looks kind of strange)?

Should the headers of the earlier files (which use the old license) be
replaced with such a header?

-- 
Thanks,
 Daniel Dekany


Tuesday, July 26, 2016, 1:16:56 PM, Max Rydahl Andersen wrote:

> On 13 Jul 2016, at 23:18, Daniel Dekany wrote:
>
>> Friday, July 8, 2016, 8:52:02 AM, Daniel Dekany wrote:
>>
>>> Friday, July 8, 2016, 1:51:45 AM, Alexey Kazakov wrote:
>>>
>>>> fix licenses in the headers of new classes
>>
>> You have provided this example:
>> https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.cdk.server/src/org/jboss/tools/openshift/cdk/server/core/internal/CDKConstantUtility.java
>>
>> I wonder if the "Contributors:" part is necessary, and if so then
>> should I mention JBoss there (and then with what wording, given the
>> initial API wasn't provided by JBoss), or only my name. I definitely
>> would prefer not having a Contributors section at all, especially not
>> one with my name (it's wrong on the same way as the @author JavaDoc
>> tag is), but then, it's up to the JBoss of course.
>>
>> (Also, if the other headers should be replaced later too, consider
>> that then nobody will try figure out for each file who the
>> contributors were...)
>
> Heya, getting back from vacation thus sorry for delay in answer.
>
> If you don't want to be listed in Contributors that is your choice.
> It is not a requirement it is listed there - we just tend to do it
> for new and when modifying things.
>
> /max
> http://about.me/maxandersen
>

-- 
Thanks,
 Daniel Dekany


From akazakov at redhat.com  Fri Jul 22 02:59:01 2016
From: akazakov at redhat.com (akazakov at redhat.com)
Date: Fri, 22 Jul 2016 02:59:01 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201607220659.u6M6x1kV000697@int-mx10.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3972

https://issues.jboss.org/browse/JBDS-3972
Summary: RHDS freezes on opening attached xml file

Assignee: None set.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 12:09:10.041559

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From akazakov at redhat.com  Fri Jul 22 05:12:45 2016
From: akazakov at redhat.com (akazakov at redhat.com)
Date: Fri, 22 Jul 2016 05:12:45 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201607220912.u6M9CjWD006727@int-mx11.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3972

https://issues.jboss.org/browse/JBDS-3972
Summary: RHDS freezes on opening attached xml file

Assignee: None set.
Component: None set - please fix.
Problem: No component - please ensure this issue has a proper component set.
Last Update: 0:14:41.819079

----------------------------



Query used: https://issues.jboss.org/issues/?jql=%28filter%3D%27ds_lint_nocomponent%27%29

From akazakov at redhat.com  Sat Jul 23 02:58:46 2016
From: akazakov at redhat.com (akazakov at redhat.com)
Date: Sat, 23 Jul 2016 02:58:46 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201607230658.u6N6wkwW027938@int-mx11.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3972

https://issues.jboss.org/browse/JBDS-3972
Summary: RHDS freezes on opening attached xml file

Assignee: None set.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 22:00:42.746090

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From akazakov at redhat.com  Sun Jul 24 02:58:49 2016
From: akazakov at redhat.com (akazakov at redhat.com)
Date: Sun, 24 Jul 2016 02:58:49 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201607240658.u6O6wn7U029322@int-mx11.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3972

https://issues.jboss.org/browse/JBDS-3972
Summary: RHDS freezes on opening attached xml file

Assignee: None set.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 1 day, 22:00:45.156612

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From akazakov at redhat.com  Mon Jul 25 02:58:58 2016
From: akazakov at redhat.com (akazakov at redhat.com)
Date: Mon, 25 Jul 2016 02:58:58 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201607250658.u6P6wwwg031901@int-mx10.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3972

https://issues.jboss.org/browse/JBDS-3972
Summary: RHDS freezes on opening attached xml file

Assignee: None set.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 2 days, 22:00:54.086810

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From akazakov at redhat.com  Tue Jul 26 02:58:56 2016
From: akazakov at redhat.com (akazakov at redhat.com)
Date: Tue, 26 Jul 2016 02:58:56 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201607260658.u6Q6wuZ1009182@int-mx13.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3972

https://issues.jboss.org/browse/JBDS-3972
Summary: RHDS freezes on opening attached xml file

Assignee: None set.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 3 days, 22:00:52.684846

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From manderse at redhat.com  Wed Jul 27 01:48:27 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 27 Jul 2016 07:48:27 +0200
Subject: [jbosstools-dev] Any way to make FreeMarker IDE fixes available
 with less delay?
In-Reply-To: <1862334389.20160726190004@freemail.hu>
References: <1139481114.20160407233937@freemail.hu>
	<5706D873.2090503@redhat.com> <1564144359.20160408083434@freemail.hu>
	<58B67DA7-810A-4E7F-8427-1741A75E6B3C@redhat.com>
	<916097661.20160413023325@freemail.hu>
	<1067385354.20160707232724@freemail.hu> <577EEB11.7030601@redhat.com>
	<1663741876.20160708085202@freemail.hu>
	<99414195.20160713231828@freemail.hu>
	<00AD098D-0BAA-4E65-97B0-C394BF3B92BA@redhat.com>
	<1862334389.20160726190004@freemail.hu>
Message-ID: <E3E909EB-5C4D-4245-90CB-37159F156C76@redhat.com>

On 26 Jul 2016, at 19:00, Daniel Dekany wrote:

> So is the whole "Contributors" section omittable? Or should it be
> there but left empty (looks kind of strange)?

You can leave out the contributors for new files if you want.

> Should the headers of the earlier files (which use the old license) be
> replaced with such a header?

No, if someone wished to be listed as contributor on the file
that is their choice.

/max

> -- 
> Thanks,
>  Daniel Dekany
>
> Tuesday, July 26, 2016, 1:16:56 PM, Max Rydahl Andersen wrote:
>
>> On 13 Jul 2016, at 23:18, Daniel Dekany wrote:
>>
>>> Friday, July 8, 2016, 8:52:02 AM, Daniel Dekany wrote:
>>>
>>>> Friday, July 8, 2016, 1:51:45 AM, Alexey Kazakov wrote:
>>>>
>>>>> fix licenses in the headers of new classes
>>>
>>> You have provided this example:
>>> https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.cdk.server/src/org/jboss/tools/openshift/cdk/server/core/internal/CDKConstantUtility.java
>>>
>>> I wonder if the "Contributors:" part is necessary, and if so then
>>> should I mention JBoss there (and then with what wording, given the
>>> initial API wasn't provided by JBoss), or only my name. I definitely
>>> would prefer not having a Contributors section at all, especially 
>>> not
>>> one with my name (it's wrong on the same way as the @author JavaDoc
>>> tag is), but then, it's up to the JBoss of course.
>>>
>>> (Also, if the other headers should be replaced later too, consider
>>> that then nobody will try figure out for each file who the
>>> contributors were...)
>>
>> Heya, getting back from vacation thus sorry for delay in answer.
>>
>> If you don't want to be listed in Contributors that is your choice.
>> It is not a requirement it is listed there - we just tend to do it
>> for new and when modifying things.
>>
>> /max
>> http://about.me/maxandersen
>>
>
> -- 
> Thanks,
>  Daniel Dekany
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From manderse at redhat.com  Thu Jul 28 04:53:04 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 28 Jul 2016 10:53:04 +0200
Subject: [jbosstools-dev] [aeri] Now supports github logins
In-Reply-To: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>
References: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>
Message-ID: <6B01203C-80A3-49A2-81D0-602FDC32B99F@redhat.com>

Excellent work Marcel!

/max

> Greetings JBosstools Devs,
>
> as discussed last week, we AERI now supports GitHub authentication and 
> authorization in addition to the previous username-password based 
> authentication. That means you can now log in with your GitHub 
> account. Your roles (reviewer, admin, or just reporter) are determined 
> by your membership in the JBoss Tools GitHub organisation and teams. 
> If you log in and are forwarded to a /reporter/ URL, please contact 
> your GitHub org admins (e.g. Alexey or Fred) and ask them to review 
> your team memberships.
>
> Please note that you can still log in with the previous credentials. 
> But this account may be shut down by your org admins soon. Thus, 
> please switch over to GitHub authorization soon. Thank you.
>
> If you experience insane login delays (say, 10 seconds and more) 
> please let me know. There might be a few things to tweak.
>
> Have a great week,
> Marcel
>
> -- 
> Codetrails GmbH
> The knowledge transfer company
>
> Robert-Bosch-Str. 7, 64293 Darmstadt
> Phone: +49-6151-276-7092
> Mobile: +49-179-131-7721
> http://www.codetrails.com/
>
> Managing Director: Dr. Marcel Bruch
> Handelsregister: Darmstadt HRB 91940


> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160728/3388c747/attachment-0001.html 

From manderse at redhat.com  Thu Jul 28 07:03:14 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 28 Jul 2016 13:03:14 +0200
Subject: [jbosstools-dev] Firefox for Windows 64 bits
In-Reply-To: <da055f19-b9cf-e5c1-b781-dd059d212cb2@redhat.com>
References: <da055f19-b9cf-e5c1-b781-dd059d212cb2@redhat.com>
Message-ID: <C95EB91D-2683-48EA-A9CB-BE6EE76701CE@redhat.com>

On 11 Jul 2016, at 22:05, Mickael Istria wrote:

> Hi all,
>
> I was following some mozilla bugs related to Windows 64 bits support. 
> IIRC, those were interesting for JBoss Tools VPE or BrowserSim at some 
> point, however, I cannot remember the details. Anyway, some of those 
> bugs were marked as fixed recently, such as 
> https://bugzilla.mozilla.org/show_bug.cgi?id=482143#c15 .
>
> Not sure whether this is any helpful for us, but I thought it might be 
> worth sharing.

unless it includes xpcom api's which I doubt I don't think it helps us 
much.

/max
http://about.me/maxandersen

From mmalina at redhat.com  Thu Jul 28 07:32:26 2016
From: mmalina at redhat.com (Martin Malina)
Date: Thu, 28 Jul 2016 13:32:26 +0200
Subject: [jbosstools-dev] [aeri] Now supports github logins
In-Reply-To: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>
References: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>
Message-ID: <E8D91FF4-51A0-4C83-9F12-66D5C01B640D@redhat.com>

Hi,

Today I wanted to check the problem that was behind this JIRA:
https://issues.jboss.org/browse/JBIDE-22655 <https://issues.jboss.org/browse/JBIDE-22655>

So I clicked the link to https://redhat.ctrlflow.com/reviewers/#!/problems/571f44b6e4b0a5498327874b <https://redhat.ctrlflow.com/reviewers/#!/problems/571f44b6e4b0a5498327874b>
The page asked me to log in, so I logged in via github - I gave it permission to use my github account.
Then I tried again and I get:
You do not have access to this view: /problems/571f44b6e4b0a5498327874b

What do I need to see this? I am a member of the JBoss Tools github organization. I think this should be enough. Further, I am in the teams of devdoc and website.

BTW, https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/> gives this:
{"timestamp":1469705301444,"status":404,"error":"Not Found","message":"No message available","path":"/"}
And https://redhat.ctrlflow.com/reviewers/#!/ <https://redhat.ctrlflow.com/reviewers/#!/> gives this:
You do not have access to this view: /

Thanks,
Martin

--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic

Tel.: +420 532 294 265



> On 25. 7. 2016, at 13:02, Marcel Bruch <marcel.bruch at codetrails.com> wrote:
> 
> Greetings JBosstools Devs,
> 
> as discussed last week, we AERI now supports GitHub authentication and authorization in addition to the previous username-password based authentication. That means you can now log in with your GitHub account. Your roles (reviewer, admin, or just reporter) are determined by your membership in the JBoss Tools GitHub organisation and teams. If you log in and are forwarded to a /reporter/ URL, please contact your GitHub org admins (e.g. Alexey or Fred) and ask them to review your team memberships.
> 
> 
> Please note that you can still log in with the previous credentials. But this account may be shut down by your org admins soon. Thus, please switch over to GitHub authorization soon. Thank you.
> 
> 
> If you experience insane login delays (say, 10 seconds and more) please let me know. There might be a few things to tweak.
> 
> 
> Have a great week,
> Marcel
> 
> 
> -- 
> Codetrails GmbH
> The knowledge transfer company
> 
> Robert-Bosch-Str. 7, 64293 Darmstadt
> Phone: +49-6151-276-7092
> Mobile: +49-179-131-7721
> http://www.codetrails.com/ <http://www.codetrails.com/>
> 
> Managing Director: Dr. Marcel Bruch
> Handelsregister: Darmstadt HRB 91940
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160728/da691748/attachment.html 

From marcel.bruch at codetrails.com  Thu Jul 28 08:16:30 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Thu, 28 Jul 2016 14:16:30 +0200
Subject: [jbosstools-dev] [aeri] Now supports github logins
In-Reply-To: <E8D91FF4-51A0-4C83-9F12-66D5C01B640D@redhat.com>
References: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>
	<E8D91FF4-51A0-4C83-9F12-66D5C01B640D@redhat.com>
Message-ID: <6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>

Martin,

I just checked your roles. You only got Reporter rights assigned (the default) b/c your teams devdoc and website were not enabled for reviewer access by your org-admins.

Org-admins, is this an oversight?



> BTW, https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/> gives this:
> {"timestamp":1469705301444,"status":404,"error":"Not Found","message":"No message available","path":"/"}


Agreed, we should make this more meaningful again.

Marcel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160728/eb26e06d/attachment.html 

From manderse at redhat.com  Thu Jul 28 08:34:52 2016
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 28 Jul 2016 14:34:52 +0200
Subject: [jbosstools-dev] [aeri] Now supports github logins
In-Reply-To: <6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>
References: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>
	<E8D91FF4-51A0-4C83-9F12-66D5C01B640D@redhat.com>
	<6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>
Message-ID: <DF67A1DF-8F99-4AAB-8B44-5D23F2CFAC6F@redhat.com>

On 28 Jul 2016, at 14:16, Marcel Bruch wrote:

> Martin,
>
> I just checked your roles. You only got Reporter rights assigned (the 
> default) b/c your teams devdoc and website were not enabled for 
> reviewer access by your org-admins.

what does reviewer access mean in this context ?

Would it be sufficient to add a read-only group that have access to all 
repos and add everyone without push access to look ?

/max
>
> Org-admins, is this an oversight?
>
>> BTW, https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/> 
>> gives this:
>> {"timestamp":1469705301444,"status":404,"error":"Not 
>> Found","message":"No message available","path":"/"}
>
> Agreed, we should make this more meaningful again.
>
> Marcel


> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From marcel.bruch at codetrails.com  Thu Jul 28 08:52:42 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Thu, 28 Jul 2016 14:52:42 +0200
Subject: [jbosstools-dev] [aeri] Now supports github logins
In-Reply-To: <DF67A1DF-8F99-4AAB-8B44-5D23F2CFAC6F@redhat.com>
References: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>
	<E8D91FF4-51A0-4C83-9F12-66D5C01B640D@redhat.com>
	<6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>
	<DF67A1DF-8F99-4AAB-8B44-5D23F2CFAC6F@redhat.com>
Message-ID: <F73D5F9D-A2B6-4144-B29B-9E5FB7987E0D@codetrails.com>

Max,


> On 28 Jul 2016, at 14:34, Max Rydahl Andersen <manderse at redhat.com> wrote:
> 
> On 28 Jul 2016, at 14:16, Marcel Bruch wrote:
> 
>> Martin,
>> 
>> I just checked your roles. You only got Reporter rights assigned (the default) b/c your teams devdoc and website were not enabled for reviewer access by your org-admins.
> 
> what does reviewer access mean in this context ?


There are three roles: reporters, reviewers and org-admins. Reporters can only see public information of a problem while reviewers can edit data, create bugs etc. org-admins can administrate different aspects of the installation.


> Would it be sufficient to add a read-only group that have access to all repos and add everyone without push access to look ?

I?ve discussed several options with Fred and Alexey last week.

Just repeating them briefly:

1. If all organization members should get reviewer access, simply do no select any team. We?ll then check membership against the organization members.

2. It may make sense to create a group especially for accessing error reports (e.g. aeri). There simply add everyone who needs access to error reports.

3. If some teams should not / do not require access to error reports, simply do not select their teams in the oauth authorization panel - that?s what?s used ATM.


Whatever you decide, just update the configuration - or let me know.


Please note that you still can log in with the previously used username/password.

Marcel

> 
> /max
>> 
>> Org-admins, is this an oversight?
>> 
>>> BTW, https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/> gives this:
>>> {"timestamp":1469705301444,"status":404,"error":"Not Found","message":"No message available","path":"/"}
>> 
>> Agreed, we should make this more meaningful again.
>> 
>> Marcel
> 
> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> 
> /max
> http://about.me/maxandersen

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160728/b3c714b0/attachment-0001.html 

From mmalina at redhat.com  Thu Jul 28 09:00:51 2016
From: mmalina at redhat.com (Martin Malina)
Date: Thu, 28 Jul 2016 15:00:51 +0200
Subject: [jbosstools-dev] [aeri] Now supports github logins
In-Reply-To: <F73D5F9D-A2B6-4144-B29B-9E5FB7987E0D@codetrails.com>
References: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>
	<E8D91FF4-51A0-4C83-9F12-66D5C01B640D@redhat.com>
	<6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>
	<DF67A1DF-8F99-4AAB-8B44-5D23F2CFAC6F@redhat.com>
	<F73D5F9D-A2B6-4144-B29B-9E5FB7987E0D@codetrails.com>
Message-ID: <DB8176BE-5666-4301-AD1A-BE78666E6E6A@redhat.com>

Hi Marcel,

Thanks for the details. I don't think the solution is to add devdoc and website teams - there are still many in our QE team who are in neither of these. In my opinion, it would make sense to just give the reporter role to the whole jbosstools team on github. But as you say, this has to be decided by the org-admins - Alexey and Fred?

-Martin


> On 28. 7. 2016, at 14:52, Marcel Bruch <marcel.bruch at codetrails.com> wrote:
> 
> Max,
> 
> 
>> On 28 Jul 2016, at 14:34, Max Rydahl Andersen <manderse at redhat.com <mailto:manderse at redhat.com>> wrote:
>> 
>> On 28 Jul 2016, at 14:16, Marcel Bruch wrote:
>> 
>>> Martin,
>>> 
>>> I just checked your roles. You only got Reporter rights assigned (the default) b/c your teams devdoc and website were not enabled for reviewer access by your org-admins.
>> 
>> what does reviewer access mean in this context ?
> 
> 
> There are three roles: reporters, reviewers and org-admins. Reporters can only see public information of a problem while reviewers can edit data, create bugs etc. org-admins can administrate different aspects of the installation.
> 
> 
>> Would it be sufficient to add a read-only group that have access to all repos and add everyone without push access to look ?
> 
> I?ve discussed several options with Fred and Alexey last week.
> 
> Just repeating them briefly:
> 
> 1. If all organization members should get reviewer access, simply do no select any team. We?ll then check membership against the organization members.
> 
> 2. It may make sense to create a group especially for accessing error reports (e.g. aeri). There simply add everyone who needs access to error reports.
> 
> 3. If some teams should not / do not require access to error reports, simply do not select their teams in the oauth authorization panel - that?s what?s used ATM.
> 
> 
> Whatever you decide, just update the configuration - or let me know.
> 
> 
> Please note that you still can log in with the previously used username/password.
> 
> Marcel
> 
>> 
>> /max
>>> 
>>> Org-admins, is this an oversight?
>>> 
>>>> BTW, https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/> <https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/>> gives this:
>>>> {"timestamp":1469705301444,"status":404,"error":"Not Found","message":"No message available","path":"/"}
>>> 
>>> Agreed, we should make this more meaningful again.
>>> 
>>> Marcel
>> 
>> 
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> 
>> /max
>> http://about.me/maxandersen <http://about.me/maxandersen>
> 
> -- 
> Codetrails GmbH
> The knowledge transfer company
> 
> Robert-Bosch-Str. 7, 64293 Darmstadt
> Phone: +49-6151-276-7092
> Mobile: +49-179-131-7721
> http://www.codetrails.com/ <http://www.codetrails.com/>
> 
> Managing Director: Dr. Marcel Bruch
> Handelsregister: Darmstadt HRB 91940

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160728/2d1d13b6/attachment.html 

From marcel.bruch at codetrails.com  Thu Jul 28 09:32:15 2016
From: marcel.bruch at codetrails.com (Marcel Bruch)
Date: Thu, 28 Jul 2016 15:32:15 +0200
Subject: [jbosstools-dev] [aeri] Now supports github logins
In-Reply-To: <DB8176BE-5666-4301-AD1A-BE78666E6E6A@redhat.com>
References: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>
	<E8D91FF4-51A0-4C83-9F12-66D5C01B640D@redhat.com>
	<6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>
	<DF67A1DF-8F99-4AAB-8B44-5D23F2CFAC6F@redhat.com>
	<F73D5F9D-A2B6-4144-B29B-9E5FB7987E0D@codetrails.com>
	<DB8176BE-5666-4301-AD1A-BE78666E6E6A@redhat.com>
Message-ID: <39987F4E-70AC-4556-BBDD-F666BFE619F4@codetrails.com>


> On 28 Jul 2016, at 15:00, Martin Malina <mmalina at redhat.com> wrote:
> In my opinion, it would make sense to just give the reporter role to the whole jbosstools team on github. 

Just a minor correction:

We use different URL prefixes for reviewers and reporters. If a ?reporter" accesses a ?reviewer" url, he/she gets an "access denied?. That?s what you got when clicking on a JIRA link.

The different url prefixes were required in previous versions of AERI. We could, however, change the current system to use only one url and so that *all* reporters get a public/anonymized view of a problem. Please note the word anonymized. Problems may contain senstive information like email addresses, error messages etc. We thus cannot make them public available to everyone as-is.

However, at Eclipse we agreed on showing a anonymized view might be perfectly okay. So we could do the same here.

Max, Alexey, Fred,
what do you think?





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160728/30e82f61/attachment.html 

From nboldt at redhat.com  Thu Jul 28 21:41:51 2016
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 28 Jul 2016 21:41:51 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Unresolved issues for 4.4.1.AM2 /
 10.0.1.AM2 - please triage!
Message-ID: <CA+QcL11dikUSk90GdFi2Qg+AbLLwEOiuGbG=KfGGOJ9iQKYR+w@mail.gmail.com>

Please resolve these issues or move them to AM3:

jbosstools (18 issues):

https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212330876%22

devstudio (12 issues):

https://issues.jboss.org/issues/?jql=project%20%3D%20JBDS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%2212330879%22

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160728/be724970/attachment.html 

From alkazako at redhat.com  Fri Jul 29 20:30:41 2016
From: alkazako at redhat.com (Alexey Kazakov)
Date: Fri, 29 Jul 2016 20:30:41 -0400 (EDT)
Subject: [jbosstools-dev] [aeri] Now supports github logins
In-Reply-To: <39987F4E-70AC-4556-BBDD-F666BFE619F4@codetrails.com>
References: <D269ACC5-55E7-43A6-AAEA-3A4F32E52844@codetrails.com>
	<E8D91FF4-51A0-4C83-9F12-66D5C01B640D@redhat.com>
	<6E12081D-8954-4FB4-B6C1-7634EA97977C@codetrails.com>
	<DF67A1DF-8F99-4AAB-8B44-5D23F2CFAC6F@redhat.com>
	<F73D5F9D-A2B6-4144-B29B-9E5FB7987E0D@codetrails.com>
	<DB8176BE-5666-4301-AD1A-BE78666E6E6A@redhat.com>
	<39987F4E-70AC-4556-BBDD-F666BFE619F4@codetrails.com>
Message-ID: <EC078815-D4F0-4F05-8B02-77B38537134E@redhat.com>

I think we should grant reviewer access to all members of jbosstools org. For example QE may not have push access in github but we still want them be able to create issues based on aeri reports.

Regarding links in jira... Ideally the same link should work for everyone with optional GitHub authentication. If you do not login or you are not a jbosstools org member you see a public version of the report. Otherwise you see what you are supposed to see corresponding to your role. 
If it requires significant efforts to implement then can we post a few links for different roles with clear descriptions as a workaround?

WDYT?


> On Jul 28, 2016, at 6:32 AM, Marcel Bruch <marcel.bruch at codetrails.com> wrote:
> 
> 
>> On 28 Jul 2016, at 15:00, Martin Malina <mmalina at redhat.com> wrote:
>> In my opinion, it would make sense to just give the reporter role to the whole jbosstools team on github. 
> 
> Just a minor correction:
> 
> We use different URL prefixes for reviewers and reporters. If a ?reporter" accesses a ?reviewer" url, he/she gets an "access denied?. That?s what you got when clicking on a JIRA link.
> 
> The different url prefixes were required in previous versions of AERI. We could, however, change the current system to use only one url and so that *all* reporters get a public/anonymized view of a problem. Please note the word anonymized. Problems may contain senstive information like email addresses, error messages etc. We thus cannot make them public available to everyone as-is.
> 
> However, at Eclipse we agreed on showing a anonymized view might be perfectly okay. So we could do the same here.
> 
> Max, Alexey, Fred,
> what do you think?
> 
> 
> 
> 
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160729/1f38d22b/attachment-0001.html 

From aer-bot at ctrlflow.com  Sun Jul 31 23:30:00 2016
From: aer-bot at ctrlflow.com (Automated Error Reporting Bot)
Date: Mon, 1 Aug 2016 03:30:00 +0000 (UTC)
Subject: [jbosstools-dev] [aeri] Weekly JBoss Tools Error Reports Digest
Message-ID: <1926502847.1.1470022201016.JavaMail.ec2-user@aeri-rh>

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160801/97636584/attachment-0001.html