[Registry-dev] Commits to Trunk

[Glen Daniels]

Deepal Jayasinghe wrote:
> We have created a branch for the release and we will be continue the
> release on the branch , however I would kindly request you all not to do
> any major changes to the trunk until we do the merging from the branch.

Hi Deepal:

Sorry, but -1 on this.  The trunk should always be available for new 
development, and we shouldn't be building anything major on a release 
branch.  Release branches are just for getting documentation and 
anything else release-specific squared away.  If you need to make coding 
changes during the (hopefully VERY short) release cycle, you should do 
so on the trunk first, and then merge those changes over to the branch - 
NOT on the branch first.

The point is: the trunk should always reflect the latest changes, and 
there should never be new work happening on a release branch.  (Clearly 
that's different for experimental branches)

This is just like what we're doing now for Axis2, and it's going to be 
really important as we follow a "release early, release often" cycle 
with the early versions of the Registry.

Sound ok to you?  If anyone has issues with this, please let's discuss 
them now.

Thanks,
--Glen