On Thu, Nov 29, 2012 at 10:34 PM, Dali Liu <[email protected]> wrote:
> Hi Rob, > > Thank you for the guidance. > The plan is very clearly. > I have submit a cwiki request, I would like to put this plan and the task > check list to our wiki page, then we will clear to know where we are. > And I purpose that we freeze our codes by the end of first week in Dec. > 2012/12/07. Is this time ok for every one? Yes, this is a good plan. I will volunteer to communicate it more broadly once we are completed. This is an excellent way to finish 2012 and demonstrate that there good progress with this project. > > 2012/11/20 Rob Weir <[email protected]> > > > On Mon, Nov 19, 2012 at 3:39 AM, Dali Liu <[email protected]> wrote: > > > Following the guide there are many todo items, I will try to find a > place > > > to track the to-do items, I will start from the technical ones. > > > > > > So what's our target date? how about one month later? Maybe some day > > around > > > 12/20? > > > > > > > The process requires a 72 hour vote in the Podling, and then another > > 72 hour vote in the IPMC. If problems are found it can take longer. > > So I'd plan for the release process -- once we have built the final > > "release candidate" build to take two weeks. > > > > So a release plan might look like: > > > > 1) Get remaining fixes and features into trunk > > > > 2) testing/verification of code, tests, releases notes, etc. ===> this > > leads to release candidate > > > > 3) Release candidate signed and posted for vote > > > > 4) 72 hour PPMC vote on release candidate ==> 72 hour IPMC vote > > > > 5) Release upload and announcement > > > > So I think steps 3-5 will take around 2 weeks. > > > > So we could work backwards from that and suggest a code freeze date. > > > > To me the date is not critical. December 20, December 30, January 15, > > it is all good. > > > > Is there anything we can do in JIRA to mark which bugs should be > > included in our next release? That way we can track what work > > remains. > > > > -Rob > > > > > 2012/11/15 Rob Weir <[email protected]> > > > > > >> On Wed, Nov 14, 2012 at 10:23 PM, Dali Liu <[email protected]> > wrote: > > >> > Hi Rob, > > >> > > > >> > I think that a new release is needed for users of ODF toolkit. I > > would > > >> > like to be a volunteer for the Release. > > >> > Because I didn't know much about the release process, can you guide > > me on > > >> > this? > > >> > > > >> > > >> Our second release should be much easier than the first one. > > >> > > >> Devin wrote up some instructions here: > > >> http://incubator.apache.org/odftoolkit/odftoolkit-release-guide.html > > >> > > >> As you can see, it is a mix of activities. Some are technical, some > > >> are process, like the voting steps. > > >> > > >> I'll try to help as well. > > >> > > >> I'd be interested in knowing what Florian and Svante think. Can we > > >> aim for a date? > > >> > > >> -Rob > > >> > > >> > > > >> > 2012/11/14 Rob Weir <[email protected]> > > >> > > > >> >> Our last release was in January. Does anyone want to have another > > >> >> release, say at the end of the year? > > >> >> > > >> >> We have a lot of bug fixes, and some new features, especially in > the > > >> >> Simple API. > > >> >> > > >> >> Nothing stunning, but that is the nature of the project. Our > > >> >> functionality is boxed in by the ODF schema. We evolve by > perfecting > > >> >> the code, improving performance, improving documentation, etc. But > > >> >> our next "leap forward" might not come until ODF 1.3 is done. > > >> >> > > >> >> If we want to do a release we want need to agree on "feature > freeze" > > >> >> deadline, a stabilization period for testing and updating release > > >> >> notes, etc. And we would also need a volunteer to be Release > > Manager. > > >> >> > > >> >> What do you think? > > >> >> > > >> >> -Rob > > >> >> > > >> > > >
