+1
On Thu, Dec 20, 2012 at 11:03 AM, Brandon Williams dri...@gmail.com wrote:
+1
On Dec 20, 2012 4:58 AM, Sylvain Lebresne sylv...@datastax.com wrote:
There was a few quacks with rc1 (most notably #5064) but we've fixed
those,
so I propose
the following artifacts for release as
+1
On Saturday, December 29, 2012, Pavel Yaskevich wrote:
+1
On Saturday, December 29, 2012 at 2:14 PM, Yuki Morishita wrote:
+1
On Saturday, December 29, 2012, Jason Brown wrote:
+1
On Dec 29, 2012 9:31 AM, Vijay vijay2...@gmail.com
javascript:;(mailto:
+1
On Fri, Jan 25, 2013 at 2:53 AM, Sylvain Lebresne sylv...@datastax.comwrote:
That list of changes since 1.2.0 is getting pretty long, time to ship that
to
users. I propose the following artifacts for release as 1.2.1.
sha1: 8540974dbd26989b1cd72608b06e57ebe053bf38
Git:
+1
+1
On Mar 14, 2013 6:05 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Some important bug fixed since 1.2.2, I propose the following artifacts for
release as 1.2.3.
sha1: f07804e0d0cf57bc6e1e2924a7b926d55408f640
Git:
+1
On Apr 8, 2013, at 1:55 PM, Sylvain Lebresne sylv...@datastax.com wrote:
A fair enough number of bugs fixed since 1.2.3, I propose the following
artifacts for release as 1.2.4.
sha1: 2e96d07114dc88f85e56d88f7322a6b91da36c0d
Git:
+1
On Fri, May 3, 2013 at 2:21 PM, Sylvain Lebresne sylv...@datastax.comwrote:
A fair enough number of bugs fixed since 1.2.4, I propose the following
artifacts for release as 1.2.5.
sha1: de98541708b9a59e918029bb3ed50b0d986d24be
Git:
+1
On Mon, May 6, 2013 at 4:15 AM, Sylvain Lebresne sylv...@datastax.comwrote:
Now that the offending tickets have been committed (#5432 and #5535), let's
re-roll this. So I propose the following artifacts for release as 1.2.5.
sha1: 59bd0e7169c5fabc0e734ccbbbcd6964709577d0
Git:
+1
On Wed, May 15, 2013 at 10:16 AM, Sylvain Lebresne sylv...@datastax.comwrote:
Hopefully third times the charm. The #4860 fix has been committed so I
propose
the following artifacts for release as 1.2.5.
sha1: 7d4380d661e7bbf3ec075b069cf2c22e9b87375f
Git:
+1
On Wed, May 22, 2013 at 5:06 AM, Sylvain Lebresne sylv...@datastax.comwrote:
I propose the following artifacts for release as 1.1.12.
sha1: 0db94069550b9c38b9f749e2087b196bb519664e
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.1.12-tentative
+1
On May 23, 2013 4:03 AM, Sylvain Lebresne sylv...@datastax.com wrote:
I propose the following artifacts for release as 1.1.12 (now with more
#5488 fixes inside).
sha1: 2dd73d171068d743befcd445a14751032d232e4e
Git:
+1
On Jun 22, 2013 12:46 PM, Sylvain Lebresne sylv...@datastax.com wrote:
The previous assertion error has been fix so I propose the following
artifacts
for release as 1.2.6.
sha1: 043a63c63b92b0bf68047da6b5e379da35f3c688
Git:
+1
On Tue, Jul 9, 2013 at 5:20 AM, Sylvain Lebresne sylv...@datastax.comwrote:
Cassandra 2.0 is coming along but we now need wider testing. So I propose
the
following artifacts for release as 2.0.0-beta1. Let it be clear that it is
only
a beta (and the first one at that), so we know it's
+1
On Monday, July 22, 2013, Sylvain Lebresne wrote:
A healthy amount of bugs have been found since beta1, so let's release a
new
beta to shake out the remaining ones before a RC. I thus propose the
following
artifacts for release as 2.0.0-beta2
sha1:
+1
On Tuesday, July 23, 2013, Sylvain Lebresne wrote:
Quite a few bugs fixed since 1.2.6, I propose the following artifacts for
release as 1.2.7.
sha1: ae62c947fc245295785324502bf6bc2c1c8477f9
Git:
+1
On Wed, Jul 24, 2013 at 12:21 PM, Sylvain Lebresne sylv...@datastax.comwrote:
So, now with some CASSANDRA-5799 inside, I propose the following artifacts
for
release as 1.2.7.
sha1: ce4e4b9b5b29b0e0518aafe02544de3765ea9dd7
Git:
+1
On Jul 27, 2013 9:17 PM, Eric Evans eev...@sym-link.com wrote:
A regression made its way into 1.2.7 and has since been fixed [2]; I
propose the following artifacts for release as 1.2.8.
Git SHA1: 0291d696018214000709025c0b806089c2f51e97
Git HTTP:
+1
On Mon, Aug 5, 2013 at 12:54 PM, Eric Evans eev...@sym-link.com wrote:
Sounds like it's that time; I propose the following artifacts for
release as 2.0.0 rc1.
Git: 2.0.0-rc1-tentative / e8ae672
Gitweb:
https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=e8ae672
+1
On Monday, August 26, 2013, Sylvain Lebresne wrote:
The changelog is getting big, I propose the following artifacts for release
as 1.2.9.
sha1: ae62c947fc245295785324502bf6bc2c1c8477f9
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.9-tentative
+1
On Fri, Mar 7, 2014 at 10:52 AM, Sylvain Lebresne sylv...@datastax.comwrote:
We're starting to have a really big changelog so I propose the following
artifacts for release as 2.0.6.
sha1: 656edc529db59f0002a7fb0eed93339071fd3974
Git:
Spark has been using the GitHub PRs successfully; they have an additional
mailing list which contains updates from GitHub (
http://mail-archives.apache.org/mod_mbox/spark-reviews/), and they also
have their PRs linked to JIRA so that going from the ticket to the PR is
easily done.
If we are going
21 matches
Mail list logo
