Commit Graph

18 Commits

Author SHA1 Message Date
Geoff Humphrey
73e158028f Preliminary 2.3.2 commits. Updated navigation schemas and bug fixes. New theme. 2010-02-05 18:37:27 +00:00
Geoff Humphrey
66848ea1dd 2010-01-20 00:49:05 +00:00
Geoff Humphrey
650d2047bd 2010-01-19 22:39:07 +00:00
Geoff Humphrey
ea7bd6d6be 2010-01-19 22:38:50 +00:00
Geoff Humphrey
411b0f805b Finalizing 2.3.1 release. 2010-01-19 18:17:54 +00:00
Geoff Humphrey
6d6577f155 Bug fixes. 2010-01-05 22:02:57 +00:00
Geoff Humphrey
dec14835eb Minor additions: yeast info popup for bb/recipe display; narrow recipe and bb lists by style with a click on a certain style; fixed some inconsistencies in the db_connect_log.inc.php file. 2010-01-05 21:44:17 +00:00
Geoff Humphrey
279b5ea8cb Finalizing 2.3.1 sub release. Fixed bug where brewBoilTime in the recipes table was not being recorded to the DB. 2009-11-14 00:14:09 +00:00
visual77
c230ddc702 added a basic kohana system to be fleshed out into a nrew brewblogger 2009-11-06 06:00:53 +00:00
visual77
519ac81824 removed some of the repeated code in place of for loops using variable variables for iteration 2009-10-27 14:58:22 +00:00
Geoff Humphrey
2e05236c35 2009-10-27 12:02:04 +00:00
visual77
a8e1dfbed6 put the SQL installation script in with the trunk so the entirety of brewblogger is clustered in the repository 2009-10-17 03:27:13 +00:00
visual77
89b9b4f575 Restructured the repository to follow the more traditional SVN structure.
The trunk folder is for all new features that are not yet ready for release. This folder will be for stabilizing work as it is built and creating new features.

The releases folder is used for release builds. The earliest available build is 2.3.x, and thus it will have the 2.3 folder. All maintenance and bug fixes go in this folder. No new features whatsoever are to be added in here, keeping those completely in the trunk. When the trunk is ready for the next version, it will have a new folder created for it (releases/2.4 for instance) to stabilizing for final release.

The tags folder is used for individual releases. When a release build is ready to go out for download, that release folder will be cloned into an appropriate tag folder. For example, the releases/2.3 folder will be cloned into tags/2.3.1 for that release, and after more work on bug fixes, it will be cloned to tags/2.3.2. Thus, these tag folders should never be modified for any reason. The tag exists purely as a snapshot of a certain point on the release path, and to modify a snapshot defeats the purpose. Any bug in a tagged release should be fixed in the appropriate release folder (such as releases/2.3 for a bug found in 2.3.1).
2009-10-16 22:09:45 +00:00
Geoff Humphrey
cd7bc1b0e9 2009-10-16 20:22:56 +00:00
Geoff Humphrey
3cb22671db 2009-10-16 20:04:26 +00:00
Geoff Humphrey
95448c3cf3 2009-10-16 16:23:38 +00:00
Geoff Humphrey
f9b88c086f 2009-10-16 15:57:59 +00:00
Unknown Author
d1e9000430 Initial directory structure. 2007-11-26 03:10:39 +00:00