kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxxxx>]

I'm going to comment on everything posted thus far.  I don't have time
to reply on each individual comment.  I will say that I am not terribly
thrilled with date style version.  I'm not absolutely sure if it causes
grief for package management systems such as apt-get or yum.  I'm fine
with starting at whatever stable release version the next one would be.
 I believe it would be 3.0.0 or 4.0.0 since I've been with the project
but JP would know for sure.  Actually we would likely not have minor
point releases like 3.1.0 because of project policy of not backporting
features.  The only changes we will make to the stable branch is for
bugs that cause kicad to crash or loss and/or corruption of data.  The
only way I see this changing is if we have a huge influx of new
developers willing to take on that task.  Since we will be providing
nightly builds of binary installers in the not too distant future, users
who don't mind bleeding on the edge can help test new features in the
development branch.  I don't think that is unfair to ask users to help
contribute to the testing.

On 10/20/2014 10:20 AM, Andy Peters wrote:
> 
>> On Oct 19, 2014, at 4:58 PM, Ian Woloschin <ian@xxxxxxxxxxxxx> wrote:
>>
>> From a not-really-developer point of view, I do want to at least recommend the user of year-based release schemes, similar to how Ubuntu or MATLAB, as opposed to the more traditional "triplet" style numbering schemes.  From what I've read here KiCad isn't going to be doing more than a couple of "stable" releases a year, so why not do something like MATLAB's 2014a/2014b style releases?
>>
>> Pros:
>> Very easy to tell what release you're on, and how old it is
>> Very clear if a user is using outdated (unsupported?) software
>> No arbitrary decisions to upgrade a major number (and potentially confuse users)
>>
>> Cons:
>> Very obvious if you don't maintain stable releases over the long term (...which won't ever happen...right? :/)
>> Might be tough to line up KiCad releases with major Linux distro releases, so a user on Ubuntu 16.04 might be stuck on KiCad 2015a (which might not be a big deal, but it "looks" bad to the uninitiated)
>> Not always clear if something is drastically new or just a bunch of bug fixes
>>
>>
>> For reference regarding MATLAB versions, if anyone isn't familiar with MATLAB:
>> http://en.wikipedia.org/wiki/MATLAB#Release_history
> 
> 
> For the love of G-d, whatever you do, don't adopt that Altium "Season" scheme ... Summer 2011 and what-not. Is Winter 2011 earlier or later than Winter 2010? What hemisphere are you in?
> 
> I'm perfectly fine with the dotted-triplet thing, Major.minor.more-minor
> 
> -a
> _______________________________________________
> 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
>