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.
When I click on target Milestone link on any issue, I get to "No Target Milestones defined", which is obviously not true Expect to have a clear doc on what is what: TBD - not evaluated yet future - don't know, have more important thing to do There was a discussion on nbdev, see it for exact formulations
blocking 27338, because some developers are not aware, which confuses users, that have read that TBD = I haven't looke at this issue yet (me is such a user)
blocking 27338, because some developers are not aware, which confuses users (e.g., me), that have read that TBD = I haven't looked at this issue yet, that's why it's not scheduled, please wait
To summarise : Need to add content to http://www.netbeans.org/issues/notargetmilestone.html describing "Target Milestone" options. AFAIK this will have to be done by Collab, but before I request they do this I need the exact content we want on that page. Assigning to Jan, IZ admin and guru; Jan do you know what our TMs are, and can you whip up some txt for that page ? BTW is it correct that we will need to ask Collab to edit that page, or can IZ admins do it ? (I am a bit suspicious of the "notargetmilestone.html" filename - why the "no" ?)
Target Milestone specifies the earliest version the issue is or is planned to be fixed in. For most modules, target milestone values correspond to the NetBeans IDE releases. Special milestone values may be defined for modules that are not aligned with IDE versions. Target Milestones are typically set by developers. Users are not expected to set the milestone values themselves. For open issues, Target Milestone specifies the version in which the issue is planned to be resolved. For resolved issues, Target Milestone specifies the earliest version that includes the fix/resolution of the issue. Target Milestones are closely related to the Version field. Both Version and Target Milestone values outline the issue lifetime. Therefore, Target Milestone should never be set to a value that would precede the Version. ----------- Hope this can be used for the description. Feel free to edit it as needed.
Ah, forgot to add... --------------- Special Target Milestone values -- 'TBD' and 'future' -- can be assigned to open issues: TBD - is automatically set for all newly reported issues. It technically means "the issue hasn't been evaluated yet". future - can be used if the developer accepts the issue, but doesn't plan to fix it in the upcoming planned releases. Version-specific target milestones should be used otherwise.
Many thanks Jan. Collab - the "Target Milestone" link above points to a page with some "no target milestones defined" txt. This is not correct. I am attaching some HMTL that describes NBs use of target milestones, could you update the page with that txt (it should replace existing txt) ? Thanks.
Created attachment 7462 [details] proposed content for Target Milestones description page
Looking into this issue.
Jack, It looks like you should be able to browse to http://www.netbeans.org/source/browse/look/www/bugzilla/notargetmilestone.html in order to make these changes. Let me know if you have any problems. Thanks, Kristen
Hmm; this does look promising, but the changes I made and commited do not show up as expected. Is there a "reload" or propagation that needs to happen ? At http://www.netbeans.org/source/browse/look/www/bugzilla/not argetmilestone.html you can see my committed changes, but at http://www.netbeans.org/issues/notargetmilestone.html the changes do not show up.
Jack, I'm not sure how this works with the customizations that were made to the netbeans ui. Logged PCN11871 for assistance. Thanks, Kristen
Just FYI - same problem with /look/www/bugzilla/bug_status.html - I have made some edits and commited them, but they do not show up on the live site. Any updates ?
Hi Jack, I updated the internal issue with the additional filename and requested an update. Thanks, Kristen
The override for this file does not appear to be set up. Confirming requirements with engineering and whether or not it is the same issue for bug_status.html. Thanks, Kristen
We've confirmed that bug_status.html does not have the override in place either. Requesting more information on which files Netbeans should have available for edits and action plan moving forward. Thanks, Kristen
Hi Jack, It does not appear that these 2 files were included in the files that were opened up to sun for edits. This has been included in the list of upgrade issues by the engineering team. Sorry for the delay. Thanks, Kristen
OK; what does that mean in terms of seeing our requested changes pushed live ? Obviously long term we'd like to be able to edit those files freely via CVS and look/, but short-term we need the edits published.
Hi Jack, Update: We're checking with engineering to see where the edits fit into their timeline. Plan: Have an update for this issue by Monday. Thanks, Kristen
Engineering has made these changes. Target Milestone now reads: Target Milestone specifies the earliest version the issue is or is planned to be fixed in. For most modules, target milestone values correspond to the NetBeans IDE releases. Special milestone values may be defined for modules that are not aligned with IDE versions. Target Milestones are typically set by developers. Users are not expected to set the milestone values themselves. For open issues, Target Milestone specifies the version in which the issue is planned to be resolved. For resolved issues, Target Milestone specifies the earliest version that includes the fix/resolution of the issue. Target Milestones are closely related to the Version field. Both Version and Target Milestone values outline the issue lifetime. Therefore, Target Milestone should never be set to a value that would precede the Version. Please verify. Thanks, Kristen
Verified and Closed, thank you
Short term problem sovled. thanks. Don't forget the real problem - changes to these files in CVS do not propagate to the live site. Updating Summary field and reopening to track the root problem.
Update: The root cause of this issue is on the upgrade task list. Please log separate issues if edits to files are not appearing live and we will have engineering assist until this is corrected. Action Plan: Engineering will investigate as part of the upgrade. Next update: Whne support receives an update to CollabNet issue PCN 11871. Thanks, Kristen
Update: our engineer found that those files 'can't be changed without an inst override'. This would answer why changes made in CVS would not show up in site. Action plan: I asked template engineers how we could make those files available for users to change without CollabNet's assistance. Next update: within one week with the an answer.
Update: Our template engineer explained that the files mentioned in this issue will be among the standard help files in standard location after the upgrade. Thus when the update is made in these files through CVS by user they will be seen on site without any further intervention by CollabNet's template engineer. Action plan: will monitor internal issue for any update by our template engineer. Will keep this issue open till upgrade will confirm the validity of the statement above. Next update: within two weeks.
update: no change in internal issue action plan: did not change: will close this issue out after upgrade after confirmation from client
Yosh, the current procedure that Collab have been following in general is to close any issue fixed in an upcoming release. It should then be verified when that release rolls out. Personally I don't think that is a good policy (closing before the user has the fix), but maybe consistent bad policy is better than inconsistent :-) I mean to be consistent this issue should probably be closed, if it is fixed in Truckee. Just my 2c.
Thanks Jack. Your're right. We should follow the consistent policy. Closing this and will revisit after the upgrade to verify.
Updating whiteboard...
Changing Target Milestone to CEE 2.6.2
Jack, This has already been fixed in 2.6.2. Please verify the same from your end. Regards, Kavitha Support Operations
No, I don't see this fixed at all. The content of : look/www/bugzilla/notargetmilesonte.html do not match what is shown when I click on "Target Milestone" in IZ, ie : http://www.netbeans.org/scdocs/notargetmilestone.html
Hi Jack We will work with our internal team regarding this and will get back as soon as possible. Thanks, Pritha Support Operations.
The location for making changes via CVS which would be reflected across the site especially with Help Docs is /look/www/branding/help-docs/ /look/www/branding/help-docs/notargetmilestone.html Closing this issue as Fixed .
I've copied the contents of look/www/bugzilla/notargetmilesonte.html to /look/www/branding/help-docs/notargetmilestone.html and commited, and it seems to have worked, the changes went live. Not sure when or why the location of that override moved, and I'm not sure we were notified. In any case, it is quite confusing to have both of them still in CVS. I'd suggest removing the one that doesn't actually do anything to save future confusion.