kicad-developers team mailing list archive

[Chris Pavlina <pavlina.chris@xxxxxxxxx>]

I think you misunderstand my suggestion, then. What I want to push into a minor
release is a check to make sure the version is valid - nothing that changes the
format. I want the minor release to start checking the version, so that when we
put out the major release later (which *does* add things to the format), people
still on the previous release will get a proper error message when opening
files the new major release has generated.

On Thu, Apr 07, 2016 at 05:20:41PM +0200, Marco Ciampa wrote:
> On Thu, Apr 07, 2016 at 11:01:26AM -0400, Chris Pavlina wrote:
> > I'm not sure what you mean by that.
> > 
> > On Thu, Apr 07, 2016 at 04:52:52PM +0200, Marco Ciampa wrote:
> > > On Thu, Apr 07, 2016 at 09:47:41AM -0400, Chris Pavlina wrote:
> > > [...]
> > > > Thoughts?
> > > 
> > > I am not a dev. I KNOW.
> > > 
> > > But... such a change (file and footprint format change) IMHO is not apt
> > > to (only) a minor version change...
> > > 
> 
> Forgive my bad English.
> 
> I mean that I expect to find a file format change between a major version
> change, not between two different minor format versions.
> 
> Between two minor version change I can expect to fine just better
> functionalities and/or bug fixies, not something that (potentially)
> breaks compatibility.
> 
> This is what I am used to, but I may be wrong of course.
> 
> --
> 
> 
> Marco Ciampa
> 
> I know a joke about UDP, but you might not get it.
> 
> ------------------------
> 
>  GNU/Linux User #78271
>  FSFE fellow #364
> 
> ------------------------
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp