phpwebsite-developers

[Phpwebsite-developers] Version 0.9 status question

[Geoff S. <ge...@ho...>]

We want to get more involved with this project and start developing some 
modules for it.

So, I have a couple of basic questions:

1. What do I need to do to upgrade my RC2 test site to RC3 (when it is 
available)? (Delete it and start over is a perfectly acceptable answer if 
that is easiest.)

2. What confidence level do you have that the database for RC3 will be 
final (or will further modifications to the database be needed)?

3. Is the module plug-in system sufficiently finalized to start working on 
some modules?

4. How many more release candidates do you think there will be before the 
final release of 0.9.0?

I'm just looking for a general idea of what to expect, not anything I can 
take to the bank!

Geoff
www.Hostricity.com

[Phpwebsite-developers] RC3 update

[Matthew M. <ma...@tu...>]

Hello all,

I talked with Adam and Steven today. Since we are in a new week, they
would like an opportunity to tighten the screws on some of the new modules
they are writing. I admit I would like a little elbow room as well. So we
are shooting for a lockdown on Thursday, a release Friday morning, a
re-release
later in the day to fix the obvious error we included in the first
release, and then a final one around midnight ;-)

Seriously, we are looking for Friday but we plan on testing better than
the last two times.

Now then, for the impatient and the module developers, information on update.

I have successfully updated RC2 to RC3. However, I would like some of you
who download CVS copies to give it a try.

Here is what you will need to do:
Get your cvs copy of the core, mods, and themes. Copy the appropriate
directories over. Obviously when RC3 comes out, you will just untar over
the old files.

If you go to your site, you MIGHT get an error if you are running
Calendar. No worries, go to setup/repair.php and follow the directions.
Ultimately, you will be able to deactivate calendar.

If you go back to your site, you will get an error in Boost, so while in
Repair, follow the question about Boost and choose Fix Boost.

NOW go back to your site, click on Boost, update Boost, update Core, and
update the rest of your modules. There is an Update All button at the
bottom of the screen.

You should be on RC3 level now. If there are any problems please let me know.

-------------------------------------------
For the developers, please check out Calendar as an example of updating.
It is very straight-forward and works much like the install.php file does.
Make sure you change your version number in your mod_info.php file. If it
is not greater than what is in mod_boost_version, it will not update. I
have updated most of the core files. I haven't touched other modules. If
you have not made any database changes, just increment your mod_info.php
version number. If you have made database changes since RC2, please enter
those changes in update.

Also, I did not use the --> if ($currentVersion < 2.3) <--- code in many
of the updates but they will appear as updates increase. MAKE SURE your
$status is TRUE by the end of the update or it will fail.

In the short term (maybe by RC3 release, maybe not) I will rethink
dependencies. I would like modules to tell you whether you need to update
other modules first. I also will build in the ability to turn modules off
before updating them.

Those of you having problems with Fallout, please try a CVS checkout and
see if repair.php helps you at all. Some changes have been made to
set_config.php to try to assist Windows installations as well.

Excelsior,
Matt


Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
phpwebsite.appstate.edu
ess.appstate.edu

Re: [Phpwebsite-developers] RC3 update

[Don S. <do...@se...>]

Is Calendar also a model for new module developers?

Don.

On Mon, 16 Dec 2002, Matthew McNaney wrote:

> Hello all,
> 
> I talked with Adam and Steven today. Since we are in a new week, they
> would like an opportunity to tighten the screws on some of the new modules
> they are writing. I admit I would like a little elbow room as well. So we
> are shooting for a lockdown on Thursday, a release Friday morning, a
> re-release
> later in the day to fix the obvious error we included in the first
> release, and then a final one around midnight ;-)
> 
> Seriously, we are looking for Friday but we plan on testing better than
> the last two times.
> 
> Now then, for the impatient and the module developers, information on update.
> 
> I have successfully updated RC2 to RC3. However, I would like some of you
> who download CVS copies to give it a try.
> 
> Here is what you will need to do:
> Get your cvs copy of the core, mods, and themes. Copy the appropriate
> directories over. Obviously when RC3 comes out, you will just untar over
> the old files.
> 
> If you go to your site, you MIGHT get an error if you are running
> Calendar. No worries, go to setup/repair.php and follow the directions.
> Ultimately, you will be able to deactivate calendar.
> 
> If you go back to your site, you will get an error in Boost, so while in
> Repair, follow the question about Boost and choose Fix Boost.
> 
> NOW go back to your site, click on Boost, update Boost, update Core, and
> update the rest of your modules. There is an Update All button at the
> bottom of the screen.
> 
> You should be on RC3 level now. If there are any problems please let me know.
> 
> -------------------------------------------
> For the developers, please check out Calendar as an example of updating.
> It is very straight-forward and works much like the install.php file does.
> Make sure you change your version number in your mod_info.php file. If it
> is not greater than what is in mod_boost_version, it will not update. I
> have updated most of the core files. I haven't touched other modules. If
> you have not made any database changes, just increment your mod_info.php
> version number. If you have made database changes since RC2, please enter
> those changes in update.
> 
> Also, I did not use the --> if ($currentVersion < 2.3) <--- code in many
> of the updates but they will appear as updates increase. MAKE SURE your
> $status is TRUE by the end of the update or it will fail.
> 
> In the short term (maybe by RC3 release, maybe not) I will rethink
> dependencies. I would like modules to tell you whether you need to update
> other modules first. I also will build in the ability to turn modules off
> before updating them.
> 
> Those of you having problems with Fallout, please try a CVS checkout and
> see if repair.php helps you at all. Some changes have been made to
> set_config.php to try to assist Windows installations as well.
> 
> Excelsior,
> Matt
> 
> 
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Appalachian State University
> Phone: 828-262-6493
> phpwebsite.appstate.edu
> ess.appstate.edu
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility 
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 
> 
> 

Re: [Phpwebsite-developers] Version 0.9 status question

[Matthew M. <ma...@tu...>]

> 1. What do I need to do to upgrade my RC2 test site to RC3 (when it is
> available)? (Delete it and start over is a perfectly acceptable answer
> if  that is easiest.)

There should be an upgrade path, so you should not have to delete it.

> 2. What confidence level do you have that the database for RC3 will be
> final (or will further modifications to the database be needed)?

The main database tables (modules, users, layout) should be stable. Any
changes will be gracefully attended to by the update script :)

> 3. Is the module plug-in system sufficiently finalized to start working
> on  some modules?

I think so. We are constantly writing new mods and we are writing a major
module in-house based on the current implementation.

> 4. How many more release candidates do you think there will be before
> the  final release of 0.9.0?

If RC3 goes well, then that will be last RC. A final release will follow.
If it goes bad, then one more RC.

> I'm just looking for a general idea of what to expect, not anything I
> can  take to the bank!

No problem. We are anxious to get it out as well.

Sincerely,
Matt

-- 
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
phpwebsite.appstate.edu
ess.appstate.edu