| Anyway, we have 1075 opened issues that consist of che6 and che7 related things. We have to spend some time to sort them, unfortunately. What I propose at this moment, is to create a label, let's say «prepared-to-move» or smth else. After that, look through the issues and mark che6 specific issues with this label. When we’ll be ready to move the codebase to new repository, we can move marked che6 issues. This process can be automated via GitHub API.
Let's back to the original question which is what to do with Che6 specific issues. There are two options: - to remove all of them - to move them along with codebase out of Che repo
As said, myself and several other are OK to to spend time for the second option. We are not a monorepo project anymore, there are 34 eclipse/che-* repos [1] (with different level of activity) already So I see no reason to invent something else, which does NOT help for initial issue anyway.
+1 to avoid moving code into a separate repo. If we find people who would be willing to maintain GWT IDE for Che 7 we could move code from 6.19.x branch only then.
Rather than refactoring things out of the Che repo to a new standalone one, why not just leave them in the 6.19.x branch and remove them from master?
Do we really want the overhead of maintaining a different repo? In theory if you move the code, you would also want to move the Che 6.x issues over there too.
Nick
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.
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
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
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
--
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
--
Nick Boldt Principal Software Engineer, RHCSA Productization Lead :: JBoss Tools & Dev Studio IM: @nickboldt / @nboldt / http://nick.divbyzero.com
“The Only Thing That Is Constant Is Change” - Heraclitus
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
_______________________________________________ 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
|
