kicad-developers team mailing list archive

[Eeli Kaikkonen <eeli.kaikkonen@xxxxxxxxx>]

Thanks, that's great. I just had the impression that there would be more
changes after an RC release. In that case "beta" would have been more
realistic and the first RC could have been released a bit later.

Another thing, which also doesn't have to affect in any way but which I
anticipate, is that there seems to be much pressure gathered so that quite
a bunch of users will start to use the RC and will find many new bigger and
smaller bugs which then push the final release even farther. Calling the
first one "RC" may be a little bit optimistic. But that's just how things
go, as a former Open Source project developer I understand that there's no
perfect scheme and there will be some problems whatever you decide. The
important thing is to eventually have stable releases and continue with
development. I hope in the future I can help with that development in some
more material way than by just giving opinions. Now I started with a minor
thing to take even one small step to get more familiar with the community
:) I hope it didn't feel like I was stepping on someone's shoes.


2018-02-19 23:00 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:

> I think we are using rc in the correct context here.  Our alpha and beta
> testing is completely open and continuous thanks to our nightly builds.
> We are in feature freeze so no new feature code is being added to KiCad.
>  We are in the process of cleaning up a final few bugs before rc1.  If
> no bugs were found in rc1 then it would become stable version 5.0.0.
> I'm not going to hold my breath on that.  We just don't use showstopper
> bugs as our stable release criteria.  If we find UI strings with
> spelling errors or other minor polishing errors during rc1, we will fix
> them and release an rc2.  I'm not going to release a stable release
> version of KiCad with these minor bugs if I can avoid it just to appease
> some versioning scheme defined on Wikipedia.  Our current versioning
> scheme suits our purposes given our manpower limitations so until I find
> a compelling reason to change it, I will keep it the way it is.  Thank
> you for your input.
>
> Cheers,
>
> Wayne
>
> On 2/19/2018 3:38 PM, Eeli Kaikkonen wrote:
> > I'm not a KiCad developer, nor do I know much about its history or
> > developers, so I don't have any kind of authority here, but I feel I
> > have to talk about the version names. Now is probably the last possible
> > time to draw attention to it because "RC1" is around the corner.
> >
> > https://en.wikipedia.org/wiki/Software_release_life_cycle#
> Release_candidate
> > :
> >
> > "a beta version with potential to be a final product, which is ready to
> > release unless significant bugs
> > <https://en.wikipedia.org/wiki/Computer_bug> emerge."
> >
> > They key expression here is "ready to release". That's how it has been
> > used in all FLOSS projects I have seen. It means that the code doesn't
> > have to be changed for the final release unless serious new bugs are
> > found. I have got the impression that the next release of KiCad, which
> > now is called RC1, should really be beta1.
> >
> > So, how far KiCad is now from the final release? Has this been discussed
> > before and how this naming scheme have been decided? What do you
> > understand by RC and beta?
> >
> >
> > Eeli Kaikkonen
> >
> >
> > _______________________________________________
> > 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
> >
>
> _______________________________________________
> 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
>