pivot-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roger L. Whitcomb" <Roger.Whitc...@actian.com>
Subject Version question
Date Fri, 03 May 2013 22:59:56 GMT
I've identified the first post-2.0.3-release-attempt bug that I'd like
to fix (PIVOT-905 <https://issues.apache.org/jira/browse/PIVOT-905> ).
So, the questions for consensus opinion are these:

1.       Should we go ahead and update "branches/2.0.x" for build 2.0.4,
and fix this bug for this next version?

2.       Or just leave "branches/2.0.x" as 2.0.3, and potentially retag
2.0.3 with some more changes (including this one)?

3.       Or should I just fix in "trunk" and leave 2.0.3 as-is until we
figure out what the next version is going to be?

 

We (my company) are probably going to switch to 2.1.0 (that is, "trunk")
fairly soon (say within a month) because of the Remote File Browser
functionality (using Common VFS) that I'm working on there.  But, given
that the 2.0.3 vote didn't pass, I think I'm open to retagging and
redoing that version with a few more fixes....  But, I could live with
any of the above solutions depending on what others think.

 

So, any thoughts?  Questions?

 

Thanks,

~Roger Whitcomb


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message