Re: Version Naming

From: "Lukas Smith" <smith@backendmedia.com> > Marcos Neves wrote: > > > Excelent!!! > > What about an expire date to every package be update. > > I think one month is enouth. > > I have heard other people also say that they would prefer to have > deadlines by which a given proposal must be applied to a given package. > I dont think however that this is really necessary. What do other people > think? One thing that would be rather important would be to determine a proper api version method. Iirc, current methods usually rely on a float, but it should probably be an array. I think it would be helpful to require an apiVersion method for all packages, which would, of course, require them to be updated pretty soon. There could be a deadline set for that. But I don't think we need a deadline for version changes -- current packages still work, even if there are benefits to the new system. That said, it would be a good idea to wait until the handling for ex-maintainers has been implemented before forcing new releases, so that it can all be done in one swoop. Klaus