Status on 5.6
Permalink
There have been some diccussion about the status of 5.6 in the bug tracker. We all know that the core team is very busy at work with 5.7 and want to get that out of the door as soon as possible. But what is the current status of maintaining 5.6 and releasing new updates for it?
To my understand the next bug fix release for 5.6 has been cooking for quite some time and it should be done.
I can understand very well that the core team has a a lot work with 5.7. But there are so many sites running 5.6 and I think it is very important that the core team still offers good support for that product.
It will take some time before 5.7 is ready for production use and many of us have to create new sites for clients before this happens. And it is important that the current version is as polished as possible.
In my opinion we should try to support both 5.6 and 5.7 as long as possible.
We just had one meeting with a client who was making a decision for the CMS used. And when they are doing a large project with the current version, they want to know that the version will be supported in the future and they don't have to make a very large update to a new major version right away. It is not optimistic to think that we can make a large 5.6 site now and just easily update it to 5.7. So we cannot market that idea to the customer either.
Could the core team take some time and go through all the open bugs in 5.6 and see which of those can be easily fixed and make some decisions of which of the harder bugs they can tackle quickly?
To my understand the next bug fix release for 5.6 has been cooking for quite some time and it should be done.
I can understand very well that the core team has a a lot work with 5.7. But there are so many sites running 5.6 and I think it is very important that the core team still offers good support for that product.
It will take some time before 5.7 is ready for production use and many of us have to create new sites for clients before this happens. And it is important that the current version is as polished as possible.
In my opinion we should try to support both 5.6 and 5.7 as long as possible.
We just had one meeting with a client who was making a decision for the CMS used. And when they are doing a large project with the current version, they want to know that the version will be supported in the future and they don't have to make a very large update to a new major version right away. It is not optimistic to think that we can make a large 5.6 site now and just easily update it to 5.7. So we cannot market that idea to the customer either.
Could the core team take some time and go through all the open bugs in 5.6 and see which of those can be easily fixed and make some decisions of which of the harder bugs they can tackle quickly?
I'm trying to take care of 5.6 pull requests, but I don't have the time to test everything myself, the amount of people testing pull requests is unfortunately pretty small... Going through all the open bugs in 5.6 isn't a quick thing, that's a task which takes a few days.
I believe that the current master branch on github is pretty stable, we're using it on all our new projects and didn't have any issues so far.
About an official release - that's not up to me, that's a core team task..
I believe that the current master branch on github is pretty stable, we're using it on all our new projects and didn't have any issues so far.
About an official release - that's not up to me, that's a core team task..
I just reprioritized Andy's time to have him make a release candidate build of where 5.6 is at now. That'll be a nice zip that can be downloaded and applied as an upgrade without the burden of grabbing it out of github by hand.
If we could get a couple dozen individuals verifying that they had applied this update with success, it would make us feel more comfortable calling it an "official" release and updating the various auto-installers to serve it to folks who aren't able to fix their own potential issues.
If we could get a couple dozen individuals verifying that they had applied this update with success, it would make us feel more comfortable calling it an "official" release and updating the various auto-installers to serve it to folks who aren't able to fix their own potential issues.
Franz,
Can you or someone ping back to this discussion with a link to the zip, I'd be happy to deploy it to a few of our less critical sites.
Thanks,
Joe
Can you or someone ping back to this discussion with a link to the zip, I'd be happy to deploy it to a few of our less critical sites.
Thanks,
Joe
Same here.
Can install the package on multiple places.
And I think everyone appreciates especially Remo's time he has taken in the 5.6 making pull requests. Good job. :)
Can install the package on multiple places.
And I think everyone appreciates especially Remo's time he has taken in the 5.6 making pull requests. Good job. :)
http://www.concrete5.org/developers/bugs/5-6-3-1/waiting-for-update...