Re: [scl.org] Python 3.6 availability
On 04/11/2017 10:24 AM, Nick Coghlan wrote: On Fri, Mar 31, 2017 at 6:30 PM, Nick Coghlan wrote: On Sun, Mar 26, 2017 at 12:50 AM, meson wrote: Hi, is there any estimate on when Python 3.6 will be available as SCL? Our devs are asking about it. If it's going to take a long time, I'll try my hand at building the packages myself. It likely makes sense to have some community maintained sclo-* Python packages I've been mulling this idea over for the past couple of weeks, and I'm wondering if it might make sense to create a rolling "sclo-python3" SCL, that's initially forked from https://www.softwarecollections.org/en/scls/rhscl/rh-python35/, but explicitly promises to rebase to new Python feature releases when they come out. So if people were happy to always run on the leading edge (even for X.Y.0 releases), they could use "sclo-python3", but if they wanted to stay on a particular X.Y release for a while, they would need to switch to the downstream rh-pythonXY SCLs. Remi, if I wanted to do that, where would I start? https://github.com/sclorg-distgit is useful as a reference for submitting changes to existing community SCLs, but it doesn't provide any guidance on how to start a new one (and that info is also missing from the wiki). Hi Nick, I've finally put some short guidance to: https://wiki.centos.org/SpecialInterestGroup/SCLo#head-b408f06ad89fd3a67686f755eafac7ce310ee081 I think that by this mail you basically did the step "Propose adding a new SCL on the mailing list", so now we should agree on the naming and SCL purpose. From my PoV, the last proposal of having "sclo-python3" with "always latest major Python 3" looks good to me, I'll also ask python maint team for their opinion, but if nobody is against here, we can go with this approach. The next step will be you (or the person who is going to build the packages) becoming a SIG member (https://wiki.centos.org/HowTos/CommunityBuildSystem) and then we need to request build tags in the cbs.centos.org (https://wiki.centos.org/SpecialInterestGroup/SCLo#head-4ce81a8b651b8a1217a0c97f757e0eab869bea48). Whether you'll find https://github.com/sclorg-distgit useful for development, or it will be used only for adding sources after build, it's up to you.. Let me know if you have any further questions.. Honza ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] Python 3.6 availability
On Fri, Mar 31, 2017 at 6:30 PM, Nick Coghlan wrote: > On Sun, Mar 26, 2017 at 12:50 AM, meson wrote: >> Hi, >> >> is there any estimate on when Python 3.6 will be available as SCL? >> >> Our devs are asking about it. If it's going to take a long time, I'll try my >> hand at building the packages myself. > > It likely makes sense to have some community maintained sclo-* Python > packages I've been mulling this idea over for the past couple of weeks, and I'm wondering if it might make sense to create a rolling "sclo-python3" SCL, that's initially forked from https://www.softwarecollections.org/en/scls/rhscl/rh-python35/, but explicitly promises to rebase to new Python feature releases when they come out. So if people were happy to always run on the leading edge (even for X.Y.0 releases), they could use "sclo-python3", but if they wanted to stay on a particular X.Y release for a while, they would need to switch to the downstream rh-pythonXY SCLs. Remi, if I wanted to do that, where would I start? https://github.com/sclorg-distgit is useful as a reference for submitting changes to existing community SCLs, but it doesn't provide any guidance on how to start a new one (and that info is also missing from the wiki). Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] Python 3.6 availability
On Fri, Mar 31, 2017 at 7:02 PM, Remi Collet wrote: > Le 31/03/2017 à 10:30, Nick Coghlan a écrit : > >> Remi, do you have access to edit the CentOS wiki? It would be good to >> provide a pointer to https://github.com/sclorg-distgit from >> https://wiki.centos.org/SpecialInterestGroup/SCLo > > Please, review if this change seems clear enough : > > https://wiki.centos.org/SpecialInterestGroup/SCLo#head-429ebba9d9c8bcd7e55c1ae23c7ba652901a629c Looks good. The other place that could potentially use an update is this one: == Steps for adding a new collection TBD == Even if there are plans in place to change the process, would it make sense to at least write down how the current sclo-* packages got started and recommend that others interested in publishing a community collection adopt the same approach? Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] Python 3.6 availability
Le 31/03/2017 à 10:30, Nick Coghlan a écrit : > Remi, do you have access to edit the CentOS wiki? It would be good to > provide a pointer to https://github.com/sclorg-distgit from > https://wiki.centos.org/SpecialInterestGroup/SCLo Please, review if this change seems clear enough : https://wiki.centos.org/SpecialInterestGroup/SCLo#head-429ebba9d9c8bcd7e55c1ae23c7ba652901a629c Remi ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] Python 3.6 availability
On Sun, Mar 26, 2017 at 12:50 AM, meson wrote: > Hi, > > is there any estimate on when Python 3.6 will be available as SCL? > > Our devs are asking about it. If it's going to take a long time, I'll try my > hand at building the packages myself. It likely makes sense to have some community maintained sclo-* Python packages regardless, as the rh-* ones are officially Red Hat maintained, and hence: - are published in line with Red Hat's product schedules rather than necessarily being ASAP after the upstream release - have RHEL-style rules against rebasing components within the collection (so some updates have to wait for the next revision of the entire collection) - are restricted to components that Red Hat is currently willing to commercially support with security backports By contrast, community packages could adopt more permissive policies around package inclusion and rebasing, without having to take Red Hat's commercial support obligations into account the way the official SCLs do. > A general question: is the SCL development open? I did not find any public > git repositories apart from the CentOS source server. I'd love to > contribute. Remi, do you have access to edit the CentOS wiki? It would be good to provide a pointer to https://github.com/sclorg-distgit from https://wiki.centos.org/SpecialInterestGroup/SCLo and you have a much better understanding than I do of how the existing sclo-* SCLs are maintained. Cheers, Nick. P.S. Perhaps it would be worth adding an "sclo-admin" repo to the sclo-distgit org, and pinning it? Then the README for that could be used as a second entry point for info about the SCLo sig, and it could also provide an issue tracker for the SIG itself, rather than relying solely on the mailing list and the RHSCL component in Red Hat's bugzilla instance (which only covers the official SCLs anyway). -- Nick Coghlan Red Hat Platform Engineering, Brisbane ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
Re: [scl.org] Python 3.6 availability
Le 25/03/2017 à 15:50, meson a écrit : > Hi, > > is there any estimate on when Python 3.6 will be available as SCL? Can't say. > Our devs are asking about it. If it's going to take a long time, I'll > try my hand at building the packages myself. > > A general question: is the SCL development open? I did not find any > public git repositories apart from the CentOS source server. I'd love to > contribute. rh-* packages are maintained upstream by Red Hat, the SIG only takes care of the rebuild in CentOS. sclo-* packages are maintained by the community (the SCLo SIG) See: https://github.com/sclorg-distgit Remi ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
[scl.org] Python 3.6 availability
Hi, is there any estimate on when Python 3.6 will be available as SCL? Our devs are asking about it. If it's going to take a long time, I'll try my hand at building the packages myself. A general question: is the SCL development open? I did not find any public git repositories apart from the CentOS source server. I'd love to contribute. Kind Regards meson ___ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
