Yes, I agree. We apparently made the false assumption that shared is already stable enough to freeze and start releasing. Mario is right I think. Perhaps we should postpone the release process and work in trunk until we really have a stable state.
Manfred On 3/9/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > Hi! > > If a patch is critical enough that it has to be put into a release > > branch, then someone needs to make the time to insure it's merged > > correctly -- and this hopefully is the exception rather than the rule. > > Either that, or a new branch is needed. > > > > Branches should be static once created so that development can > > continue in full force on the trunk. > > > This is not that different to what sean tries to archive, no? > > I may ask if its the right time to start with the release now. > > We have a rather young module myfaces-shared and uncover problems with > it every day. > I think we have to put every effort into shared so that it is clean in > two weeks - and avoid any additional complexity. > > Means, we should gave us one week to fix shared (in trunk), another to > test the trunk and then to start the release. > I have no problems to drop the trunk in our internal production version > - currently this is not possible. > > Once shared is stable I am definitely +1 to do the merging stuff during > the release for the rare fixes which we need once the whole system is > more stable again - which is NOT the case currently. > > Ciao, > Mario > >
