Re: [DISCUSS] Java package change before the first ASF release?

2016-10-12 Thread Puja Valiyil
The only breaking change that I think we have had this far has been the artifacts moving to an Apache namespace. I probably would have voted against doing that too. I guess more importantly, I'd like us to get out a release soon rather than keep adding more features in. Theoretically the

Re: [DISCUSS] Java package change before the first ASF release?

2016-10-12 Thread Aaron D. Mihalik
FYI: There are already a handful of package name changes and other breaking refactoring from 3.2.9 to 3.2.10. This would be along those lines and not present any significant API changes. On Wed, Oct 12, 2016 at 8:30 AM Puja Valiyil wrote: > -1 I think we should wait. I'd

Re: [DISCUSS] Java package change before the first ASF release?

2016-10-12 Thread Puja Valiyil
-1 I think we should wait. I'd like us to have one non-breaking official release on Apache before we start adding changes that will greatly effect end users. Dramatically changing the Api seems like a bad idea since users will have no choice but to update. Theoretically once we get past the