Home
My Page
Projects
deegree

[#6294] Regular pre-release builds/quality assurance

Date:
2012-02-12 17:12
Priority:
3
State:
Open
Submitted by:
Markus Schneider (mschneider)
Assigned to:
Johannes Wilden (jwilden)
Summary:
Regular pre-release builds/quality assurance

Detailed description
The last announced deegree 3.2 pre-release is pre2 from December, 6th [1].



While I know that there has been a another release in the meantime (3.2-pre3), I would like to push for a decision/clarification on the following things:



- Do we want to have a regular pre-release cycle (e.g. every 2 weeks)? If yes, how do we ensure that we cling to it?

- How do we ensure that all details a build are covered (building, announce on the download page, demo servers)?



[1] http://wiki.deegree.org/deegreeWiki/DownloadPage

Followup

Message
Date: 2012-11-02 12:28
Sender: Johannes Wilden

I think the way to go will be to create a process which includes maven and jenkins/hudson.


These tolls provide everything you need to create a release and deploy everything anywhere you want.

I will prepare an example process for the deegree community space as a starting point for discussion about this topic.
Date: 2012-06-12 13:46
Sender: Johannes Wilden

Also:

To improve quality of deployed services on the demo server, some automated tests to check completeness and correctness of deployment would be helpful. Can be achieved by defining request/response pairs and respective processing. This is basically an issue for release management.
Date: 2012-05-18 14:47
Sender: Markus Schneider

Please prepare an update on the status of this item for the next TMC meeting (scheduled for 29-05-2012).
Date: 2012-03-06 14:30
Sender: Torsten Friebe

A 2 weeks release cycle means that all steps need to be automated including build, deployment, update website, demo server etc
Date: 2012-02-15 11:08
Sender: Johannes Wilden

Work in progress:

http://wiki.deegree.org/deegreeWiki/deegree3/BuildScheduleAndProcess
Date: 2012-02-14 20:25
Sender: Markus Schneider

As discussed [1], the following things need to be done:

- Create a deegree wiki page to describe build schedule and process
- Include a checklist of things to do (update wiki, announce mail, update roadmap, install & test demo servers, make workspaces available,...)

[1] http://wiki.deegree.org/deegreeWiki/TmcMeeting/TmcMeeting20120214

Attached Files:

Changes:

No Changes Have Been Made to This Item


This site is hosted by Intevation GmbH