-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/29/2015 03:17 PM, Piotr Popieluch wrote: > On 11/26/2015 01:11 PM, Zuzana Svetlikova wrote: >> Are there any actual plans for Node.js stack in fedora? Are we >> going to update everything and hope that nothing breaks (much)? >> Is there any way of knowing beforehand if update will break some >> other packages (because I don't know of any, so please enlighten >> me)? > I try to build packages in COPR first, but this is quite work > intensive and does not have any automated checks. Rawhide has no > gating/checks either, I think most of us did accidentally push a > package to rawhide which happened to introduce new missing > dependencies. Koschei is good to see if an update to a package > breaks a dependency, but for this to work packages need to have > tests enabled and we still miss some test frameworks (which are not > packaged yet). Also Kosechei is a bit too late imho, I would rather > want to know if my update breaks something *before* I push it to > rawhide, not after.. > >> What about updating v8, nodejs and npm? Are we going for LTS and >> npm@2 or directly to v5.x and npm@3? > T.C. Hollingsworth had plans to update but this got delayed. I > haven't heard from him in a while.
- From what I've heard, he's effectively gone from this project due to other commitments at this time. > Victor Jancik tried to update nodejs out of the blue without > contacting any one of us. That wasn't received well and most of his > ACL requests got mass denied. I think that unfortunately this > reaction demotivated him to continue on this. > > Someone needs to step up to lead these updates. I certainly don't > have the time and packaging experience to do this. > I have the packaging experience and can try to help with reviews, but my daily tasks will prevent me from doing a lot of active work right now. That said, I know that there are plenty of people with a vested interest in seeing Node,js 4.x+ appear in Fedora and EPEL as soon as humanly possible. In particular, with the source release of Visual Studio Code, there are some folks who would consider it a coup for Fedora 24 to be the first distro to carry it in the repository. I'd also like to propose that we focus on working only on the 4.x LTS release initially and upgrade Fedora to the latest supported release after that (this way we can do the exact same work for both Fedora and EPEL in the first pass; I think it makes sense for EPEL to always stay on the LTS releases). >> >> I'm sorry for so many questions, I'd just like to have some >> answers so I know on what I should focus. >> No, it's important to have a plan, certainly. I'll see what I can do to get the core libuv and nodejs packages up to 4.x if I can find the time this week. In order to avoid breaking Rawhide significantly, I think it would be a good idea to request a side-tag to work on this. I'm resurrecting the 0.12 upgrade Change Proposal and updating it to 4.x: https://fedoraproject.org/wiki/Changes/NodeJS4x I've put my name on it as the Change Owner, but I'd appreciate if anyone else who is working on this would also add their names to the Owner section. I'll mark the page as ready for the wrangler announcement once at least one other person signs on. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlZcTUUACgkQeiVVYja6o6NVBACeKdLxoR+XeblHBBDjwDHgOBJs ED0An2iG7P+p1+E3DmM4/5OK5iRyu9Kj =oIvD -----END PGP SIGNATURE----- _______________________________________________ nodejs mailing list [email protected] http://lists.fedoraproject.org/admin/lists/[email protected]
