Support/TikiTrunkTestingNotes: Difference between revisions
< Support
Jump to navigation
Jump to search
MarcLaporte (talk | contribs) |
MarcLaporte (talk | contribs) No edit summary |
||
| Line 8: | Line 8: | ||
=== 2009-12-28 === | === 2009-12-28 === | ||
* http://tiki-trunk.mozilla.com/ is now testable | * http://tiki-trunk.mozilla.com/ is now testable | ||
** Very soon, automatic svn upgrades will be sorted (and we'll have revision number if bottom bar) | ** Very soon, automatic svn upgrades will be sorted (and we'll have revision number if bottom bar) (Last update from SVN (trunk -future Tiki 5.x-): Sunday 27 of December, 2009 00:43:11 UTC - REV 24050) | ||
** However, http://tiki-trunk.mozilla.com/tiki-admin.php "reports Database Version Problem" | ** However, http://tiki-trunk.mozilla.com/tiki-admin.php "reports Database Version Problem" | ||
*I get logged out every once in a while. Perhaps the load balancers? | *I get logged out every once in a while. Perhaps the load balancers? | ||
| Line 17: | Line 17: | ||
*plugins need to be re-created (keyboard, etc) | *plugins need to be re-created (keyboard, etc) | ||
** This should be done in profiles for easy redeployment | ** This should be done in profiles for easy redeployment | ||
Revision as of 15:21, 28 December 2009
Coordination page for http://tiki-trunk.mozilla.com/ testers.
Background
tiki-trunk.mozilla.com contains real SUMO data from November 2009, on a environment similar (same?) to the real thing. The code will soon be updated daily from Tiki trunk
Notes
2009-12-28
- http://tiki-trunk.mozilla.com/ is now testable
- Very soon, automatic svn upgrades will be sorted (and we'll have revision number if bottom bar) (Last update from SVN (trunk -future Tiki 5.x-): Sunday 27 of December, 2009 00:43:11 UTC - REV 24050)
- However, http://tiki-trunk.mozilla.com/tiki-admin.php "reports Database Version Problem"
- I get logged out every once in a while. Perhaps the load balancers?
Some things to think about
- plugins need to be re-created (keyboard, etc)
- This should be done in profiles for easy redeployment