What version to use? #958

New Issue

Closed

opened 2022-09-27 16:01:39 +00:00 by Chris Paschen · 2 comments

Chris Paschen commented

2022-09-27 16:01:39 +00:00

Member

(in past I would have added this to the 'discussions' area, but we don't seem to have that on the git.vdm.dev area)

Due to the fact that I'm now teaching when the live meetings are happening, I can't participate and feel a bit out of the loop on what is going on with JCB.

It would be nice to just have even a short paragraph every meeting or two just to know about where things stand and what we should be doing to prepare for the J4 version (if anything).
For those of us still develping extensionis with JCB on J3, what version/tag/etc is 'stable'? If we need to just use an older, but 'stable' version, that isn't getting regular release updates, that is fine. But trying to navigate around potential issues in releases that haven't been widely tested can be a bit troublesome when trying to create something functional right now.

This is not to be critical of the process - just wanting to know what would be the 'best practice' for those of us who can't be active in the current 'migration' process of JCB and just need to remain productive and be ready to use and promote the J4 version of JCB when it is released as stable.

Thanks!

(in past I would have added this to the 'discussions' area, but we don't seem to have that on the git.vdm.dev area) Due to the fact that I'm now teaching when the live meetings are happening, I can't participate and feel a bit out of the loop on what is going on with JCB. 1. It would be nice to just have even a short paragraph every meeting or two just to know about where things stand and what we should be doing to prepare for the J4 version (if anything). 2. For those of us still develping extensionis with JCB on J3, what version/tag/etc is 'stable'? If we need to just use an older, but 'stable' version, that isn't getting regular release updates, that is fine. But trying to navigate around potential issues in releases that haven't been widely tested can be a bit troublesome when trying to create something functional right now. This is not to be critical of the process - just wanting to know what would be the 'best practice' for those of us who can't be active in the current 'migration' process of JCB and just need to remain productive and be ready to use and promote the J4 version of JCB when it is released as stable. Thanks!

Llewellyn commented

2022-09-29 18:43:48 +00:00

Owner

This is the official descution form of JCB: https://github.com/vdm-io/Joomla-Component-Builder/discussions

So you can take this conversation there 👍

@startmindmap
+ JCB
++ git.vdm.dev
+++ Main Repository
++++ Branches
+++++ All active branches
++++ Tags
+++++ All version
++++ Releases
+++++ Package Releases
+++++ Includes all Plugins
++++ Issues
+++++ Only Core JCB related issues
+++++ You can use UML in Issues
++++ Pull Requests
+++++ Contributors welcome
+++++ All Active Forks
++++ Projects
+++++ Joomla 4
+++++ Compiler Improvements
+++++ Feature Requests
++ github.com
+++ Mirror Repository
++++ Updates Automaticly
+++ Discussions
++++ Announcements
++++ Extention Issues
++++ General
++++ Ideas
++++ Opportunities
++++ Polls
++++ Q&A
++++ Show and tell
@endmindmap

This is the official descution form of JCB: https://github.com/vdm-io/Joomla-Component-Builder/discussions So you can take this conversation there 👍 ```uml @startmindmap + JCB ++ git.vdm.dev +++ Main Repository ++++ Branches +++++ All active branches ++++ Tags +++++ All version ++++ Releases +++++ Package Releases +++++ Includes all Plugins ++++ Issues +++++ Only Core JCB related issues +++++ You can use UML in Issues ++++ Pull Requests +++++ Contributors welcome +++++ All Active Forks ++++ Projects +++++ Joomla 4 +++++ Compiler Improvements +++++ Feature Requests ++ github.com +++ Mirror Repository ++++ Updates Automaticly +++ Discussions ++++ Announcements ++++ Extention Issues ++++ General ++++ Ideas ++++ Opportunities ++++ Polls ++++ Q&A ++++ Show and tell @endmindmap ```