[chirp_devel] Features and Bug Fixes
I have a question about the process.
Am I supposed to close Feature/Bug tickets after I submit a patch or is that handled by someone/something else? I don't want to leave clutter lying about.
-- wireless Joseph.P.Scanlan@n7xsd.us +1-702-896-0507 -- work Joseph.P.Scanlan@ClarkCountyNV.gov +1-702-455-3679
On Tue, Dec 22, 2015 at 10:48 AM, Joseph scanlan via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
I have a question about the process.
Am I supposed to close Feature/Bug tickets after I submit a patch or is that handled by someone/something else? I don't want to leave clutter lying about.
You can close them as soon as they make it into a build. Sometimes I give it an extra few days for users to report issues (though they can continue to do this when it's closed).
Let Dan know if you need permission.
Tom KD7LXL
Hi,
Following Tom logic, the issue #2169 must be closed by now, as the driver is in the daily build for about a month and no user's issues are detected. I submitted a patch about it yesterday with new models and PEP8.
And I need permission to manage the issue #2999 which I started, I will be updating it soon with the first workable driver, I'm working on PEP8 & testbed
This first version can handle memory operations but no settings yet.
Holiday season greetings to all.
El 22/12/15 a las 14:05, Tom Hayward via chirp_devel escribió:
On Tue, Dec 22, 2015 at 10:48 AM, Joseph scanlan via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
I have a question about the process.
Am I supposed to close Feature/Bug tickets after I submit a patch or is that handled by someone/something else? I don't want to leave clutter lying about.
You can close them as soon as they make it into a build. Sometimes I give it an extra few days for users to report issues (though they can continue to do this when it's closed).
Let Dan know if you need permission.
Tom KD7LXL _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
> Following Tom logic, the issue #2169 must be closed by now, as the
driver is in the daily build for about a month and no user's issues are detected. I submitted a patch about it yesterday with new models and PEP8.
And I need permission to manage the issue #2999 which I started, I will be updating it soon with the first workable driver, I'm working on PEP8 & testbed
You should be good for any and all issues now, let me know if not.
Thanks!
--Dan
Dan,
I have tickets I want to close. Do I have access?
-- wireless Joseph.P.Scanlan@n7xsd.us +1-702-896-0507 -- work Joseph.P.Scanlan@ClarkCountyNV.gov +1-702-455-3679
participants (4)
-
Dan Smith -
Joseph scanlan -
M.Sc. Pavel Milanes Costa -
Tom Hayward