![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| High Level Programming Post questions about C, C++, Java, SQL, and other programming languages here. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| OMG CEP Standards event: what standards? | iBot | Complex Event Processing RSS News | 0 | 03-13-2008 10:40 PM |
| Unix Shell Scripting Standards | janmolby | Shell Programming and Scripting | 6 | 03-29-2007 02:22 PM |
| Which version of UNIX I'm using? | Nomaad | UNIX for Dummies Questions & Answers | 1 | 10-03-2006 02:12 PM |
| Link to the Open Group (UNIX Standards) | Neo | UNIX IEEE Std 1003.1-2001 (POSIX.1) | 0 | 08-18-2002 03:40 PM |
| Unix Coding Standards | himanshu_s | UNIX for Dummies Questions & Answers | 3 | 12-06-2001 01:34 PM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
UNIX version standards
I'm new to UNIX programming. I'm used to starting my program's versions at 1.0, but I look at all the UNIX programs out there and see things like 0.000.1 or 3.3.000 and I'm wondering what these things really mean. Do people just type anything they feel in there? Are things in pre-release development kept at 0-dot-whatever?
Any input would be appreciated. Thanks, Scott |
| Forum Sponsor | ||
|
|
|
#2
|
||||
|
||||
|
There is no real industry wide standard here. I can't speak to other people's customs. But typically, version 1.0 would the version that I would assign to my program when it is first ready for use. For complex programs this will imply that versions 0.0, 0.1, 0.2, etc may exist. But with simpler programs, I may indeed go straight to version 1.0.
Local standards are really more important. If you're participating in any sort of group effort (commercial or freeware), you probably should conform to whatever standard is already in place. Also if you're using RCS or SCCS or something like that, your versioning scheme should work well with the package you use. |
|
#3
|
||||
|
||||
|
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 |
|
#4
|
||||
|
||||
|
Quote:
|
|
#5
|
|||
|
|||
|
also the linux kernel's version numbers are very informative... you can know what is a stable kernel and what is still experimental by the version number. check out kernel.org for more information.
|
|
#6
|
|||
|
|||
|
hello
well,
its rely very hard to understand this website, have no idea why they put all this rubbish. and have no information about new unix versions. |
|
#7
|
||||
|
||||
|
Don't get frustrated so quickly.. there's plenty of information on new versions.. check your other post.
|
||||
| Google The UNIX and Linux Forums |