kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

No hurry.  Just something to think about before the stable release.  Thanks.

On 11/9/2015 4:26 PM, Nick Østergaard wrote:
> Yes, this can be done very easily. There is already binaries on
> http://docs.kicad-pcb.org/ that can be downloaded as a zip or tar.gz
> file. I might try to tage some with an rc2 tag to prepare everything
> and every packager. I forgot to do that, but probably tomorrow.
> 
> 2015-11-09 22:23 GMT+01:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>>
>>
>> On 11/9/2015 9:13 AM, Nick Østergaard wrote:
>>> 2015-11-09 14:54 GMT+01:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>>>> On 11/8/2015 6:01 PM, Nick Østergaard wrote:
>>>>> Hi Wayne
>>>>>
>>>>> Thank you for realasing. Although the download link is a bit strange..
>>>>> it still partly refers to rc1.
>>>>>
>>>>> https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz
>>>>>
>>>>> But anyway, I guess we can just say that the docs, and their
>>>>> translations, and the GUI translations shall be done in two weeks if
>>>>> they want to be included with the release. The same witht he libs, if
>>>>> anything is is left to be done, and we can just take a snapshot of the
>>>>> libs and put it on the download page.
>>>>
>>>> I'm wondering if we should branch the translation and doc repos.  Once
>>>> new features and strings are added to kicad during the next development
>>>> cycle, updating the translation and doc repos will not make sense
>>>> against the 4.0 stable release of kicad.  Creating 4.0 branches of the
>>>> doc and translation repos would allow for new translations and improved
>>>> documentation for the 4.0 stable release.  There would be some
>>>> cross-over between the 4.0 and development repos which would be a bit
>>>> more work.  I'm OK with tagging the current repos as well.  The downside
>>>> to that is there will be no new translations or doc improvements until
>>>> the next stable release.  I'll leave that up to the doc and translation
>>>> folks.  Tagging and a snapshot archive makes sense for the lib repo.
>>>
>>> I think just tagging it should be sufficient to generate a release
>>> tarball on github (4.0.0.0). If we need followup changes we can make a
>>> leaf branch from there or later on the master branch with 4.0.0.1. I
>>> don't think -n is good here, because multiple packaging systems use a
>>> dash number notation to describe revisions of the packaging scripts
>>> themselves. The triplet is reserved to the kicad source, so we must
>>> need some other indicator for auxiliary stuff. But we really need to
>>> align the version numbers across the source code, docs, translations
>>> and libs.
>>
>> I just thought of something.  We will need a way to fetch the built
>> documentation for packaging on platforms that don't have the native
>> tools to build the docs from source.  I still have not had any success
>> building the docs from source on windows.  This means that if we do tag
>> the doc repo rather than branch it, we will need to be able provide
>> builds from the tagged version of at least the pdf files for all
>> languages.  I'm assuming this can be done.  If not, we will have to find
>> alternative.
>>
>>>
>>>>> 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>>>>>> I just finished up getting all of the relevant code for RC2 uploaded to
>>>>>> launchpad so let's fire up those autobuilders and get some rc2 packages
>>>>>> out there for testing.  I'm hoping this will be the last rc before the
>>>>>> stable release.  Let's keep our fingers crossed.  We need start thinking
>>>>>> about branching or tagging the library, documentation, and translation
>>>>>> repos so that packagers can build consistent packages for their
>>>>>> respective platforms.  Thanks to everyone who made this possible.  I'm
>>>>>> going to step away from my computer for a while and enjoy the adult
>>>>>> beverage of my choice.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Wayne
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>
>> _______________________________________________
>> 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