Carsten On Thu, Jun 12, 2008 at 11:14 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > ok, the honest answer is that we don't have a fixed date - it happens when > it happens :) For sure, that answer does not satisfy, so I can outline the > best case scenario.
Good answer :) > I'll adjust the notice files and the other stuff as discussed tomorrow. > Hopefully others can help with the readme files. So we should have a version > on monday or tuesday. Then we have to vote on this version in the Sling > project - the vote has to be open for 72 hours. This means we should finish > the vote by the end of next week. > As Sling is in incubation, the incubator PMC has to vote after that as well > - again for 72 hours; as it is not the best idea to hold a vote over the > week, we might start the vote on friday/saturday but leave it open for 96 > hours until tuesday/wednesday. > > Keeping the story short - the optimum would be to have the final version > around the 25th of June. But if any problems are detected throughout the > whole process, we have to restart it from the beginning! Which adds approx. > 10 to 14 days each time! Thanks, that helps me a lot. Does that mean that the compiled release (*) will be available in maven repositories also around 25th June in the best case? > So the best thing is that people help with getting it right the first time > (well, it's the third time actually...) and help getting the readme's done, > add docs, check the notice files after I change them and report potential > problems before I will build the release candidate. Fair enough. Thanks for your hard work on this. Regards, Greg (*) I know Apache projects release source code, and the built binaries are just to help the users. This are indeed very helpful for us consumer of this technology.
