| Do we plan to move GWT IDE into separated repo?
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.
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. 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.
+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.
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
--
_______________________________________________ che-dev mailing list che-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev
|
