Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ISSUE_TEMPLATE: Add that bugs must be reproducible with SqlServerDsc #1036

Closed
johlju opened this issue Jan 29, 2018 · 0 comments · Fixed by #1061
Closed

ISSUE_TEMPLATE: Add that bugs must be reproducible with SqlServerDsc #1036

johlju opened this issue Jan 29, 2018 · 0 comments · Fixed by #1061
Labels
enhancement The issue is an enhancement request.

Comments

@johlju
Copy link
Member

johlju commented Jan 29, 2018

Details of the scenario you tried and the problem that is occurring:
We should add to the issue template that issues using a configuration that using the older xSQLServer must be able to be reproduced with SqlServerDsc.
This is because bug fixes are released only in SqlServerDsc, not xSQLServer.

The DSC configuration that is using the resource (as detailed as possible):
n/a

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
n/a

What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
n/a

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev
@johlju johlju added enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community. labels Jan 29, 2018
johlju added a commit to johlju/SqlServerDsc that referenced this issue Mar 10, 2018
@johlju
Changes to SqlServerDsc
73983a9 
- Updated the ISSUE_TEMPLATE to hopefully be more intuitive and easier
  to use.
- Added information to ISSUE_TEMPLATE that issues must be reproducible
  in SqlServerDsc resource module (if running the older xSQLServer
  resource module (issue dsccommunity#1036).
@johlju johlju mentioned this issue Mar 10, 2018
Merged
5 tasks
@johlju johlju added in progress The issue is being actively worked on by someone. and removed help wanted The issue is up for grabs for anyone in the community. labels Mar 11, 2018
johlju added a commit to johlju/SqlServerDsc that referenced this issue Mar 11, 2018
@johlju
Changes to SqlServerDsc
ebe5a3a 
- Updated the ISSUE_TEMPLATE to hopefully be more intuitive and easier
  to use.
- Added information to ISSUE_TEMPLATE that issues must be reproducible
  in SqlServerDsc resource module (if running the older xSQLServer
  resource module (issue dsccommunity#1036).
johlju added a commit to johlju/SqlServerDsc that referenced this issue Mar 12, 2018
@johlju
Changes to SqlServerDsc
b623b95 
- Updated the ISSUE_TEMPLATE to hopefully be more intuitive and easier
  to use.
- Added information to ISSUE_TEMPLATE that issues must be reproducible
  in SqlServerDsc resource module (if running the older xSQLServer
  resource module (issue dsccommunity#1036).
johlju added a commit that referenced this issue Mar 12, 2018
@johlju
SqlServerDsc: Update ISSUE_TEMPLATE to hopefully be more intuitive (#…
1d33111 
…1061)

- Changes to SqlServerDsc
  - Updated the ISSUE_TEMPLATE to hopefully be more intuitive and easier
    to use.
  - Added information to ISSUE_TEMPLATE that issues must be reproducible
    in SqlServerDsc resource module (if running the older xSQLServer
    resource module (issue #1036).
@johlju johlju removed the in progress The issue is being actively worked on by someone. label Mar 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement The issue is an enhancement request.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

SqlServerDsc: Updated ISSUE_TEMPLATE to hopefully be more intuitive johlju/SqlServerDsc
1 participant
@johlju