Moin! (north german hello) I would like to add some thoughts.
1. Releases are a must have. Think about someone having a 10000 Dollar Maschine being brocken by a Bug. I for myself am very cautious about testing new versions, as my machine has 2x 2KW servos on y-axis, easy able to tear the machine apart... 2. If there are spenders, bring them on. What about a patreon for lcnc? And payment is done in 3 tiles, one in advance, one @integration and one @release. We make a list of open things, define a price and publish them. I for myself would be OK with the one organizing getting paid for his work. 3. Mark Shuttleworth may be interested in sponsorship along with Ubuntu? I think we have the usual problem, communication issues. It the spenders and the developers would have a platform..... Best regards Julian On 11 June 2020 18:57:56 CEST, Curtis Dutton <curtd...@gmail.com> wrote: >I'm not familiar exactly with the release process as I'm a RIP guy on >all >of my machines and run master. > >One of the open source projects I work with (racket-lang) uses a >monthly >release schedule with minor releases and then a major release once per >year. They are academics and have funding so doing a monthly release >sounds >too hard. However would something along those lines be appropriate? >Perhaps >quartly or bi-annual releases? > >Is generating a release highly difficult? If so we should work on >making >that easier and ideally automatic. > >Master functionality vs 2.7 or 2.6 is a very large difference and no >matter >when the next release occurs, it is going to be painful for most users >to >upgrade. This next release will almost be more of a 3.0 than anything. >The >sooner that bandaid gets pulled off the better. > >Users need to be accustomed to frequent releases and frequent upgrades >if >not just to get them used to doing it. > >Now we definitely want RTAI in there, many users need it and linuxcnc >needs >as many users as it can get. > >Is it possible to get RTAI on a point release after the fact (unless >the >bug gets fixed sooner?) Why does the release need to be all or nothing? >Can >we do a special RTAI release later as soon as the bug gets fixed just >because it is a special case? > > > >On Thu, Jun 11, 2020 at 12:58 AM Phill Carter <phillcarte...@gmail.com> >wrote: > >> >> >> > On 11 Jun 2020, at 12:54 pm, Rod Webster <r...@vmn.com.au> wrote: >> > >> >> On Thu, 11 Jun 2020 at 12:33, Reinhard ><reinha...@schwarzrot-design.de> >> wrote: >> >> >> >> If other users have similar experiences, then a lot of precious >> developer >> >> time >> >> has been wasted on releases, that don't have much importance. >> >> I believe, that developer time spent on pushing things ahead makes >more >> >> sense, >> >> than spending it on releases. >> > >> > I think that sums it up nicely. >> > Look to the future I say! >> >> >> But I thought you were pushing for a release Rod. ;-) >> >> _______________________________________________ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers >> > >_______________________________________________ >Emc-developers mailing list >Emc-developers@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/emc-developers -- Mit freundlichen Grüßen aus Pinneberg Julian Wingert Subtilitas Consulting Holstenstr. 25 25421 Pinneberg Phone: 0170/4516094 FAX: 03212-1479681 Mail: julian.wing...@subtilitas.de USt-IdNr.: DE272503212 _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
