Repo and Release management With David and Glen's departure from att, is anybody within att actively leading the development of ast and/or ksh as I believe they were able to manage this during work time and I imagine that they don't have as much time for this now?
There are a number of open issues and some pull requests in github but no responses have been made so I guess most are wondering what is happening. Could somebody external to att be allowed to at least manage the repo to tag releases and label and assign issues to people? It would also be nice to have a roadmap of what is planned (or hoped for). I have a few ideas for ksh that I am hoping to put forward myself soon and it would be nice to get feedback for such feature requests. Automated Regression Testing Does att have an internal build environment for automated regression and cross-platform testing after commits? If not, would att be open to at least providing this to encourage external contributions? So that perhaps git commits trigger automated build testing? Documentation Could att just upload the documentation source to github so that it can be edited from git and host it again somewhere, pulling the source from github automatically when it is updated? Note for anyone interested, it's browseable on wayback here: https://web.archive.org/web/20151104235435/http://www2.research.att.com/~astopen/download/ I don't know if the downloads will work, but this link sets up the frames properly for browsing. Which also reminds me: are the old binary downloads going to be made available on github as well? -- Regards Danny _______________________________________________ ast-developers mailing list ast-developers@lists.research.att.com http://lists.research.att.com/mailman/listinfo/ast-developers