Message-ID: <1037551066.4533.1414150993505.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4532_1493857849.1414150993504" ------=_Part_4532_1493857849.1414150993504 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Note: Article currently under development
This article describes the steps to follow when building a mapbuilder-li= b release.
Notify developers that you are about to make a release and reque= st users for the LICENSE file.
At least 24 hours before building a release. This should allow them to e= nsure their fixes are in the code base. The email should also request a lis= t of new developers to add to the LICENSE file.
Here is a sample email.
Update the LICENSE file
Once people respond, upda= te the LICENSE file and commit to subversion.
Check all code back into Subversion
If you have not done so already, check all the code you have been editin= g into Subversion.
Update the CHANGES file
Update and commit CHANGES file with updates between the last release and= this one. These files should be in the base directory.
These can be found in the Project Plan
Commit CHANGES back into SVN
Set release version in properties.xml
in mapbuild= er/default.properties set the app.version value to the current release. Thi= s should look something like:
Commit the new build.xml back into SVN.
Get latest updates= from SVN
Ensure you have the latest files from SVN.
Tag the release
Tag the files that should be in the release. (Usually, not all files in = SVN are included in a release).
The <tag> should be of the form: mapbuilder-lib-[number]-[status]<= /p>
Export the release
This may be performed as the anonymous SVN user.
Install JSDoc dependancies
JSDoc builds javadoc l= ike documentation for all the Mapbuilder classes and it requires a Perl mod= ule not available by default. You will know you don't have it installed bec= ause when you try to build the distribution (next step) you will see an err= or in your output which looks something like: "Can't locate HTML/Templ= ate.pm in @INC".
In windows install ActivePerl.
In linux do the following (as described at http://jsdoc.so= urceforge.net/ ).
Then provide default answers to all questions. (Yes, it is a pain).
Build the distribution
Test the release
Run through the manual testing p= rocess described at Testing.
Get signoff from mapbuilder developers
Copy the r= elease to a tmp directory (where?) and give mapbuilder-devel 24 hours to ch= eck. Ask developers to check against the criteria at Testing.
Navigate to the uploaded mapbuilder-lib-*.zip and mark it as the default download by clicking "Select All" in= the "view details" (i-button).
Update release tags in JIRA
Set the release date for the current release. Any issues which were tagg= ed to be fixed in this release should be moved to the next release.
Notify OSGeo as per https://www.osgeo.org/= content/news/submit_news.html. For significant announcements, the follo= wing URL might also be relevant: http://wik= i.osgeo.org/index.php/Press_Release_Process