Did all the changes for you Bob, you just have to re-package the thing from branches/0.10 and upload it. :)

- David


Am 06.01.2006 um 12:12 schrieb David Zülke:

Schweet, BUT... I think you forgot to merge the changes from Veikko's branch in :>>>>>>>>> I'll do that for you quickly so you can roll another version of that release before anyone notices =)

- David


Am 06.01.2006 um 06:03 schrieb Bob Zoller:

Rolled, uploaded, verified, agavi.org updated with some helpful info.
trunk and 0.10 branch should be in sync, and I even managed to copy
and paste to tag the 0.10.1 release ;)

Let me know if anything looks wonky.

Re: lead, David, tag-you-are-it.  There has to be at least one 'lead'
to satisfy PEAR, so you're it.
Re: the non-PEAR rolls, DEFINITELY.  Even if only as a protest to
PEAR's wackiness.
Re: branches/tags/trunk - agreed.
Re: tests and your arses - tests are good, but it'd be a
pot-calling-the-kettle-black situation if I said more ;)

Thanks guys,
--Bob

On 1/5/06, David Zülke <[EMAIL PROTECTED]> wrote:
Did some more fixes to the build scripts. We should consider re-
writing them one day ;) I changed the state from alpha to beta (it
already was beta in one of them) and also added FreeBSD/OpenBSD
detection for the agavi script installation.

- David


Am 06.01.2006 um 02:24 schrieb David Zülke:

I created an 0.10 version branch and tagged version 0.10.0.
Here's teh plan:
- commit it to branches/0.10
- don't forget to merge the bugfix back to trunk ;)
- after you're done and finished packaging etc, tag the new version
by copying branches/0.10 HEAD to tags/0.10.1 (which is just one
command: svn copy svn+ssh://[EMAIL PROTECTED]/home/svn/agavi/
branches/0.10 svn+ssh://[EMAIL PROTECTED]/home/svn/agavi/tags/
0.10.1 -m "Tagging version 0.10.1"

- David

P.S.: I fixed the package tasks so they finally and hopefully will
include INSTALL and RELEASE_NOTES. I've also added Veikko and me to
the maintainers list and labeled us all "developers", at least
until someone comes up with something better ;)

P.P.S.: We maybe should have "vanilla" tarballs for 0.11 or
something, since not everyone will want to go the PEAR way.

P.P.P.S.: You guessed right, all new features still go into trunk
(and feature branches before that), the 0.10 branch remains for
bugfixes etc which, of course, should be ported back to trunk and
vice-versa. We're already at 0.10.1 right now, and maybe we'll have
to roll some more members of the 0.10 family, but let's not hope so ;)

P.P.P.P.S.: Veikko, we really need to get off our arses and write
some tests :D


Am 05.01.2006 um 16:48 schrieb Bob Zoller:

Sounds like something we need to get out there ASAP. I'll find some free time today to get that change into trunk and roll 0.10.1, though
it may not be until later tonight unfortunately.
--Bob

On 1/5/06, Veikko Mäkinen <[EMAIL PROTECTED]> wrote:
Hi,

As pointed out in http://forum.agavi.org/viewtopic.php?id=79 Agavi
0.10.0 has a bug in context.ini parsing. This is because the
ReturnArrayConfigHandler was changed to behave like it's suppose to
behave and context.ini parsing relied on the older version of
ReturnArrayConfigHandler.

We talked about this with David but fixing it has been delayed
because
of the holidays (oh yes, New Year's eve at Puerto de la Cruz,
Tenerife
was nice :). We both think that ReturnArrayConfigHandler now
works as
it's supposed to work so introducing a separate ContextConfigHandler class seemed like a good idea. So I did one (actually I just took an
older version of the ReturnArrayCH and renamed it, I'm lazy and
busy).
This is a quick and dirty fix for now, but something had to be
done. I
opened a new branch for this.

Do we like this? Is it adequate for now? When do we merge it to
trunk
and (re-)release 0.10.0? Did Santa bring lot's of presents? Did we
deserve them?


-veikko

_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev

_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev


_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev





_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev


_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev

Reply via email to