file shuffling

[Marcus Sorensen <sh...@gmail.com>]

I just need to blow off some steam about the shifting sands of our
codebase.  I went to look at the resizeVolume method today and found
that it has moved again, twice in about six months. It went from
StorageManagerImpl.java in 4.1 to VolumeManagerImpl.java in 4.2, and
now VolumeApiServiceImpl.java in 4.3. I assume sometime soon it will
move again from com.cloud.storage to org.apache.storage or something.
I'm hoping that change is progress, but between this and knowing of at
least two occasions where features/patches simply disappeared because
a file re-org branch was merged in that ignored any changes
post-branch, I begin to wonder why in the heck things keep getting
moved around and how much thought is being put into the consequences.

Re: file shuffling

[Chiradeep Vittal <Ch...@citrix.com>]

Been frustrating, I agree. History should not be lost and merges should
not be squashed!

On 11/22/13 7:37 PM, "Marcus Sorensen" <sh...@gmail.com> wrote:

>I just need to blow off some steam about the shifting sands of our
>codebase.  I went to look at the resizeVolume method today and found
>that it has moved again, twice in about six months. It went from
>StorageManagerImpl.java in 4.1 to VolumeManagerImpl.java in 4.2, and
>now VolumeApiServiceImpl.java in 4.3. I assume sometime soon it will
>move again from com.cloud.storage to org.apache.storage or something.
>I'm hoping that change is progress, but between this and knowing of at
>least two occasions where features/patches simply disappeared because
>a file re-org branch was merged in that ignored any changes
>post-branch, I begin to wonder why in the heck things keep getting
>moved around and how much thought is being put into the consequences.