Hey Sharan, > how hard would it be to create a release?
For Kibble-1, cutting out a release in terms of ASF should be pretty easy (create release tag in Github, prepare sources, verify and vote). For the old version we should probably also release kibble-scanners. Tricky part can be if we would like to add some convenience packages (for example to make Kibble pip installable) as this would require some additional work. Cheers, Tomek On Thu, 23 Sept 2021 at 14:18, Sharan Foga <sha...@apache.org> wrote: > Hi All > > A while ago I responded to a question from the ASF about the date of our > last release [1] and the answer was that Kibble has never done one. Kibble > was created as a TLP so bypassed Incubator where we would have had to > create at least one. We have interest in the project from within Apache, > also from CHAOSS saying that we can be apply to become a reference software > that implements some of their metrics (which I think will give the project > some great visibility!). We also have some users out there - I know > specifically of Project Jupyter. > > With no release information - it can be difficult for existing and new > users to have a stable base to explore the project from. We do have our > Live Demo but I have no idea whther the version that is running is changing > as we update the code or is several months / years old. My point here is > that without having a release as a benchmark we could be missing things. > > Anyway my question is as in the subject line is - how hard would it be to > create a release? Could we use Kibble-1 since we already have the code that > is currently being run for the demo? > > If that is too hard then another option could be to do some sort of basic > release of the new Kibble - bearing in mind that we will have a mismatch > between the demo functionality and what we call our release. I am not sure > what is feasible so am opening this discussion up to the community to get > some feedback. > > So I am happy to hear people's thoughts, suggestions and creative ideas of > how we could look at approaching this. > > Thanks > Sharan > > [1] https://s.apache.org/l6z4n >
