Indeed the last real discussion BigBlueButton - Completion conditions ended 14 November. Since then there are five "discussions" where people are talking alone including the post above.
Visvanath Ratnaweera
Posts made by Visvanath Ratnaweera
Hi Andrew
I didn't get your suggestion as I replied earlier:
> change a little with one branch per set of releases (with a set ending on the LTS release - e.g. 4.2-4.5 is a set).
Fully agree. This is indeed a simple and neat solution!
Repeating: Rather than one plug-in producing a branch for 3.4-3.8, another for 3.9-3.11 and the latest 4.0-4.2 and the other plug-in going 3.6-3.9, 3.7-3.10, 3.9-3.11 and 4.0-4.2, everybody goes 3.10-4.1 (LTS), 4.2-4.5 (LTS), etc.
Others, if you too think this is a good idea, please "vote" by rating Andrew's post as Useful!
I didn't get your suggestion as I replied earlier:
> change a little with one branch per set of releases (with a set ending on the LTS release - e.g. 4.2-4.5 is a set).
Fully agree. This is indeed a simple and neat solution!
Repeating: Rather than one plug-in producing a branch for 3.4-3.8, another for 3.9-3.11 and the latest 4.0-4.2 and the other plug-in going 3.6-3.9, 3.7-3.10, 3.9-3.11 and 4.0-4.2, everybody goes 3.10-4.1 (LTS), 4.2-4.5 (LTS), etc.
Others, if you too think this is a good idea, please "vote" by rating Andrew's post as Useful!
Hi Davo
You must have misunderstood. This has nothing about developing. Rather about Linux system administration in running very active Moodle sites. All "manual" Unix CLI on dedicated or virtual private servers. A couple of the Moodle instances have upward of 50 additional plug-ins installed. We are transitioning from 3.9 LTS to 4.1 LTS. I can see hours and hours of manual, individual Git commands in each plug-in directory.
Even if there is a magic method, it is too late for the Moodle instances I am trying to upgrade currently, one has started as a Moodle 1.5, the other something 2.4.
Oh yes, the plug-ins have been fetched with 'git clone' from their GitHub repos. (No the 1.5 wasn't. But over the years, I replaced the unpacked zip directories with Git repos.)
You must have misunderstood. This has nothing about developing. Rather about Linux system administration in running very active Moodle sites. All "manual" Unix CLI on dedicated or virtual private servers. A couple of the Moodle instances have upward of 50 additional plug-ins installed. We are transitioning from 3.9 LTS to 4.1 LTS. I can see hours and hours of manual, individual Git commands in each plug-in directory.
Even if there is a magic method, it is too late for the Moodle instances I am trying to upgrade currently, one has started as a Moodle 1.5, the other something 2.4.
Oh yes, the plug-ins have been fetched with 'git clone' from their GitHub repos. (No the 1.5 wasn't. But over the years, I replaced the unpacked zip directories with Git repos.)
Hi Luca
Thanks for the prompt support. Note that I haven't touched a zip, rather "got the latest https://github.com/h5p/moodle-mod_hvp by cloning". Do you mean, I need to combine many Git repos in to /mod/hvp/?
Thanks for the prompt support. Note that I haven't touched a zip, rather "got the latest https://github.com/h5p/moodle-mod_hvp by cloning". Do you mean, I need to combine many Git repos in to /mod/hvp/?
I'm sorry, I was just sarcastic. I support a whole bunch of teachers who use H5P systematically. When they started it was only the mod_hvp. The "competition" confused them, and me too. Now we have two halves. You know, they don't make one full.
Wanted to vent. I don't want to dive deep, I don't know the waters.