There is no commitment on dates, the dates on the website are just tentative dates. We do not follow a Beta/RC1/RC2 cycle, nor we have a predefined list of planned tickets to be resolved.
However I think it is good time to prepare for the publication of the new release, since the stabilization phase has been pretty long already. What other think? I can prepare the release artifacts and start a vote in a few days if we are all ok. Jacopo On Sep 19, 2014, at 3:49 PM, Ron Wheeler <[email protected]> wrote: > I am new here but since I started to get active Release 13.07 has missed 2 > published release dates. > I have also found out that some people are already using it in production > environment and are starting to worry about changes to 13.07 data structures > and functionality that are being suggested as part of "bug fixes" to 13.07 as > part of the release. > > Beta, RC1, RC2 planned? > Is there a list of tasks that need to be done to release the first 13.07 > release which is currently scheduled for next week? > Have they been assigned and accepted? > When will they be completed? > There seems to be a lot of spare energy in the group at the moment and it > would be good to channel it into getting the release done. > > Are there documentation or other non-coding tasks that need to be finished? > > I understand that this is an open source project with volunteers but there > still needs to be some commitment to dates. > They may slip but it should be absolutely clear why they slipped and a > commitment from the PMC to see that the revised dates are met once the PMC > has published the new dates. > > > -- > > Ron Wheeler > President > Artifact Software Inc > email: [email protected] > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 >
