[Spce-user] db rev naming

Alex Lutay alutay at sipwise.com
Fri Aug 21 12:36:21 EDT 2015

Hi Jon,

Sorry for delay, we are a bit busy now :-)
The idea is good, I am completely agree to keep some spaces between ID.

I am not sure about possibility to use release version in DB statements.
It will create misunderstanding for backported DB statements.

Maybe it will be enough just to multiply current login on 10.
So, Sipwise will release 12340, 12350, 12360 which has a gap for 9
statements everywhere.

What do you think?

On 08/20/2015 01:19 AM, Jon Bonilla (Manwe) wrote:
> I'd like to suggest to change the naming policy of the db revisions. At the
> moment they are numbered with consecutive numbers. 
> I am doing  PBX integration for one customer and I have to extend the db schema
> with new preferences and tables. If I create db revs for those changes I don't
> have numbers for them as the next rev provided by Sipwise will follow the last
> one. 
> I would suggest to change the numbering plan for future revs to something like
> this:
> 401XX Where 401 means mr 4.0.1 and XX and increasing id. That way, if 15 db
> revs are supplied with mr4.0.1 I know that I have 85 slots for custom revs as
> next release would start with 40200 or 41100.
> This naming is compatible with ngcp-update-db-schema and it also provides more
> information about ngcp version and rev mapping. 
> Is this something it could be considered for future releases?

Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com

More information about the Spce-user mailing list