Possibly more frequent and scheduled releases (e.g. twice a year) would be the vehicle to get more developers on board and also allow easier stabilization due to less amount of big changes. However the efforts for a release need to be small (best case zero due to automation or distribution of validation to many) for this to work out. And a master mind needs to setup schedule and organize it.
Regards (and hi, first mail) Daniel Rod Webster <[email protected]> schrieb am Di. 21. Mai 2019 um 22:17: > I'm at a bit of a loss on this really. Rene tried to Commit Reverse Run in > November 2018 and announced that on the forum thread Phill started about > his repo > > https://forum.linuxcnc.org/plasma-laser/35449-another-plasma-component?start=40#120142 > Then Rene had to revert. > > So Phill worked though every commit and merged it into his repo where its > been tested in the real world and kept it current ever since. Now all of a > sudden its pushed to one side becasue a couple in the dev team don't know > enough about it. If it was good enough back in November, shouldn't it be > good enough now particularly after it been tested on live machines? > > I find it incredibly frustrating to find road blocks that can be resolved > by merging existing branches that have sat languisihing for several years > and have then become broken because of inactivity. To my mind its not > treating the contributors respectfully and its no wonder they become > disillusioned and move away. > > New developers like Phill and Randy need to be welcomed with open arms, but > more importantly be shown respect for their work by committing it. If you > don't, then the project is likely to wither away due dwindling developers. > > Rod Webster > *1300 896 832* > +61 435 765 611 > Vehicle Modifications Network > www.vehiclemods.net.au > > > On Wed, 22 May 2019 at 02:13, Moses McKnight <[email protected]> wrote: > > > Hi Phillip, > > > > Last I heard there were issues merging reverse-run with master - so that > > is new > > to me! I tend to agree with Chris on this, but I don't know enough about > > the > > state of reverse run. There are bug fixes for the TP ready for 2.7, but > a > > lot > > of merge conflicts putting them in master currently. > > > > On 5/21/19 1:14 AM, Phillip Carter wrote: > > > I do have a separate reverse-run branch if that is up to date with > > Master (well it was of a couple of hours ago) > > > > > > https://github.com/phillc54/linuxcnc/tree/reverse-run < > > https://github.com/phillc54/linuxcnc/tree/reverse-run> > > > > > > Most probably if there are other TP updates then this will be broken… > > > > > > Cheers, Phill. > > > > > > > > >> On 21 May 2019, at 3:32 pm, Chris Morley <[email protected]> > > wrote: > > >> > > >> I feel we have be cautious with 'getter done' > > >> Each time we add some capability time is needed to properly find bugs > > and update screens configuration wizards etc. > > >> We are notorious for waiting waaay too long to make a stabilization > > branch and so feel compelled to release it too early. > > >> Particularly the configuration wizards always have bugs that show > > themselves right after release. > > >> Since we historically only build a ISO once - we are stuck with buggy > > software for newbees to endure till they update. > > >> > > >> I would suggest we have already started to go too far with the > > inclusion of python 3 code work. > > >> Our 2.8 stabilization branch should probably be made under that and > > soon. > > >> Then we should stabilize for a long time like 4 -6 months. > > >> > > >> Then we should release in another year because there is lots to add in > > that year. > > >> And that is when reverse run should go in. > > >> > > >> My 2 cents > > >> Chris M > > >> > > >> ________________________________ > > >> From: Rod Webster <[email protected]> > > >> Sent: May 21, 2019 4:22 AM > > >> To: EMC developers > > >> Subject: Re: [Emc-developers] Introduction and a couple of questions > > >> > > >> Well forum member PhillC has a working version of Reverse run in his > > git > > >> repository <https://github.com/phillc54?tab=repositories> and enough > > people > > >> have been using it to confirm it works without breaking anything. > > >> > > >> Aside from some simulations and one component (plasmac.comp), > > incorporating > > >> reverse run is the only change Phill has done to the core code and he > > keeps > > >> it up to date with master branch weekly. I think he's kept the sims > and > > >> component separate from his modified master branch code. > > >> > > >> So there is not really any excuse to leave Reverse run out. Get it > > done > > >> Andy! > > >> > > >> > > >> > > >> _______________________________________________ > > >> Emc-developers mailing list > > >> [email protected] > > >> https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > > > > > > _______________________________________________ > > > Emc-developers mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > > > > -- > > And as it is appointed unto men once to die, but after this the > judgment: > > So Christ was once offered to bear the sins of many; and unto them that > > look > > for him shall he appear the second time without sin unto salvation. > > (Hebrews 9:27-28) > > > > > > _______________________________________________ > > Emc-developers mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
