This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
From NetCAT member's email: Do you think it’s possible to have specs view on tribe page in the format of the “big huge table with all specs” instead of a list ? Make it more comfortable to show what is “deleted”.
The little confusion I have is that page with all specifications shows specification and versions in which it exists. But in tribe page, you assign exact version of specification to tribe. This table would help in term "ha, we can see we have old version of specification, maybe we could create a new one?"
Thks for opening the issue. I hope I can transmit my tought in an understandable manner :p. I think the enhancement is idea that comes with the "complex" lifecycle of test specification affected to maven tribe. Table is maybe not the good way too. 1) Current list is this one → Maven 7.3 → Maven OSGI 7.4 → Maven Support - Sanity 7.4 → Maven Support Test Specification 7.4 → [maven] Maven Support - Sanity 8.0 → [maven] Maven Support Test Specification 8.0 2) Assuming [maven] prefix was never used we may have that: → Maven 7.3 → Maven OSGI 7.4 → Maven Support - Sanity 8.0 → Maven Support Test Specification 8.0 But the Sanity are not needed cause it parts of test spec (with label feature) Maven is contained is test specs Maven OSGI was merge in Test Spec 3) So maybe the list may resume to: → Maven Support Test Specification 8.0 or alternativly with line with depreciated to incite not using it → Maven (depreciated) → Maven OSGI (depreciated) → Maven Support - Sanity (depreciated) → Maven Support Test Specification 8.0 and the idea of the "big huge table" is to have the previous information as a "timeframe" to see wich version it has been deprecated to browse former netcat ml or tribe ml. So maybe the point is more tagging a spec as depreciated (I saw delete button but :) Its sound scary ) Maybe to achieve this "ha, we can see we have old version of specification, maybe we could create a new one?" and also "hey do not continue on this spec"
Here's my 2 cents :) If specification should not be tested by tribe members, it (I think) shouldn't be in list of specifications for given tribe in the first place. This is basically your point 3). There is no reason to have "wrong" (obsoletes) specifications in your tribe. This causes the confusion about deprecated specification. Is specification deprecated ? Remove it from tribe and leave it as it is in Synergy (no reason to completely delete it). This basically says "hey do not continue on this spec" Then if tribe members don't know what to test, list of specifications in their tribes should help. Another solution would be: - tribe has specification Maven 7.3 - in Synergy, there is already newer spec Maven 7.4 => in tribe page, next to spec Maven 7.3 display warning information "newer specification available" with link to Maven 7.4 - it would not change it to 7.4, but let user to decide (and it would be up to tribe leader to update it)
(In reply to Vladimir Riha from comment #3) > Here's my 2 cents :) If specification should not be tested by tribe members, > it (I think) shouldn't be in list of specifications for given tribe in the > first place. This is basically your point 3). > > There is no reason to have "wrong" (obsoletes) specifications in your tribe. > This causes the confusion about deprecated specification. Is specification > deprecated ? Remove it from tribe and leave it as it is in Synergy (no > reason to completely delete it). This basically says "hey do not continue on > this spec" Agree. A leader can undbind spec from tribe. (I though it was for removing the specs) > Then if tribe members don't know what to test, list of specifications in > their tribes should help. > Agree > Another solution would be: > - tribe has specification Maven 7.3 > - in Synergy, there is already newer spec Maven 7.4 > => in tribe page, next to spec Maven 7.3 display warning information "newer > specification available" with link to Maven 7.4 - it would not change it to > 7.4, but let user to decide (and it would be up to tribe leader to update it) Yep will help also leader or tribe member to report. Something remains, MavenOSGI in no more in maven tribe, (it's decided that it's merged with MavenTestSpec and not likely to be retested: human decision, not in synergy yet) How to tell a "free runner" looking at synergy for assigniign a test or a tribe member affecting spec this is a "wrong" spec do not use it
(In reply to skygo from comment #4) > Agree. A leader can undbind spec from tribe. (I though it was for removing > the specs) If you press Delete on specification page, it removes specification from Synergy "completely". If you press Remove on edit tribe page [1] it only removes specification from list of specifications in this tribe > How to tell a "free runner" looking at synergy for assigniign a test or a > tribe member affecting spec this is a "wrong" spec do not use it Well tribe member should have a look at tribe page and follow list of specifications, anything he does "extra" is up to him, his responsibility. You can edit tribe description and add any HTML code (links) you want. Free runner can only create assignment using [2] where he has to filter specifications by version. So if he selects 8.0, Maven OSGI is not offered. [1] http://services.netbeans.org/synergy/client/app/#/tribe/34/edit [2] http://services.netbeans.org/synergy/client/app/#/assignment/create/run/5
Ok so the idea is if you want to
sorry for "partial comment;" was asked for password and all message was not saved. Using html in description make the trick. Cloning a test specification to current version make the spec available. (I think that what I did for creating [maven] prefixed one) Editing maybe the way. Do you think I can create a wiki page to compile information on synergy ? Maybe crossing with others issues and tribe and netbeans netcat
I believe it should be up to someone to keep the list of specifications in tribe up to date. However, of course, the responsible user might not always be aware of new versions of specification or he/she might not always update the list before anyone look into it and create a assignment for himself/herself. I would propose to improve the page as it looks on attached draft. What do you think? (In reply to skygo from comment #7) > Do you think I can create a wiki page to compile information on synergy ? > Maybe crossing with others issues and tribe and netbeans netcat I don't know if there is some restrictions but that could be useful I guess (best would be to have it in Synergy of course, but it is not possible now). Adding Jirka to cc as he probably knows better. Jirko, what do you think?
Created attachment 144072 [details] draft of improved tribe page
I think the draft sounds good, it allows tribe review with help of synergy to check for newer version. Just to be sure: is the automatic tribe assignement in this case just assign the netbeans 8 specs ?
(In reply to Vladimir Riha from comment #8) > (In reply to skygo from comment #7) > > Do you think I can create a wiki page to compile information on synergy ? > > Maybe crossing with others issues and tribe and netbeans netcat > > I don't know if there is some restrictions but that could be useful I guess > (best would be to have it in Synergy of course, but it is not possible now). > Adding Jirka to cc as he probably knows better. Jirko, what do you think? I think it depends on what Eric wants to include on that page and how fast the information becomes obsolete. Isn't it still too early to document Synergy? If you are Eric willing to compile the page and then keep it updated I agree.
(In reply to skygo from comment #10) > Just to be sure: is the automatic tribe assignement in this case just assign > the netbeans 8 specs ? This is only filter on existing list of specifications. When you, as a tribe leader, create assignments for members of your tribe, you selecting specification from list of specifications that belongs to tribe. So you will see all. But since I'm going to improve the tribe page, I might as well do the same for create tribe assignment page. Once you select specification that has newer version, warning message will come up.
> > I think it depends on what Eric wants to include on that page and how fast > the information becomes obsolete. Isn't it still too early to document > Synergy? If you are Eric willing to compile the page and then keep it > updated I agree. Was willing to add something like NetCAT Synergy or a page near netcat forrest to compile by role and task (not feature as first class) Admin (is not part of NetCAT member job) Tribe leader tribe managment, spec managment Tribe member Free runner with assignement spec edition My feeling is more to show netcat member perspective (so maybe netbeans qa team may adjust community feeling) Maybe anticipating a future embedded help in synergy.
In case Tribe has reference to older specification, warning message is displayed next to the specification, see [1] for instance. Relation old/new specification is found from "Similar specifications" (list of similar specs is on each specification page - e.g. [2]). The same is displayed when tribe leader is creating assignments for tribe. All changes will be live in 30 minutes (until then it will show false warning) [1] http://services.netbeans.org/synergy/client/app/#/tribe/38/view [2] http://services.netbeans.org/synergy/client/app/#/specification/113/v/2
Sorry reopening, because I have seen a little glitch in maven tribe Maven OSGI indicate newer version available but it's Maven OSGI 6.9. [1] http://services.netbeans.org/synergy/client/app/#/specification/264
Nice catch, thank you. Should be OK now