Hi Mario, I know that it is quite an effort to keep track of the features developed on multiple branches and versions. Maybe after the enhancement requests have been discussed you could have a clearer look on what should go into 1.1 and what should be delayed for 1.2. And maybe at that point you could think of a 1.2 branch with clearly defined targets especially if you would have contributors for those features.
Regards, Robert On 11/14/05, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > > Hi! > >Agree. Will let you guys know if I have anything useful and we can put > >it in a branch first until it stabilizes.. > > > > >>And if so couldn't a separate > >>(maybe 1.2) branch be created and start developing the identified > >>features? > >>A merge into the main branch could be done later once 1.1 is released. > >> > > You know, every contribution is very welcome. > But in our current constellation its too much hassle for us (me) to > support multiple branches. > > Once I have a better feeling how it is to deal with releases and the > development/vote/release cycle is more naturally I'll consider this again. > You see how complicated it can be to get a release out ;-) > > Said that, any contribution will go into the development branch for now. > > I'll publish a list of requested enhancements on commons-dev so we can > start a discussion on it. > > --- > Mario > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
