Bug 964455 - Node.js really shouldn't be in the "Java Development" section of the release notes
Node.js really shouldn't be in the "Java Development" section of the release ...
Status: CLOSED CURRENTRELEASE
Product: Fedora Documentation
Classification: Fedora
Component: release-notes (Show other bugs)
devel
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Pete Travis
Fedora Docs QA
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-18 15:40 EDT by T.C. Hollingsworth
Modified: 2013-05-18 17:25 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-05-18 16:53:18 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description T.C. Hollingsworth 2013-05-18 15:40:04 EDT
Node.js is currently listed in the "Java Development" section of the release notes, but JavaScript really has nothing to do with Java.  (You can thank Netscape's marketing department from the 90s for this wonderful confusion.)

Please consider moving it somewhere else.  Perhaps adding a new "Web Development" section is in order?  I'm sure I can find a few more things to add to such a section.  ;-)
Comment 1 Pete Travis 2013-05-18 16:53:18 EDT
I've added a new Web Development section, good idea! Node.js is there now, looking forward to ideas on what else to include :)


commit a02f50d61d233c943bc19f92b10f8851f8b9f312
Author: Pete Travis <immanetize@fedoraproject.org>
Date:   Sat May 18 14:51:39 2013 -0600

    Added a Web Development beat, and moved Node.js there. BZ964455
Comment 2 T.C. Hollingsworth 2013-05-18 17:25:41 EDT
Thanks!  Django 1.5 is the only thing I can think off to add right off the top of my head.

Give me a couple days and I'll look around for what's changed in F19 in this area and send a patch your way.  :-)

Note You need to log in before you can comment on or make changes to this bug.