Hi Matt, Making a release on GitHub is extremely simple. Steps to take:
- Go to GitHub and jallib - Go to 'Releases'. There are 0 at this moment - Press the button 'Create a new release' - Give the release a tag version, e.g 'Jallib 1.4.0' - Give the release a title, e.g. 'Release of Jallib 1.4.0' or something else if you want that makes this release so special. - Press the button 'Publish Release'. With a checkbox you can indicate that this is a pre-release. You can wait for the response before publishing the release so that you do not have to use the pre-release option now. That's all! Kind regards, Rob On Sunday, January 27, 2019 at 5:51:41 PM UTC+1, Matthew Schinkel wrote: > > I don't know how to make a Github beta release, you can go ahead with that > and let me know how you did it. I'm not sure when a good time to do it is, > maybe when the final is released? > > I will remove those samples from torelease. > > Other versions of the compiler can stay. > > I'm not sure where install.log comes from, i'll look and remove it. > > I can release another beta, but lets wait and see if anything else shows > up. > > Matt. > > On Sunday, January 27, 2019 at 5:31:05 AM UTC-5, RobH wrote: >> >> >> Hi Matt, Rob and others, >> >> On 2019/01/27 03:21, Matthew Schinkel wrote: >> >> >> I've released Jallib 1.4.0 Beta. It is available for download at >> http://www.justanotherlanguage.org/downloads under Beta Release >> >> Please let me know if there are any major issues, otherwise this package >> will be promoted to be the final release. >> >> >> I found in the sample directory 3 programs with an compilation issue: >> - 16f877_fat32_small_sd_card warning: Hardware stack overflow >> - 16f877a_fat32_small_sd_card warning: Hardware stack overflow >> - 16f1455_usb_hid_keyboard warning: skip error at 0x038d >> >> I have my doubts about the usefulness of distributing 'other_versions' of >> the compiler since these are all older versions. If someone needs a >> compiler version for an 'unsupported' operating system he/she maybe clever >> enough to generate it from the sources or ask help from another user in the >> discussion group. >> >> The file README and several other files still contain the googlecode URL: >> - doc/html/jallib.css: >> - lib/transceiver_cc1101.jal >> - lib/accelerometer_gyroscope_bmi160.jal >> - project/pic18f14k50_usb_io/serial_converter/usb_serial_converter.jal >> - project/pic18f14k50_usb_io/led_switch_test/18f14k50_led_switch_test.jal >> - project/pic18f14k50_usb_io/examples/usb_serial_converter.jal >> - project/pic18f14k50_usb_io/examples/usb_i2c_master.jal >> - project/pic18f14k50_usb_io/examples/board_18f14k50_usb_af.jal >> - project/pic18f14k50_usb_io/examples/blog_part3.jal >> - project/pic18f14k50_usb_io/examples/blog_part2_a.jal >> - project/pic18f14k50_usb_io/bootloader/18f14k50_usb_bootloader.jal >> - project/lcd_interface/lcd_interface.jal >> - sample/18f4620_transceiver_cc1101.jal >> - sample/16f1455_usb_serial.jal >> >> Distributing the install log in the release package seems not of interest >> to the 'average' Jallib user. >> >> Regards, Rob. >> >> >> -- >> *Rob H*amerling, Vianen, NL >> > -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/jallib. For more options, visit https://groups.google.com/d/optout.
