Le 21/12/15 17:14, Shawn McKinney a écrit : > Hello, > > It has been some time since we’ve released fortress, over 8 months, and it > has only core and not the others. Since that time there have been many > enhancements and fixes that should be made available. > > I am proposing that we increase the frequency of releases to the apache > directory fortress sub-projects. In the past, before moved to apache > directory, we released around once a month. That is probably too frequent, > but 5 or 6 times a year sounds about right to me.
Once a month is fine, but if the code base is consolidated already, it makes sense to release less if there is no urgency. The important thing here is : release when it's ready (and it can be every week, or every 6 months). At The ASF, we think that releasing often is somehow a proof that the project is alive and kicking. It's just a matter of dining the right pace though ! > > That being said, I don’t believe a release means that everything is perfect > in the code base. WHATTT ??? :-) > There are many things that fortress ‘should do’ but that must not get in the > way with having the best possible working code available for our community. That would be interesting to open discussions on the ML aboit what should be added in Fortress. We have a few people that seems interested in Fortress now, and I'm sure that feedback from teh community might help to decide what is important and what can be differed. > > The problems we face: the only way to use (apache directory fortress) realm, > rest and web is by downloading source and building locally. We have to offer a way for users to just download jars or binary, as a courtesy to them. > > So what do you say - can we get the next full release done sometime in the > next weeks? I'm your man. I just cut a release for MINA, the LDAP API and ApacheDS last week, so a few more are not frightening me. That would also be the perfect occasion to document the process for anyone here to cut a release.
