by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 12:43
    WWILLV starred winsw/winsw
  • 12:36
    jimsears starred winsw/winsw
  • 12:02
  • 09:42
    GuoKerS starred winsw/winsw
  • 07:32
    mrbugs55 starred winsw/winsw
  • 07:32
    mrbugs55 starred winsw/winsw
  • Sep 17 17:36
    oslvbo starred winsw/winsw
  • Sep 17 09:55

    NextTurn on v3

    Bump Mono.Cecil from 0.11.2 to … (compare)

  • Sep 17 09:55

    NextTurn on nuget

    (compare)

  • Sep 17 09:55
    NextTurn closed #684
  • Sep 17 09:00
    sunazl starred winsw/winsw
  • Sep 17 07:18
    lim0513 starred winsw/winsw
  • Sep 17 07:12
    dependabot[bot] synchronize #684
  • Sep 17 07:12

    dependabot[bot] on nuget

    Bump Mono.Cecil from 0.11.2 to … (compare)

  • Sep 17 07:12
    dependabot[bot] edited #684
  • Sep 17 07:11
    dependabot[bot] edited #684
  • Sep 17 07:11
    NextTurn commented #684
  • Sep 17 06:05

    NextTurn on devps-a

    (compare)

  • Sep 17 06:05

    NextTurn on v3

    Add 'dev ps -a|--all' option (compare)

  • Sep 17 06:05
    NextTurn closed #685
Oleg Nenashev
@oleg-nenashev
makes sense
Extension support is critical, because without it WinSW for YAML does not provide similar functionality as XML
BTW it is not a blocker for the release even in this case
My main concern is that we postpone the release too much and do not deliver the changes to users before the end of GSoC
... so that all user feedback comes in afterwards
Next Turn
@NextTurn

Ideally it's better to only use the style with root elements.

Just to clarify, this comment only applied to XML. Using both items and item in YAML seems verbose and defeats the sequence design IMO.

Oleg Nenashev
@oleg-nenashev
So I am tempted to cut the new WinSW release tomorrow with proper YAML support preview disclaimers. WDYT @NextTurn @buddhikac96 ?
Next Turn
@NextTurn
I completely agree.
Buddhika Chathuranga
@buddhikac96

So I am tempted to cut the new WinSW release tomorrow with proper YAML support preview disclaimers. WDYT @NextTurn @buddhikac96 ?

Is this mean you will release tomorrow with current status?

Oleg Nenashev
@oleg-nenashev
yes
Hopefully it will lead to a few users trying it out
Buddhika Chathuranga
@buddhikac96
thanks.. yeah that would be great!
Oleg Nenashev
@oleg-nenashev
If you could publish your slides somewhere, I am happy to reference them in the changelog
Buddhika Chathuranga
@buddhikac96
is google slides not okay?
I can use slides.com or slideshare as you prefer
Next Turn
@NextTurn
@oleg-nenashev When do we plan to switch the default branch?
Next Turn
@NextTurn
I suggest merging #569, #580 and #582 into this release. These are all ready to ship.
Oleg Nenashev
@oleg-nenashev
+1
regarding switching, ready at any moment
Next Turn
@NextTurn
I'm worried about the notifications of closed issues. Without v3 being the default branch our users will only received "Closed #xxx" rather than "Closed #xxx via #xxx", making it unclear if it has been fixed.
Oleg Nenashev
@oleg-nenashev
It is always possible to add additional comment with clarification
Buddhika Chathuranga
@buddhikac96

is google slides not okay?

??

Next Turn
@NextTurn

It is always possible to add additional comment with clarification

But that will generate 1x more notifications for all subscribers... which is what I'm trying to avoid.

Oleg Nenashev
@oleg-nenashev
@buddhikac96 google slides should be fine if public
Also beware about potential comment vandalizm
I usually post my slides as google slides these days tho
Buddhika Chathuranga
@buddhikac96
great. I ll share with view-only access
Oleg Nenashev
@oleg-nenashev
@buddhikac96 :+1: would you also be able to announce the feature preview in the blogpost? You can add a placeholder link to the WinSW release for downloads
Buddhika Chathuranga
@buddhikac96
Great! So the feature preview section should simply include something like we have released a feature preview with YAML support and you can download from here ?
Oleg Nenashev
@oleg-nenashev
Yes
Buddhika Chathuranga
@buddhikac96
@oleg-nenashev I create a simple plan for the extension support. Diagrams may not be following the rules. Could you review whether this plan works?
Next Turn
@NextTurn
I have a small suggestion... Don't use [here](). Give the link a name.
Buddhika Chathuranga
@buddhikac96
like You can find the document in https://github.com/winsw/winsw/blob/master/doc/YamlConfigFile.md?
Next Turn
@NextTurn
like [YAML configuration specification](YamlConfigFile.md).
Buddhika Chathuranga
@buddhikac96
great
Oleg Nenashev
@oleg-nenashev
FTR Release Drafter does not handle multi-branch configurations well. I have another tool which generates changelogs in a more consistent way, but right now I will rather patch the changelog manually
Will release in 1h if no negative feedback
Oleg Nenashev
@oleg-nenashev
@buddhikac96 Am I right that in the current version in the v2 branch it is NOT possible to use the feature as a user? ServiceDescriptorYaml is not used anywhere in the codebase
Created winsw/winsw#630 . I will not be releasing WinSW until the YAML configuration support is actually added for users and documented
Buddhika Chathuranga
@buddhikac96
Yes. My plan was, select the configuration type(XML or YAML) by configuration file provided by the user. For that, we have to integrate both new CLI and YAML Support. That was how I did the demo. But there is another workaround we can do. Find the configuration file with the same name as the executable and select the configuration type (XML or YAML). If both are available then continue with XML. If that workaround sounds good I can implement that. Otherwise, we can integrate both new CLI and YAML support. What do you prefer?
Oleg Nenashev
@oleg-nenashev
I believe we agreed on a workaround a few weeks ago, didn't we?
Buddhika Chathuranga
@buddhikac96

We can search for both winsw.xml and winsw.yml, and use .xml as a first choice.

Yeah, we talk about this. But I think we did not confirm that. Sorry, I think I have misunderstood that :(

Oleg Nenashev
@oleg-nenashev
I suggest we reintroduce the weekly voice chat to ensure that we are on the same page
Buddhika Chathuranga
@buddhikac96
Would be great!
Anyway how should I continue on that? I can allocate time for this.
Oleg Nenashev
@oleg-nenashev
Just send a doodle. If you have slots before 11 am UTC, it would be great
5 replies
Buddhika Chathuranga
@buddhikac96
Sure. I will. Anyway I mean I can spend time working on that feature right now if we can confirm a workaround?