|
|
Sponsored Content
Top Forums
Programming
UNIX version standards
Post 35866 by Neo on Friday 9th of May 2003 09:15:04 PM
05-09-2003
Administrator
Version control and numbering is a matter of personal or organization preferences. For me, here is what I do for papers:
So, release numbering is often a matter of style and you know you have 'arrived' when others begin to understand your logic when releasing updates. Folks often tease me about my personal numbering style when writing documents.....it can be fun!!
Software release styles are similar and often have letters like a (alpha) and b (beta) to signify very early releases (similar to 0.01 or 0.10 in documents)..... however since software has the element of testing, there are lots of variations. With experience, you will develop your own style.
If you are developing, create your own style in your release numbering, but keep in mind that the first solid release is normally 1.0 not 3.0 or 6.0
- First rough draft or outline is version 0.01
- First draft is 0.10
- Each time I correct a nit or typo increment by 0.01
- When I feel it is about half way ready it is called 0.5
- Major changes increment by 0.10 or 0.05 (depending)
- When close to a final draft release it is at least 0.9 something
- Major first release after lots of reviews is 1.0
So, release numbering is often a matter of style and you know you have 'arrived' when others begin to understand your logic when releasing updates. Folks often tease me about my personal numbering style when writing documents.....it can be fun!!
Software release styles are similar and often have letters like a (alpha) and b (beta) to signify very early releases (similar to 0.01 or 0.10 in documents)..... however since software has the element of testing, there are lots of variations. With experience, you will develop your own style.
If you are developing, create your own style in your release numbering, but keep in mind that the first solid release is normally 1.0 not 3.0 or 6.0
|
|
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I pulled out my old 386 from the garage and dusted it off, and now i want to install unix on it. The 386 however only has a 104mb HD, and has NO cd rom support. Which if any version of unix would best suite this box? Is installing with floppies my only option? (8 Replies)
Discussion started by: nefarious
8 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am looking for some coding standards for Unix Shell Scripting. Can anyone help me out in this?
Regards,
Himanshu (3 Replies)
Discussion started by: himanshu_s
3 Replies
3. UNIX for Dummies Questions & Answers
Hullo Unix fans. Hoping one of you might be able to give me an indication here...
7 years ago, I was responsible for managing a windows 95 network with a unix server. Problem is I'll be buggered if I can recall what version of unix it was. Can anyone tell me what the standard version of the time... (2 Replies)
Discussion started by: k-lye
2 Replies
4. UNIX IEEE Std 1003.1-2001 (POSIX.1)
Click HERE to learn about The Single UNIX Specification, Version 3
Or:
Here is another link to the UNIX IEEE Standard, an Open Group Technical Standard, Issue 7
Keywords
UNIX® is a registered trademark of The Open Group (0 Replies)
Discussion started by: Neo
0 Replies
5. UNIX for Dummies Questions & Answers
Please post me a command, About how to find UNIX version on our machine.
i have tried
> WHICH Version
it didn't worked though. (2 Replies)
Discussion started by: Kzar
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I am thinking of buying a computer to learn UNIX. I am familiar with windows but not UNIX. Can someone tell me which version of UNIX should I get installed in my new PC? And how do I start learning UNIX? (4 Replies)
Discussion started by: hana
4 Replies
7. Shell Programming and Scripting
Would anyone have details of pre-existing Unix shell scripting standards. I've been asked to prepare a document outlining standards when writing korn shell scripts & don't really know where to start. Thanks. (6 Replies)
Discussion started by: janmolby
6 Replies
8. Solaris
i have a program writing in PRO C which currently running in unix version 8 tie with oracle 8i, but in the future company gonna migrate this OS to version 9.
Anything i have to prepare for my PRO C program to run in unix version 9? or anything would that impact my program couldn't run well?
what... (2 Replies)
Discussion started by: lsy
2 Replies
LEARN ABOUT OPENDARWIN
end
GET_END(3) Library Functions Manual GET_END(3) NAME
get_end, get_etext, get_edata - get values of UNIX link editor defined symbols SYNOPSIS
#include <mach-o/getsect.h> unsigned long get_end(); unsigned long get_etext(); unsigned long get_edata(); DESCRIPTION
These routines provide a stopgap measure to programs that use the UNIX link-editor defined symbols. Use of these routines is very strongly discouraged. The problem is that any program that is using UNIX link editor defined symbols (_end, _etext or _edata) is making assumptions that the program has the memory layout of a UNIX program. This is an incorrect assumption for a program built by the Mach-O link editor. The reason that these routines are provided is that if very minimal assumptions about the layout are used and the default format and memory layout of the Mach-O link editor is used to build the pro- gram, some things may work by using the values returned by these routines in place of the addresses of their UNIX link-editor defined sym- bols. So use at your own risk, and only if you know what your doing. Or better yet, convert the program to use the appropriate Mach or Mach-O functions. If you are trying to allocate memory use vm_allocate(2), if you are trying to find out about your address space use vm_region(2) and if you are trying to find out where your program is loaded use the dyld(3) functions. The values of the UNIX link-editor defined symbols _etext, _edata and _end are returned by the routines get_etext, get_edata, and get_end respectively. In a Mach-O file they have the following values: get_etext returns the first address after the (__TEXT,__text) section, note this my or may not be the only section in the __TEXT segment. get_edata returns the first address after the (__DATA,__data) section, note this my or may not be the last non-zero fill section in the __DATA segment. get_end returns the first address after the last segment in the executable, note a shared library may be loaded at this address. SEE ALSO
ld(1), dyld(3) Apple Computer, Inc. April 10, 1998 GET_END(3)