I was looking for an reason to stop testing older versions and a minimum of 8.04 is as good as any. Thanks
Sent from my iPhone > On May 22, 2018, at 11:19 AM, chris burke <[email protected]> wrote: > > The current code has a minimum release for builds of 804, see the Changes > section on page http://code.jsoftware.com/wiki/Addons/GitHub . > > >> On Tue, May 22, 2018 at 10:01 AM, bill lam <[email protected]> wrote: >> >> From JAL Build Log >> >> 2018 5 22 15 4 35 addons >> built: general/joddocument0.9.993 j804 >> general/joddocument0.9.993 j805 general/joddocument0... >> >> If you want to continue support j602, then RELEASE needed >> to be set to that version. Otherwise, from jwiki it said, >> >> RELEASE earliest J release supported, e.g. 'j805', or empty if all >> >> >> Вт, 22 мая 2018, John Baker написал(а): >>> After adding the required FOLDER and resetting the minimum RELEASE I >> managed to trigger a JAL update from the new GitHub repos. Incrementing the >> VERSION for commits is critical. >>> >>> The move to GitHub will expose J code to a much wider audience and >> foster better collaboration. I’d urge all addon authors to try out the new >> process. >>> >>> >>> >>> Sent from my iPhone >>> >>>> On May 21, 2018, at 9:22 PM, bill lam <[email protected]> wrote: >>>> >>>> rebuild should be automatical without any delay. >>>> >>>> In your manifest.ijs you had reverse something that >>>> are needed/changed since recently. >>>> >>>> -RELEASE=: '' >>>> - >>>> -FOLDER=: 'general/jod' >>>> - >>>> +RELEASE=:'j602 j701 j801 j802 j803 j804 j805 j806 j807' >>>> >>>> At least, the FOLDER is mandatory. and RELEASE is the >>>> minimum version that an addon will support. >>>> >>>> >>>> Пн, 21 мая 2018, John Baker написал(а): >>>>> I pushed a test JOD update to the jsoftware git repos. The commits >> show but it didn’t trigger a JAL build. >>>>> >>>>> Are the builds scheduled or is there a manual step on your end? >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On May 21, 2018, at 12:45 PM, chris burke <[email protected]> >> wrote: >>>>>> >>>>>> Each addon repo has a webhook that is used to update the J server >> addons. >>>>>> It sends a "commit" event to the J server so it can update the addon >> if the >>>>>> manifest version has been incremented. This is essentially the same >> as the >>>>>> old SVN commit event. >>>>>> >>>>>> Also, if you wish you can transfer your repos to your personal github >>>>>> account. I would encourage you to do so, though it will also be fine >> to >>>>>> leave them on the Jsoftware account. To make a transfer, login to >> github, >>>>>> view the repo and open Settings. Then in the Danger Zone at the foot >> of the >>>>>> Settings page, click the Transfer button and follow the >> instructions. Once >>>>>> transferred, you are free to rename it and change access permissions. >>>>>> >>>>>> >>>>>> >>>>>>> On Mon, May 21, 2018 at 11:31 AM, John Baker <[email protected]> >> wrote: >>>>>>> >>>>>>> In the next few days I will be committing a minor JOD update to the >> new >>>>>>> GitHub addon repos. >>>>>>> >>>>>>> I see I am a contributor to the JOD addons and I have set up local >> git >>>>>>> versions of them. I haven’t tried committing anything yet because I >> not >>>>>>> sure if there is anything else that needs to done to trigger an >> addon >>>>>>> build. When changes were committed to the old SVN repos JAL builds >> were >>>>>>> kicked off. I presume something similar will happen with the Git >> repos but >>>>>>> I fuzzy on the details. >>>>>>> >>>>>>> Jdb >>>>>>> >>>>>>> Sent from my iPhone >>>>>>> ------------------------------------------------------------ >> ---------- >>>>>>> For information about J forums see http://www.jsoftware.com/ >> forums.htm >>>>>> ------------------------------------------------------------ >> ---------- >>>>>> For information about J forums see http://www.jsoftware.com/ >> forums.htm >>>>> ------------------------------------------------------------ >> ---------- >>>>> For information about J forums see http://www.jsoftware.com/ >> forums.htm >>>> >>>> -- >>>> regards, >>>> ==================================================== >>>> GPG key 1024D/4434BAB3 2008-08-24 >>>> gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 >>>> gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3 >>>> ---------------------------------------------------------------------- >>>> For information about J forums see http://www.jsoftware.com/forums.htm >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >> >> -- >> regards, >> ==================================================== >> GPG key 1024D/4434BAB3 2008-08-24 >> gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 >> gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3 >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
