[Koha-devel] updatedatabase (bug 7167)

[Ian Walls]

As eager as I am to have a more robust database update method, I think the
ship has sailed for 3.8.  I believe the new mechanism should be part of
both 3.6.x and master, so we're going to need a time when 3.6.x == master,
at least on the DB level.  That may or may not happen, as new features come
along.  The next time we know stable release and master will be equal is
just after 3.8 releases.

So, how about we test this new mechanism, but slate it for release along
with 3.8?


-Ian

On Wed, Nov 30, 2011 at 10:58 AM, Chris Nighswonger <
cnighswonger at foundations.edu> wrote:

> On Wed, Nov 30, 2011 at 10:53 AM, Paul Poulain
> <paul.poulain at biblibre.com> wrote:
> > Le 30/11/2011 15:54, Chris Nighswonger a écrit :
> >> 2. If the db update improvements are introduced into master during the
> >> 3.7.x development cycle, they must be back ported to the 3.6.x branch.
> >> The only condition I will withdraw this objection under is if this
> >> "feature" is pushed immediately prior to the release of 3.8.0.
> > I don't understand why we need to backport this new mechanism.
> > With the new system, we can address separately updateDB patches for
> > stable and master version (with the same patch, I don't mean in 2
> > different patches). I think that's how we must do it.
> >
> > Let me give you an example with actual mechanism:
> > Day 1 => updatedatabase for bugfix passes QA and can be pushed
> > Day 2 => updatedatabase for a new feature passes QA and can be pushed
> > Day 3 => updatedatabase for a bugfix passes QA and can be pushed
> >
> > How will you deal with D2 patch ?
> > ATM, you'll have a problem, isn't it ?
> > D1 = should be 3.07.00.001 on master
> > D2 = should be 3.07.00.002 on master
> > D3 = should be 3.07.00.003 on master
> > except you're not supposed to push D2 patch on stable branch.
> > (or there's something i'm missing)
>
> I think you have missed something. Take a look at the release notes
> for 3.6.1. You will see several enhancement bugs included. These are
> smallish and are included because they improve existing features. This
> has been true from day one of my tenure as Release Maintainer. If you
> remove the ability to back port all enhancements, you remove this
> option.
>
> I maintain my opposition to not back-porting the db update changes.
>
> Kind Regards,
> Chris
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20111130/88d783c9/attachment.htm>