Re: [osg-users] Creating a annex/attic repository for old and no longer used parts of the OSG
Option 2 is better. 2016-06-20 21:16 GMT+07:00 Jan Ciger : > > > On Mon, Jun 20, 2016 at 2:13 PM, Alberto Luaces wrote: > >> Robert Osfield writes: >> >> > Thoughts? >> >> In my opinion, a new repo implies extra maintenance duties (even they >> are likely low), but cannot guarantee that it is synced or working with >> the latest OSG version, so it has a little added value. >> > > > Wasn't the entire point of having the dead code in a separate repo that it > won't need to be maintained? If someone still wants to use it, it will be > available, just not necessarily compiling with the current OSG and they > would have to put some elbow grease in it to make it work again. > > Personally I don't have an issue with it. There is little point in > spending resources on things that are not being used but still have to be > maintained only because someone could find the code potentially useful in > the future. > > I would adopt a 2 step process for it, though - mark the bits to be > removed as deprecated in version N first, including warning messages being > printed, etc. and only remove it to a separate "attic" repo in release N+x, > where x is to be defined. Not everyone that uses OSG follows the list or > updates to the current version as soon as it is released, so that should > give them an ample warning. > > J. > > > ___ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Creating a annex/attic repository for old and no longer used parts of the OSG
On Mon, Jun 20, 2016 at 2:13 PM, Alberto Luaces wrote: > Robert Osfield writes: > > > Thoughts? > > In my opinion, a new repo implies extra maintenance duties (even they > are likely low), but cannot guarantee that it is synced or working with > the latest OSG version, so it has a little added value. > Wasn't the entire point of having the dead code in a separate repo that it won't need to be maintained? If someone still wants to use it, it will be available, just not necessarily compiling with the current OSG and they would have to put some elbow grease in it to make it work again. Personally I don't have an issue with it. There is little point in spending resources on things that are not being used but still have to be maintained only because someone could find the code potentially useful in the future. I would adopt a 2 step process for it, though - mark the bits to be removed as deprecated in version N first, including warning messages being printed, etc. and only remove it to a separate "attic" repo in release N+x, where x is to be defined. Not everyone that uses OSG follows the list or updates to the current version as soon as it is released, so that should give them an ample warning. J. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Creating a annex/attic repository for old and no longer used parts of the OSG
Robert Osfield writes: > Thoughts? In my opinion, a new repo implies extra maintenance duties (even they are likely low), but cannot guarantee that it is synced or working with the latest OSG version, so it has a little added value. Removing things at the point they were working is a good aid for interested people to see what changed in OSG since that date when trying to port again those features into a recent branch. -- Alberto ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] Creating a annex/attic repository for old and no longer used parts of the OSG
Hi All, I would like to trim down the core OpenSceneGraph so it no longer has dead/unused components. One such example is the DW (Designer Workbench) plugin that I wrote about last week, and got zero replies for anyone with any interest in using it, I could just remove this dead code with the knowledge it's still in the older branches of the OSG - like OSG-3.4 and previous release, or I could create a separate repository that will place parts that the bulk of the community no longer need but some niche users may want to cherry pick from. Personally I'm happy to just keep my life simply and remove the no longer used parts safe in the knowledge that they can be cherry picked from the older branches if need be. However, I'm open to placing this no longer parts out to a dedicated repository to be maintained by community. Thoughts? Robert. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
