Especialy since the distros often lag the release cycle by quite a bit. 1.7.x is not due on Fedora until release 25, which is several months away.
On 12 Sep 2016 09:58, "Dave Cheney" <d...@cheney.net> wrote: An 'official' deb/apt/yum repo for Go would be much appreciated, https://github.com/golang/go/issues/10965 On Monday, 12 September 2016 11:44:06 UTC+10, Mark Richman wrote: > > Ian, > > I would definitely be interested in triage, backlog refinement, etc. Are > there product owners designated for each functional area? I could start by > making sure new issues are at least assigned to the correct PO for > prioritization. > > With respect to packaging, I'm aware of the current effort underway. In my > day job, I'm responsible for packaging -- both our internal library > packages, and our customer-facing product packages. This includes the > tooling around the packages, the delivery mechanism(s), web front end for > administration, etc. I am admittedly a Go novice, but I think this is a > relatively language-agnostic discipline. However, I know of the vendoring > quirks and lack of portable libraries (i.e. dll or jar style references). > > If you think these are areas I could be of service, feel free to follow up > with me offline if you like. > > Thanks, > Mark > http://markrichman.com > mark [at] markrichman.com > > On Sunday, September 11, 2016 at 1:55:52 PM UTC-4, Ian Lance Taylor wrote: >> >> On Sun, Sep 11, 2016 at 6:43 AM, Mark Richman <markar...@gmail.com> >> wrote: >> > >> > I'm somewhat new to the community, and seek to understand its >> challenges >> > better. I'm also looking for opportunities to contribute. >> > >> > To that end, what 5 things does Go need in 2017? >> > >> > For example: language features, tooling, advocacy, community, platform >> > support, etc. >> >> Thanks for offering. There are many open issues at >> https://golang.org/issue. Issue triage is an ongoing consumer of >> time. >> >> Personally I think our biggest open issues relate to packaging, >> especially managing third party packages. There is an active effort >> to sort this out. >> >> Unfortunately helping with those does require some familiarity with >> the language and the community. >> >> The documentation can always be improved. >> >> This is just off the top of my head, others may have other suggestions. >> >> Ian >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
