Christian Stimming [EMAIL PROTECTED] writes:
Hence, I'd suggest to branch off the stable 2.2 branch now (or: within the
next few weeks), and merge the csv-importer branch into trunk directly after
that so that more people can have a look at the importer code.
+1.
--
...jsled
http
The subject says it all: The CSV importer in the csv-branch looks good enough
to be merged into our developement trunk. However, it still needs some work
here and there, which is why it shouldn't be merged into the trunk branch as
long as we are still releasing 2.2.x releases from it.
Hence
says it all: The CSV importer in the csv-branch looks good
enough to be merged into our developement trunk. However, it still needs
some work here and there, which is why it shouldn't be merged into the
trunk branch as long as we are still releasing 2.2.x releases from it.
Hence, I'd suggest
Hi Christian,
Am Sonntag, den 07.10.2007, 23:04 +0200 schrieb Christian Stimming:
The subject says it all: The CSV importer in the csv-branch looks good enough
to be merged into our developement trunk. However, it still needs some work
here and there, which is why it shouldn't be merged
Quoting Andreas Köhler [EMAIL PROTECTED]:
What do you think?
+1, as it seems to help development. We/I could do the branching
whenever you like. BTW, are you doing the merge then?
I think that if the CSV branch is ready to merge then we should make
the 2.2 branch and then merge CSV into
Benjamin Sperisen [EMAIL PROTECTED] writes:
Anyway, most of what I've done has been to address the shortcomings
discussed earlier.
Benjamin, congrats on a pretty successful Summer of Code project. The
importer is looking (and working) pretty well.
First, I've reworked the internal error
Hi everyone,
Sorry for the long silence from my end! I just committed the work I've
done over August in a big chunk. I should have committed it in smaller
increments, but the main reason I refrained was that for much of the
time it was in a not-so-functional state. :-( I guess this is a lesson
in
