Hi all, I agree with Ken in that we should work towards milestone-based releases rather than strictly using date-based releases. Another approach would be regular date-based releases with each containing a milestone project such as Nemeth support and so on. For example, we could say we should release a major release around Fall, then release bug fixes (after a test period) every quarter. The feature set could be as follows: * Major release (Fall): major milestones reached which forms the basis for improvements throughout the year. For example, we could work on a milestone for UEB support slated for a Fall release, and should be included in the fall release if it has gone through various testing phases. * Winter/Spring: Bug fixes and other milestones (if these were not ready for fall release). * Summer: mainly bug fixes and base code for next milestone. These would work for both sides: having date-based releases would guarantee that table maintainers are aware of when to submit improved tables, and using milestone-based releases (at least once a year) would guarantee that the code had sufficident testing period. So may I propose an alternate dates for some new release please: * 2.5.4: I'd go with Christian's deadline for now. * 2.5.5: Some time in May 2014 with bug fixes and milestones. * 2.5.6: July 2014 with bug fixes. * Possibly 2.6: Some time in October 2014 to include various milestones and improvements. Another option is to release the new versions every 4 months or so like: * 2.5.4: Christian's deadline. * 2.5.5: June 2014. * Possibly 2.6: October 2014. Any thoughts on this? Thanks. Cheers, Joseph -----Original Message----- From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry Sent: Thursday, January 9, 2014 10:50 AM To: liblouis-liblouisxml@xxxxxxxxxxxxx Subject: [liblouis-liblouisxml] Re: Proposal for next liblouis release date I am fine with goals I do not like dates. I would be fine if John said we will release when Nemeth support is working, or we will release when the bugs in back_translation is working. My problem with a date is if no one did anything worthwhile from this point till march we might have more unstable code than finished code being released as a product for people to use. I realize that is an extreme example but I would just like a list of things that will be finished for this release. Ken -----Original Message----- From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Keith Creasy Sent: Thursday, January 9, 2014 8:38 AM To: liblouis-liblouisxml@xxxxxxxxxxxxx Subject: [liblouis-liblouisxml] Re: Proposal for next liblouis release date I agree Ken but there have to be goals for when a product is released or the release never happens. This is especially true of something like LibLouis where constant changes are happening. There is always one more thing. What I like to do is set a date and then decide what we want to be in that release. Those become the milestones and then the release date can be adjusted if necessary based on progress toward the milestones or goals. -----Original Message----- From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry Sent: Wednesday, January 08, 2014 11:34 PM To: liblouis-liblouisxml@xxxxxxxxxxxxx Subject: [liblouis-liblouisxml] Re: Proposal for next liblouis release date I want to state for the record I would rather see releases based on mile stones than dates. I know I have no say in this at all but I find picking a date and saying I will release now no matter what is in or not in, working or not working is an odd way to do software. -----Original Message----- From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Mesar Hameed Sent: Wednesday, January 8, 2014 8:48 PM To: liblouis-liblouisxml@xxxxxxxxxxxxx Subject: [liblouis-liblouisxml] Re: Proposal for next liblouis release date Hi Christian, Sorry for not replying sooner: On Mon 23/12/13,14:28, Christian Egli wrote: > I'd like to release version 2.5.4 of liblouis early next year, let's > say Friday 2014-1-17. We are due a release on the 1st March, 2014, just before the spacing param is removed. //www.freelists.org/post/liblouis-liblouisxml/Eliminating-the-spacingpa rameter Does this mean we will have two releases in quick succession? I would prefer if we could delay until the 1st, there are some major improvements for the Danish tables that Bue and I are keen to see made available in a release, but it will most likely not be doable by 17th Jan. 1 March is more doable for us. thoughts? thanks, Mesar For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com