Hi Malcolm,
> The problem is that developers/admin needs to understand the details so
> they
> can make decisions on deploying patches.
>
It's not possible to annotate each patch in development branch so that it's
understandable to users. Moreover, this is not necessary. The rule is:
don't deploy development branch in production until we said it's stable or
released new version.
You can monitor 3.5.xxx-release-fixes brach (if any). It contains (or will
contain) critical fixes which are 100% safe to apply. We'll try to describe
them so that they are understandable for your admins and will try to
connect patches with trackers.
> For example, the following bug fix from 2 days ago seems important: "Some
> indecies bugfixes. Indexing on text nodes working"
>
Yep. It fixes some tricky use case with indices. But, again, you can't
apply it in production. We need to run complex testing to be sure that
everything is ok.
> I see the disconnect between bug tracking & git, and I see how some of the
> disconnection can occur.
> ...
> What should have occurred is the Sedna team saying: Yes, dateTimes
> subtraction is an issue, please go to the bug tracker & enter the issue.
>
It works sometimes, sometimes it doesn't. Usually users don't like to
submit and describe issues formally. Don't forget also, some users have
private data.
Moreover, a lot of bugs are found and fixed by ourselves :). It's not
practical for us now to use bug tracker for every bug fix or change.
> 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.
>
Yes, github is very good. But is it good enough to discard project's
history - trackers, lists, old releases? Is it possible to easily migrate
all that stuff? We started with SF long before github appeared.
Ivan Shcheklein,
Sedna Team
-----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
>
>
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
