Hi,
Does 0.2.x mean that is not created from trunk but from the 0.2 branch
(that is created from the 0.2 tag)? If this is the case, do we have to
merge specific changes from trunk? Or what is exactly the idea?
Ferdy
On Mon, Jul 23, 2012 at 11:12 PM, Kazuomi Kashii kazu...@kashii.net wrote:
+1
0.2.1 or 0.3 really depends on what we are going to ship. If we are just
shipping the improvements of our existing modules, then I say it should be
0.2.1.
If we are going to give the gsoc stuff to the world then it should be a 0.3.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Ah ok. So let's see if I got this right:
Even though we might be calling it 0.2.1, we can still use trunk for the
release. So the version number is just a semantic to indicate if it is a
minor or major release. (The latter typically introducing major features or
incompatibilities). 0.2.1 does not
I would suggest rolling the Avro release as a new minor version, but
weather or not its 0.3 or 0.4 I don't see as being a big issue.
On Tue, Jul 24, 2012 at 8:56 AM, Lewis John Mcgibbney
lewis.mcgibb...@gmail.com wrote:
Hi,
On Tue, Jul 24, 2012 at 11:19 AM, Ioannis Canellos ioca...@gmail.com
OK coming back to this then
Henry put either 0.2.1 or 0.3 into the picture are there any preferences???
Personally over the last while my feelings have switched slightly and
there are a few events which have caused this.
1) gora-cassandra has been pretty well turned up side down, totally
Sorry I was not clear enough.
I did not mean make the change to the parent pom.xml to accommodate
your most recent issue. I meant just generally speaking, as that you
are officially included as a developer, committer and Gora PMC member
within the gora parent pom.
Oh and yes if you can then
+1 to roll release and I'll also throw my name into the hat to release it.
Let me know.
Thanks!
Cheers,
Chris
On Jul 5, 2012, at 12:30 PM, Lewis John Mcgibbney wrote:
Hi,
As the GSoC project is moving along nicely and it's been some 3 or so
months since the 0.2 release I was thinking
Hi Kaz,
Also please make sure to commit your details to the gora parent
pom.xml it would be great to include you in the dist when we get round
to releasing. Thanks
Lewis
On Fri, Jul 6, 2012 at 7:05 PM, Kazuomi Kashii kazu...@kashii.net wrote:
+1 for new release
1) I committed
Hi Lewis,
Did you mean CHAGES.txt ?
I think pom.xml is not required to change for GORA-143.
-Kaz
On 7/6/12 1:32 PM, Lewis John Mcgibbney wrote:
Hi Kaz,
Also please make sure to commit your details to the gora parent
pom.xml it would be great to include you in the dist when we get round
to
Hi,
As the GSoC project is moving along nicely and it's been some 3 or so
months since the 0.2 release I was thinking about drumming up support
for another (possibly even 0.2.1) release?
We have some 15 issues which have been addressed in the development
drive since 0.2 was released and I for
10 matches
Mail list logo
