To publish an official version of gvSIG Desktop in www.gvsig.org, the following steps must be followed:

1. Rename the binaries with the following nomenclature:

• gvSIG-[major-number]_[minor-number]_[revision-number]-[Build-Number]-[final_pilot_alpha_RCx_prot]-[operat_syst-3_letters]-[Processor_Type]-[JVM_description]-[JVM].[file_extension].
  For example: gvSIG-1_9-1245-final-lin-i586-withjre-j1_6.bin, gvSIG-1_9-1264-RC2-win-i586-j1_5.bin

2. Rename source code files (if it's a file) with the following nomenclature:

• gvSIG-[major-number]_[minor-number]_[revision-number]-[Build-Number]-[final_pilot_alpha_RCx_prot]-[operat_syst]-src.[file_extension].
  For example: gvSIG-1_9-1265-final-lin-src.zip

3. Upload binaries and source code to OSOR.eu:

• In the Forge of the project, being logged, go to Files (for example in gvSIG Desktop: http://forge.osor.eu/frs/?group_id=89)
• In every project, 2 Packages will be created: one for stable versions and another one for unstable ones, for example: gvsig-desktop (final ver.), gvsig-desktop (other ver.), gvsig-network-ext. (final v.), gvsig-mobile (final v.)...
• In the corresponding Package, the Release must be created. For example:
  For example: gvSIG 1.9 RC2
• Every file will be uploaded to this release.

4. Upload the manuals to OSOR.eu:

• They will be renamed like this: 
  • gvSIG-[major-number]_[minor-number]_[revision-number]-man-[manual_version]-[language_2_letters].[file_extension]
                For example: gvSIG-1_1-man-v1-en.pdf
• In the Forge of the project, being logged, go to Files (for example in gvSIG Desktop: http://forge.osor.eu/frs/?group_id=89): 
  • A "Releases" folder must be created (if it doesn't exist)
  • Inside that folder, a new folder called as the name of the version, with 2 figures (eg: 0.3) must be created
  • Inside that folder, a new folder called as the name of the version, with 3 figures (eg: 0.3.0) must be created
  • Manuals in pdf format will be uploaded to this last folder.