Personally, I think it makes sense that when V2.9 becomes the release version (eg replacing V2.8), V2.9 is pushed to the Debian version and master branch will need to be built from source. Only bug fixes to the released version would then be sent to Debian until lcnc releases a new version.
It would be really nice if the LCNC release schedule allowed the new version to be included each debian release on debian release day. Rod Webster *1300 896 832* +61 435 765 611 Vehicle Modifications Network www.vehiclemods.net.au On Sun, 4 Sept 2022 at 15:54, Chris Morley <chrisinnana...@hotmail.com> wrote: > I see the action with Debian package. > I hope that gets us some more exposure and more develops/users. > > I did wonder what that means for the project as far as maintaining > versions. > How are bug fixes addressed with Debian packages after (Debian) release? > > Will Debian users be directed to the forum or github for issues? > > Will it end up we have a current buildbot released version, current Debian > version and master version? > > Will having Debian force us on a time schedule? > What happens if we are not on time? > > _______________________________________________ > 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
