The rationale behind this is that we put a lot of effort in making oak-segment-tar independent from the release process of Oak and I want to keep it this way.
oak-segment-tar should be releasable at any time. If I had to launch a quick patch release this morning, I would have to either revert your commit or postpone my release until Oak is released. Please don't let Oak impact the way we decided to manage oak-segment-tar. On Jun 29, 2016 9:25 AM, "Chetan Mehrotra" <[email protected]> wrote: > Hi Francesco, > > On Wed, Jun 29, 2016 at 12:49 PM, Francesco Mari > <[email protected]> wrote: > > Please do not change the "oak.version" property to a snapshot version. If > > your change relies on code that is only available in the latest snapshot > of > > Oak, please revert this commit and hold it back until a proper release of > > Oak is performed. > > I can do that but want to understand the impact here if we switched to > SNAPSHOT version? > > For e.g. in the past we had done some changes in jackrabbit which is > need in oak then we had switched to snapshot version of JR2 and later > reverted to released version once JR2 release is done. That has worked > fine so far and we did not had to hold the feature work for that. So > want to understand why it should be different here > > Chetan Mehrotra >
