Sandbox

The some Patch_Packages contains the "installation" Directory. 

Björn

Rey: Respect! Making mistakes is human; admitting them takes courage!

And: Core-1.07 files are allready flowing this way! ;-)

Well have upgraded from 1.0.5 to 1.0.7 and it seems to be working good. Haven't found errors yet.

Just curious...
I noticed on this page under Status that 1.0.7 is listed as Pending whereas everything else is Active.  Is that something that needs to be changed?

EDIT:  I see that the status has been changed to Active 

Good thing that I haven't put my site online yet. I've been developing a site with 1.0.5 offline on my personal server. I have 4 to do but only started on the one site and have it nearly finished.

Do I use the upgrade package or can I erase all the files (except my template, modules and components, etc. I added) and refresh with all new 1.0.7 files, but keep the old database intact? I'm not sure which way would be easiest.

As for the other 3 sites which I haven't started, that is easy. I'll just wait for 1.0.7 to arrive and work with that.

Now I assume for any future releases, I can just use the upgrade packages?

I'm quite confused on what upgrade packages actually do. Do they just keep kludging the code and patching things or do I get the same as I would have if I had the actual 1.0.7 package? I am concerned that the more I upgrade, the more a mess I'll make of the code being all patched up from different versions and instead of the latest version, I'll have a severely patched up version which is a mixture of several previous versions?

What is my best cource of action at this point? Suggestions are welcome.

I too would like to know if it's ok to get 1.0.7 even if the status is "pending". Is the code the same as the final version?

Well as they say...to err is human...to really stuff things up requires a computer 
In serious...thanks to the Dev team and for responding so quickly to the noted error.

Phil

Hi,

My mom always says: "Backup your file system before applying a patch, and always test unpacking an archive before releasing it !!"
Just kidding 

Hey Rey, does it mean you're alone on this matter? No offense but if so, it's too much responsability on one man's shoulder IMO.
Like Phil said, I think it's high time to set some "more strict" test proceedures and more people involved before releasing a new version. Patching a site should not be a "patch and pray" process, and since 1.0.5 release... 

Again, it's not a personal attack Rey, I really appreciate your hard work, but you need more support man; where is the rest of the Core Team BTW !? I know it's sunday but remember, 1.0.5 was released on holidays... Why not releasing on business days when more people are available?

hornos wrote:Hey Rey, does it mean you're alone on this matter? No offense but if so, it's too much responsability on one man's shoulder IMO.
Like Phil said, I think it's high time to set some "more strict" test proceedures and more people involved before releasing a new version. Patching a site should not be a "patch and pray" process, and since 1.0.5 release... 

The work on Stability Releases of course invovles many people and there a re a myriad of testers involved.

However the process of finalizing, packaging and releasing falls under my responsibility alone - this is actually the most efficent and effective way to do this as the coordination of all the PI information and the uploading of files needs to reside with one person to effectively coordinate it all.  It also is my direct responsibility as the Stability Team Leader.  We have tried having more people involved in the release process, but it is actually harder to manage than having one person in central control.

As to the more strict test & release procedures, we are in agreeance here.  And we are on the way to introducing these, however as anything take time to implement.  However, the main problem here was the testing procedure - not necessarily the release procedure.

hornos wrote:Again, it's not a personal attack Rey, I really appreciate your hard work, but you need more support man; where is the rest of the Core Team BTW !? I know it's sunday but remember, 1.0.5 was released on holidays... Why not releasing on business days when more people are available?

They have been here at different times and before 1.0.7 was released we conferenced as to the best course of action to take.
However, there is the distinction between stability work and development work.  So those involve in 1.1.x are obviously focused on working on 1.1.x

As to release times, it is actually easier on the weekends as that is when we have the free time.  Business days, means everyone is focusing on their `normal` work.



But we will be most definitely fully examining all procedures and working to improve them as a priority

ok so it's save to update to 1.0.7 now?

Put it on a test server and see how it does for you.

Should'nt 1.0.6 be taken off the Forge all together ??

I know v1.0.7 is now there but some peeps might not see the tiny note at the top of the files saying don't use etc.

Just athought..

hornos - Good advice though. I always back things up just in case. But once a site is live with people contributing (the site I'm working on now will have people register and contribute articles and links, then a staff member will review and publish them (or reject and notify the author of needed changes). So if I have a fully live site, I'll want to be sure the upgrade goes through smoothly enough, so as to minimize down-time.

Rey - I agree with you. I too, think that sometimes too many cooks spoil the pot, as the proverb goes. But I guess one has to have a balance. Open Source works great because of the fact it has many developers and testers on a project. But some areas may need more than others. I had done a programming project in Visual Basic years ago where I was the sole programmer/developer/packager and I had a team of 10 beta testers who just tested and reported bugs. It wasn't easy, even with a very small project such as that one. I can't even imagine some of these open source projects with all these folks working on it. Coordinating can be quite difficult, I'd imagine.

As for the business days/weekends - I was thinking the same thing. I work on my own sites on the weekends as I have to work during the week, so there's no time. Sometimes though, I do manage to sneak in some time in the evenings, depending if I have to work late or not. But I do like to do other stuff - games, hobbies, etc. and sometimes just get away from the computer for a little while.

Hats off to you guys. You're doing great! I've already been convinced to decide on Joomla over Mambo.

Well I don't have a test server and I never tested joomla before updating...

Well then the best idea is to wait 24/48 hours at least after a release....lots of other people have a test server and you can sit back while all hell breaks loose on their sites 

Phil

phil_roy wrote:Well then the best idea is to wait 24/48 hours at least after a release....lots of other people have a test server and you can sit back while all hell breaks loose on their sites 

Phil

Great idea, will do that. Lucky I almost did that and didn't put 1.0.6.

I think we better close this thread seeing as 1.0.7 is now out..