Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] Che6 related bugs/issues


On Tue, Mar 19, 2019 at 12:15 PM Gennady Azarenkov <gazarenk@xxxxxxxxxx> wrote:


On Tue, Mar 19, 2019 at 11:21 AM Sergii Kabashniuk <skabashn@xxxxxxxxxx> wrote:


On Mon, Mar 18, 2019 at 7:24 PM Vladyslav Zhukovskyi <vzhukovs@xxxxxxxxxx> wrote:
Do we plan to move GWT IDE into separated repo?
 
I would say "No" at this moment. GWT IDE in the sidecar is a nice concept, however, it's working only under certain conditions. 
Largest prerequisite is that Workspace/Project API has to be on workspace master in the state that we have at 6.x era.
I believe that would be changed soon.

If so, then I propose to sort the issues and move an actual issues into repo with GWT IDE. I don’t think that closing issue just because it become stale is a good decision. Maybe there are an enthusiastic people (community) that will be support GWT IDE, take this into account.
 
If you or you know such people or they can reach me I with glad will help to coordinate work in a new repo. 

+1 on removing GWT IDE to standalone repo, reviewing and moving or deleting related issues and refactoring ide. Count on me with this.
+1 from my side  

From another hand, people who think that small cleanup with issues is needed already raised a hand and we should honor their opinion too. 
 
I do NOT think it harm someone else. In this case GWT IDE issues will disappear from Che repo anyway. 
 
I can propose to wait, let's say a week if someone will raise an initiative to support GWT IDE in sidecar compatible to Che7 direction we will 
talk about alternatives otherwise, I would say we should do some cleanup in code and issues anyway.

VLADYSLAV ZHUKOVSKYI

SOFTWARE ENGINEER, ORACLE CERTIFIED ASSOCIATE, JAVA SE 8

vzhukovs@xxxxxxxxxx    M: 380634355319    

TRIED. TESTED. TRUSTED.



18 марта 2019 г., в 17:40, Yevhen Ivantsov <yivantso@xxxxxxxxxx> написал(а):

As suggested, interested parties can reopen an issue, I do not see any problems with that. I see no danger for any downstream problems here.

On Mon, Mar 18, 2019 at 5:38 PM Dmytro Nochevnov <dnochevn@xxxxxxxxxx> wrote:
Hello everyone.

Please, before closing all the Che 6 issues, take into account that there are downstream projects which would still depend on Che 6 during some period of time, and so could require bug-fix releases of Che 6, like 6.19.2.

On Mon, Mar 18, 2019 at 5:28 PM Oleksandr Garagatyi <ogaragat@xxxxxxxxxx> wrote:
+1 
If somebody thinks an issue should not be closed they can reopen the issue. 
Also if somebody is interested in an issue that is gonna to be closed they can discover that there is new shiny version of Che they missed that might be not suffering from a bug/feature request. 


On Mon, Mar 18, 2019 at 4:58 PM Sergii Kabashniuk <skabashn@xxxxxxxxxx> wrote:
Hello, devs.
As we are moving towards to Che7 I have one question in mind.
Does someone see a reason why don't we close Che6 related bugs/issues?
Issues related to GWT IDE and issues related to Che6 related topics on the dashboard.

My motivation:
- Community: More clarity that issue is "stale" and more likely nobody will work on that.
- Newcomer: if they want to contribute on some issue will not be misled with an old version task.
- Committers: less job by tracking all issues.

Thoughts?


--
Sergii Kabashniuk

Principal Software Engineer, DevTools 
Red Hat Ukraine
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev


--
OLEKSANDR GARAGATYI

SENIOR SOFTWARE ENGINEER

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev


--
With best regards,
Dmytro Nochevnov
Codenvy Associate
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev


--
EUGENE IVANTSOV

eivantsov@xxxxxxxxxx   

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev


--

Sergii Kabashniuk

Principal Software Engineer, DevTools 

Red Hat Ukraine

skabashniuk@xxxxxxxxxx    

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev


--

VITALII PARFONOV

PRINCIPAL SOFTWARE ENGINEER, CHE PROJECT

Red Hat EMEA

Ukraine

M: VPARFONO@xxxxxxxxxx    

Back to the top