All -
Next week, we will be branching for the next release of Knox and begin the
evaluation of outstanding issues that need to get into 0.5.0.
We will then need to starting thinking about the theme and major features
for the next release.
There are a number of exciting features in the wings that
We can certainly consider that, Ed!
The plan is to branch for the 0.5.0 release around the end of the month.
If we can get the patch contributed before that then will be easier to make
it into the release.
After the branching we will likely be more conservative about patches
applied to the release
I would really like to get the SSH tunnel functionality that we've been
working on into 0.5.0.
Can we get KNOX-250 added to the target? I've been a bit short on time to
integrate it back into the master branch and make some updates that Larry
has suggested, but hopefully I can in the coming week o
Folks -
I'd like to summarize a brief conversation that Kevin and I had today
regarding release planning.
* We should look to branch for a release around the end of August and will
need to scope the release effort with that timeframe in mind
* incompatible changes like repackaging everything will
Seems like they should be done at the same time to me.
Is there some reason that they should be separated in terms of risk of
completion or something else?
On Tue, Aug 5, 2014 at 1:59 PM, Kevin Minder
wrote:
> Should we consider the maven groupId change separately from the package
> name chang
Should we consider the maven groupId change separately from the package
name change?
On 8/5/14 1:58 PM, larry mccay wrote:
Yes - that is a good point and should be done regardless of version
designation but certainly if we are to go with a 1.0.
On Tue, Aug 5, 2014 at 12:37 PM, Kevin Minder
w
Yes - that is a good point and should be done regardless of version
designation but certainly if we are to go with a 1.0.
On Tue, Aug 5, 2014 at 12:37 PM, Kevin Minder
wrote:
> One important consideration for our next release should be changing at
> least our maven groupId and possibly our pack
One important consideration for our next release should be changing at
least our maven groupId and possibly our package structure to
org.apache.knox. I had always considered this a step we would take as
part of a 1.0 release.
On 8/5/14 12:24 PM, larry mccay wrote:
Folks -
I think it is time
Folks -
I think it is time that we begin talking about the next release for Apache
Knox.
There are quite a few fixed and outstanding jiras that would be candidates
for this release.
We will need to determine a couple things:
1. Version numbering for the release. I believe that we have a couple
