kicad-developers team mailing list archive

[Carl Poirier <carl.poirier.2@xxxxxxxxx>]

The kicad-library repository and all non-empty .pretty repositories have
been tagged as well!

Congrats to everyone. It's a great day today!

Carl Poirier

On Sun, Nov 29, 2015 at 4:19 PM, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
wrote:

> Wonderful!  Thanks all!
>
> I should be able to push the button on an OS X download tonight, and I'll
> sanity check and then push it again with the proper fancy name tomorrow :)
>
> Adam Wolf
>
> On Sun, Nov 29, 2015 at 3:17 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx>
> wrote:
>
>>
>>
>> On 11/29/2015 04:05 PM, Nick Østergaard wrote:
>> > 2015-11-29 21:39 GMT+01:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>> >> I just finished rolling out KiCad 4.0.0.  Many thanks to everyone who
>> >> made this possible.  Each and every one of you deserve to sit back and
>> >> enjoy this accomplishment.  I have a few minor requests before I make a
>> >> trip to my refrigerator to grab a cold one to celebrate.
>> >>
>> >> Someone please add an announcement the to blog page on the KiCad
>> website?
>> >
>> > Yes, I am on it. It will be available shortly.
>>
>> Thanks.
>>
>> >
>> >> The footprint, symbol and 3D model library, documentation, and
>> >> translation repos need to be tagged 4.0.0 so future package builds can
>> >> pull the proper version.  At some point in the future we may need to
>> >> create 4.0.0 branches of the library, documentation, and translation
>> >> repos but for now the tags should suffice.  Please do not make any
>> >> commits to these repos until after they are tagged.
>> >
>> > Commiting should not prevent you to tag commits in git, and I don't
>> > even think so in bzr. :)
>>
>> You are correct.  I had a brain cramp.  You just have to remember which
>> commit needs to be tagged if you make any commits after the announcement.
>>
>> >
>> >> What do we need to do as far as creating automated builds for the
>> >> correct version of the documentation?  I know packagers on some
>> >> platforms will need pre-built documentation for the 4.0 release.  This
>> >> shouldn't be a significant issue until we start documenting new
>> features
>> >> during the next development cycle.
>> >
>> > I am planning to just build the latest docs and make them available on
>> > downloads.kicad-pcb.org/docs/kicad-doc.{tar.gz,zip}
>> <http://downloads.kicad-pcb.org/docs/kicad-doc.%7Btar.gz,zip%7D> or
>> something.
>>
>> Thanks.
>>
>> >
>> >> Please do not swamp me with patches and new feature merge requests over
>> >> the next few days.  I have some of my own coding that I need to get
>> done
>> >> for the next development cycle so I'm not going to have a lot of time
>> to
>> >> do code reviews and I would like to reduce the number hours a week I've
>> >> been spending working on KiCad for a few weeks.
>> >
>> > Thank you for finally calling the release.
>> >
>> >> Thanks again everyone!
>> >>
>> >> 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
>
>