Hello Ivan, Thank you for sharing the GIT link. Seeing the list helps.
The summaries are well written. Patching: The problem is that developers/admin needs to understand the details so they can make decisions on deploying patches. For example, the following bug fix from 2 days ago seems important: "Some indecies bugfixes. Indexing on text nodes working" The corresponding test says: "Sedna 3.5.161 crashes. Do not pull until committing source code!" Mailing list, bug tracker & git: I see the disconnect between bug tracking & git, and I see how some of the disconnection can occur. Example: dateTimes subtraction a. I first went to the mailing list to see if 'dateTimes subtraction' was an issue or just me. b. It was an issue and the Sedna team took the lead to resolve. (Thanks!) c. The dateTimes subtraction issue never appeared in bug tracking. ( :-( ) What should have occurred is the Sedna team saying: Yes, dateTimes subtraction is an issue, please go to the bug tracker & enter the issue. Requiring issues to be inserted into bug tracking is a normal occurrence for me with other FOSS projects. The release notes should be improved if developers are forced to use the bug tracker, marking which version the bug was discovered, and the Sedna team marking which version the issue is fixed. The down side is that the SF bug tracker may not be practical. (One of the reasons I dislike using SF). github: Has there been any consideration about migrating the source code to github? I like the overall experience of github over SF, and github may do a better job of bug tracking and release notes. Thanks, Malcolm -----Original Message----- From: Ivan Shcheklein [mailto:shchekl...@gmail.com] Sent: Sunday, February 19, 2012 8:39 AM To: Malcolm Davis Cc: sedna-discussion@lists.sourceforge.net Subject: Re: [Sedna-discussion] SEDNA release monitoring 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
