Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cFE 6.5 Documentation Updates #167

Closed
skliper opened this issue Sep 30, 2019 · 30 comments
Closed

cFE 6.5 Documentation Updates #167

skliper opened this issue Sep 30, 2019 · 30 comments
Milestone

Comments

@skliper
Copy link
Contributor

skliper commented Sep 30, 2019

This ticket will be used for all cFE 6.5 documentation updates including the VDD. A listing of the needed documentation updates will be added to this ticket as tickets, requiring code updates, are reviewed and determined there is an associated documentation change.

@skliper skliper added this to the 6.5.0 milestone Sep 30, 2019
@skliper skliper self-assigned this Sep 30, 2019
@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Imported from trac issue 136. Created by sstrege on 2016-02-15T11:46:30, last modified: 2019-03-05T14:57:55

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-02-15 11:50:18:

Ticket #156 - JSC: change uint8 to char for strings in interface structures. Requires updates to the cFE readme file and doxygen user's guide to alert user's on the cFE's dependency on platforms supporting 8-bit unsigned "char" types. Discussed at 2-10-16 CCB.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2016-02-16 13:23:48:

cfe-next is cfe 6.5

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-03-21 13:36:09:

Doxygen and cFE readme have been updated in response to Ticket #156 documentation request. Changeset [changeset:c82b3d] is ready for CCB review.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2016-03-21 14:47:09:

Interesting -- do we really have code that breaks if "char" is signed?

If so, then we should probably also have a bit of code that verifies
that "char" is unsigned on the current target ...

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-03-22 15:37:15:

The following commit: [changeset:8e13ca6] removes the term "unsigned" as agreed upon at the 3-22-16 CCB

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by jphickey on 2016-03-22 18:13:55:

This has added into the ic-2016-03-22 merge

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2016-03-30 15:12:30:

development now includes ic-2016-03-22 merge.

IIRC, the decision was to keep this ticket open
pending further updates (so not closing it just yet).

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-04-26 10:04:59:

HowToRunCFEUnitTests.txt updates are attached and can be viewed in the following commit: [changeset:b88e451]. Ready for CCB review.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2016-04-26 11:27:29:

recommend accept.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2016-04-29 12:47:47:

Included as part of the ic-2016-04-26 merge.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-05-03 11:03:52:

Reopening this ticket for other documentation updates i.e. VDD and CMake deployment guide.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-05-18 18:43:01:

Built doxygen HTML files with latest cFE 6.5.0 in development. New files are under commit: [changeset:9425a79]

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by stashakk on 2016-05-23 10:10:46:

I have a few problems with the Tested platforms section

  1. How can x86-32 be running 64-bit CentOS? Was this meant to be x86-64, 32-bit CentOS, or some PAE?
  2. What version of RedHat Linux?
  3. Why if we list the distro version of a few linux options then list x86-64 Linux? Does this mean all x86-64 distros?
  4. What versions of RTEMS or other OS?

If the OSAL is working correctly then it should not matter what platform that cFE was tested on because the point of the OSAL is to abstract way the OS that cFE is on, correct? I am figuring that the platforms are being listed for completeness but it seems counter intuitive.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sduran on 2016-05-23 17:14:39:

VDD looks good, recommend accept.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2016-05-24 13:32:44:

We are fortunate that 64-bit X86 Linux systems are still capable
of running 32-bit X86 binaries (as long as you install the right
packags; gcc-multilib seems to be sufficient). So yes, we are
testing our 32-bit X86 binaries on 64-bit X86 Linux machines.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2016-05-24 13:39:37:

Side note: in the case of our Bamboo builds, I did
explicitly install 32-bit Debian Jessie, to assure
that the build was not mistakenly turning out any
64-bit binaries (for the test target).

{{{
glimes@cfsbt32:$ uname -a
Linux cfsbt32.pollux.local 3.16.0-4-686-pae #32 SMP Debian 3.16.7-ckt9-2 (2015-04-13) i686 GNU/Linux
glimes@cfsbt32:
$
}}}

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-05-26 15:45:52:

See attachment "cFE650-VDD-CMonacoComments.pdf" for details on "minor things" found.

From: Monaco, Chris [mailto:[email protected]]
Sent: Tuesday, May 24, 2016 1:35 PM
To: Strege, Susanne L. (GSFC-5820) [email protected]
Cc: Monaco, Chris [email protected]
Subject: RE: [cfs-community-ccb] cFE 6.5.0 VDD - Initial Revision Open for CCB Review

Susie,

Only minor things.

Like the discussion about having a table of tested platforms with columns for each platform/software etc attribute.

Everything else looks fine… “approve”

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by stashakk on 2016-06-03 08:26:06:

Looks good.

Approved

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by jphickey on 2016-06-03 09:25:07:

Approve, with one very minor suggestion. In section 1.1 it lists "Added support for Electronic Data Sheets (EDS)" as a bullet item. This could be confusing since, although some of the changes in this release will make the code play nicer with generated header files, it does not support EDS and does not actually contain any of the EDS functionality.

I recommend deleting that bullet item, to avoid confusion.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-06-03 13:52:04:

Agreed, the newly attached updated VDD has the "Added support for Electronic Data Sheets (EDS)" bullet removed.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2016-06-03 14:10:33:

approved.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by jphickey on 2016-06-03 14:14:07:

Approve.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sduran on 2016-06-06 10:32:03:

Approve

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by dthames on 2016-06-06 17:31:23:

Approve

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-06-06 17:35:43:

Approving on behalf of Chris Monaco

Approval received via email

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-06-09 18:13:32:

Updated release notes can be found in commit [changeset:41945d3]

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2016-06-09 20:02:43:

Updated release notes to include information on compiler issues with the SC and HS applications. Additional commit [changeset:d828235]

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2016-06-14 15:09:56:

CFE 6.5.0 master branch has been sealed.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by jhageman on 2019-03-05 14:57:55:

Milestone renamed

@skliper skliper closed this as completed Sep 30, 2019
@skliper skliper removed their assignment Sep 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant