Hi Malcolm,
Is there a process of monitoring development/build releases to discover if
> something significant has been fixed and should be deployed?
>
Development process can be monitored there: http://sedna.org/gitweb . All
stable releases are announced in this list. And we recommend to upgrade
after the announcement.
Unfortunately we are not able to actively develop and provide releases for
several branches. So, there are:
- Current stable version. It can be downloaded from our site. There can be
branch in our git repository like this:
http://sedna.org/gitweb/sedna.git/shortlog/refs/heads/v3.4.66-release-fixes,
which contains bug fixes. We don't announce commits of that branch. Rarely
(when there are critical bugs fixes and we are not ready for the next
version) we release bug fixed version of the current stable.
- Current development version. Can be downloaded there:
http://modis.ispras.ru/FTPContent/sedna/development/ . It may be not
stable. Build is created every night from the default git branch.
> Are there release notes with the items that were fixed or changed?
>
Usually, it's not possible. Most of the items are not registered in bug
tracker and very hard to reproduce or describe. Some of them are
reproducible on some private data provided by our users. So, there are
release notes for each stable version but usually they don't include list
of bug fixes. Just major changes and features.
Ivan Shcheklein,
Sedna Team
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
