Do you recommend using the github master for production?
Permalink
I'm coming from CodeIgniter and a CMS I developed myself. CI is also actively developed on a public repo and it's usually stable enough to use as a starting point instead of the last official release - since most of the commits are fixes or well-tested small additions to a stable core.
After going trough the commits in the Concrete5 repo it looks similar to the way CodeIgniter works. I'm a php developer, so I can catch and fix a small glitch that can creep up in the development version, but since I'm new to C5, I can't handle serious instability. On the other hand, I like all the small bugfixes I see on github since the last full release...
My question - which do you recommend for me - the official release or the latest master branch on github?
Thank you!
After going trough the commits in the Concrete5 repo it looks similar to the way CodeIgniter works. I'm a php developer, so I can catch and fix a small glitch that can creep up in the development version, but since I'm new to C5, I can't handle serious instability. On the other hand, I like all the small bugfixes I see on github since the last full release...
My question - which do you recommend for me - the official release or the latest master branch on github?
Thank you!
I don't think that would be a good idea at this time -- I believe the git repo is in active development.
I would recommend using the official releases. I know the core team is working on some new features at the moment, and if you're pulling those in on a regular basis they may end up breaking your current setup.
If you really want the updates and tweaks, I would recommend making your own fork of concrete5 and then cherry picking in the commits one at a time to your own 'stable-yet-has-cool-stuff' branch.
hmm, now I'm getting inspired... if I have a bunch of spare time I may end up doing that, but it's unlikely for the foreseeable future to be honest. Let me know if you go down that path though.
If you really want the updates and tweaks, I would recommend making your own fork of concrete5 and then cherry picking in the commits one at a time to your own 'stable-yet-has-cool-stuff' branch.
hmm, now I'm getting inspired... if I have a bunch of spare time I may end up doing that, but it's unlikely for the foreseeable future to be honest. Let me know if you go down that path though.
Thank you guys, you answered my question and the idea of a fork with bugfixes is great. I don't feel competent enough to decide about those yet, but if one of the veterans would do it, it would be a great idea.
An example from the CodeIgniter community - there were a few annoying little bugs in the release version (1.7.1) that were fixed in the repo for a long time but everyone still had endless troubles because they didn't know about the fixes.
An official fork of the most recent release with such small fixes maybe?
An example from the CodeIgniter community - there were a few annoying little bugs in the release version (1.7.1) that were fixed in the repo for a long time but everyone still had endless troubles because they didn't know about the fixes.
An official fork of the most recent release with such small fixes maybe?
I think i could do that after the next release...
Mike, do you know what the ETA on the next release is (just a ballpark)? I want to start making some improvements but might wait until the next release in case they've already been made or other new features would impact them.
Thanks.
-Jordan
Thanks.
-Jordan
I'd make the improvements now, and if you think they could benefit the community as a whole, submit them as a pull request.
> or the latest master branch on github?
I guess I missed an announcement. Is the C5 repo now on Git? If so, where? The last URL I had for it now yields a 404.
-Steve
I guess I missed an announcement. Is the C5 repo now on Git? If so, where? The last URL I had for it now yields a 404.
-Steve
https://github.com/concrete5/concrete5
(Your URL may have been http: instead of https: -- sometimes github doesn't redirect properly and you see the wavy star wars 404 message)
(Your URL may have been http: instead of https: -- sometimes github doesn't redirect properly and you see the wavy star wars 404 message)
>https://github.com/concrete5/concrete5...
Thanks, Jordan! (Is the URL somewhere on this site BTW? I couldn't find it in the obvious places like under the developer menu.)
> Your URL may have been http: instead of https:
Actually, it was the "aembler" URL (Andrew's own account I guess) from way back after the initial announcement by Franz.
> and you see the wavy star wars 404 message
Yeah, what a cool parallax effect!
-Steve
Thanks, Jordan! (Is the URL somewhere on this site BTW? I couldn't find it in the obvious places like under the developer menu.)
> Your URL may have been http: instead of https:
Actually, it was the "aembler" URL (Andrew's own account I guess) from way back after the initial announcement by Franz.
> and you see the wavy star wars 404 message
Yeah, what a cool parallax effect!
-Steve
yeah, we moved it under a concrete5 organization.
