Re: Add kio-gdrive to the release service
On 30/06/20 22:05, Albert Astals Cid wrote: > El dimarts, 30 de juny de 2020, a les 0:23:17 CEST, Elvis Angelaccio va > escriure: >> On 29/06/20 23:41, Albert Astals Cid wrote: >>> El dilluns, 29 de juny de 2020, a les 22:44:16 CEST, Elvis Angelaccio va >>> escriure: On 24/06/20 00:25, Albert Astals Cid wrote: > El dilluns, 22 de juny de 2020, a les 23:44:39 CEST, Elvis Angelaccio va > escriure: >> Hi release team, >> >> I'd like to add kio-gdrive to the release service. kio-gdrive depends on >> libkgapi which is also included in the release service, so it makes >> sense to follow the same release schedule. It already happened once that >> libkgapi changed the API and I could not make a new kio-gdrive release >> in time. >> >> Do you see any drawbacks? Please discuss :) > You will lose the external versioning of the tarballs. What do you mean exactly? >>> I mean that kio-gdrive tarball released will be kio-gdrive-20.08.0.tar.xz >>> which as a followup of 1.3.0 may be weird. >>> >>> But if you think that's fine for your users, then no problem. >> Yes I think it would be fine. >> >>> You also need to decide if you want to internally align to >>> RELEASE_SERVICE_VERSION or keep your 1.x.y naming. If you keep to your >>> 1.x.y naming you need to commit to update it timely. >> Yes I'd prefer to switch to the automatic version bump provided by >> RELEASE_SERVICE_VERSION. Otherwise I'll forget for sure :P > Ok, since noone else seemed to complain i've added it to the list of modules > to be released > > https://invent.kde.org/sysadmin/release-tools/commit/55205d99c891db1c5e8980ebcd16b5f213d2c31b > > Please update the code to use RELEASE_SERVICE_VERSION as soon as possible. Done. Thanks Albert and Ben :) Cheers, Elvis > > I think that there's something else somewhere that needs to change so that > the build.kde.org changes from "extragear" to "Applications" [both outdated > terms]. Sysadmin? > > Cheers, > Albert > >>> Cheers, >>> Albert >> Thanks, >> >> Elvis >> >> > Cheers, > Albert Cheers, Elvis >> Thanks >> >> Cheers, >> Elvis >> >> > >>> >>> > > >
Re: Add kio-gdrive to the release service
On Wed, Jul 1, 2020 at 8:05 AM Albert Astals Cid wrote: > > El dimarts, 30 de juny de 2020, a les 0:23:17 CEST, Elvis Angelaccio va > escriure: > > On 29/06/20 23:41, Albert Astals Cid wrote: > > > El dilluns, 29 de juny de 2020, a les 22:44:16 CEST, Elvis Angelaccio va > > > escriure: > > >> On 24/06/20 00:25, Albert Astals Cid wrote: > > >>> El dilluns, 22 de juny de 2020, a les 23:44:39 CEST, Elvis Angelaccio > > >>> va escriure: > > Hi release team, > > > > I'd like to add kio-gdrive to the release service. kio-gdrive depends > > on > > libkgapi which is also included in the release service, so it makes > > sense to follow the same release schedule. It already happened once > > that > > libkgapi changed the API and I could not make a new kio-gdrive release > > in time. > > > > Do you see any drawbacks? Please discuss :) > > >>> You will lose the external versioning of the tarballs. > > >> What do you mean exactly? > > > I mean that kio-gdrive tarball released will be kio-gdrive-20.08.0.tar.xz > > > which as a followup of 1.3.0 may be weird. > > > > > > But if you think that's fine for your users, then no problem. > > > > Yes I think it would be fine. > > > > > > > > You also need to decide if you want to internally align to > > > RELEASE_SERVICE_VERSION or keep your 1.x.y naming. If you keep to your > > > 1.x.y naming you need to commit to update it timely. > > > > Yes I'd prefer to switch to the automatic version bump provided by > > RELEASE_SERVICE_VERSION. Otherwise I'll forget for sure :P > > Ok, since noone else seemed to complain i've added it to the list of modules > to be released > > https://invent.kde.org/sysadmin/release-tools/commit/55205d99c891db1c5e8980ebcd16b5f213d2c31b > > Please update the code to use RELEASE_SERVICE_VERSION as soon as possible. > > I think that there's something else somewhere that needs to change so that > the build.kde.org changes from "extragear" to "Applications" [both outdated > terms]. Sysadmin? This should be done now, in the two commits that I CC'ed to this list. Regards, Ben > > Cheers, > Albert > > > > > > > > > Cheers, > > > Albert > > > > Thanks, > > > > Elvis > > > > > > > > > >>> Cheers, > > >>> Albert > > >> Cheers, > > >> > > >> Elvis > > >> > > >> > > Thanks > > > > Cheers, > > Elvis > > > > > > >>> > > >>> > > > > > > > > > > > > > > >
Re: Add kio-gdrive to the release service
El dimarts, 30 de juny de 2020, a les 0:23:17 CEST, Elvis Angelaccio va escriure: > On 29/06/20 23:41, Albert Astals Cid wrote: > > El dilluns, 29 de juny de 2020, a les 22:44:16 CEST, Elvis Angelaccio va > > escriure: > >> On 24/06/20 00:25, Albert Astals Cid wrote: > >>> El dilluns, 22 de juny de 2020, a les 23:44:39 CEST, Elvis Angelaccio va > >>> escriure: > Hi release team, > > I'd like to add kio-gdrive to the release service. kio-gdrive depends on > libkgapi which is also included in the release service, so it makes > sense to follow the same release schedule. It already happened once that > libkgapi changed the API and I could not make a new kio-gdrive release > in time. > > Do you see any drawbacks? Please discuss :) > >>> You will lose the external versioning of the tarballs. > >> What do you mean exactly? > > I mean that kio-gdrive tarball released will be kio-gdrive-20.08.0.tar.xz > > which as a followup of 1.3.0 may be weird. > > > > But if you think that's fine for your users, then no problem. > > Yes I think it would be fine. > > > > > You also need to decide if you want to internally align to > > RELEASE_SERVICE_VERSION or keep your 1.x.y naming. If you keep to your > > 1.x.y naming you need to commit to update it timely. > > Yes I'd prefer to switch to the automatic version bump provided by > RELEASE_SERVICE_VERSION. Otherwise I'll forget for sure :P Ok, since noone else seemed to complain i've added it to the list of modules to be released https://invent.kde.org/sysadmin/release-tools/commit/55205d99c891db1c5e8980ebcd16b5f213d2c31b Please update the code to use RELEASE_SERVICE_VERSION as soon as possible. I think that there's something else somewhere that needs to change so that the build.kde.org changes from "extragear" to "Applications" [both outdated terms]. Sysadmin? Cheers, Albert > > > > > Cheers, > > Albert > > Thanks, > > Elvis > > > > > >>> Cheers, > >>> Albert > >> Cheers, > >> > >> Elvis > >> > >> > Thanks > > Cheers, > Elvis > > > >>> > >>> > > > > > > >
Re: Add kio-gdrive to the release service
On 29/06/20 23:41, Albert Astals Cid wrote: > El dilluns, 29 de juny de 2020, a les 22:44:16 CEST, Elvis Angelaccio va > escriure: >> On 24/06/20 00:25, Albert Astals Cid wrote: >>> El dilluns, 22 de juny de 2020, a les 23:44:39 CEST, Elvis Angelaccio va >>> escriure: Hi release team, I'd like to add kio-gdrive to the release service. kio-gdrive depends on libkgapi which is also included in the release service, so it makes sense to follow the same release schedule. It already happened once that libkgapi changed the API and I could not make a new kio-gdrive release in time. Do you see any drawbacks? Please discuss :) >>> You will lose the external versioning of the tarballs. >> What do you mean exactly? > I mean that kio-gdrive tarball released will be kio-gdrive-20.08.0.tar.xz > which as a followup of 1.3.0 may be weird. > > But if you think that's fine for your users, then no problem. Yes I think it would be fine. > > You also need to decide if you want to internally align to > RELEASE_SERVICE_VERSION or keep your 1.x.y naming. If you keep to your 1.x.y > naming you need to commit to update it timely. Yes I'd prefer to switch to the automatic version bump provided by RELEASE_SERVICE_VERSION. Otherwise I'll forget for sure :P > > Cheers, > Albert Thanks, Elvis > >>> Cheers, >>> Albert >> Cheers, >> >> Elvis >> >> Thanks Cheers, Elvis >>> >>> > > >
Re: Add kio-gdrive to the release service
El dilluns, 29 de juny de 2020, a les 22:44:16 CEST, Elvis Angelaccio va escriure: > On 24/06/20 00:25, Albert Astals Cid wrote: > > El dilluns, 22 de juny de 2020, a les 23:44:39 CEST, Elvis Angelaccio va > > escriure: > >> Hi release team, > >> > >> I'd like to add kio-gdrive to the release service. kio-gdrive depends on > >> libkgapi which is also included in the release service, so it makes > >> sense to follow the same release schedule. It already happened once that > >> libkgapi changed the API and I could not make a new kio-gdrive release > >> in time. > >> > >> Do you see any drawbacks? Please discuss :) > > You will lose the external versioning of the tarballs. > > What do you mean exactly? I mean that kio-gdrive tarball released will be kio-gdrive-20.08.0.tar.xz which as a followup of 1.3.0 may be weird. But if you think that's fine for your users, then no problem. You also need to decide if you want to internally align to RELEASE_SERVICE_VERSION or keep your 1.x.y naming. If you keep to your 1.x.y naming you need to commit to update it timely. Cheers, Albert > > > > > Cheers, > > Albert > > Cheers, > > Elvis > > > >> Thanks > >> > >> Cheers, > >> Elvis > >> > >> > > > > > > >
Re: Add kio-gdrive to the release service
On 24/06/20 00:25, Albert Astals Cid wrote: > El dilluns, 22 de juny de 2020, a les 23:44:39 CEST, Elvis Angelaccio va > escriure: >> Hi release team, >> >> I'd like to add kio-gdrive to the release service. kio-gdrive depends on >> libkgapi which is also included in the release service, so it makes >> sense to follow the same release schedule. It already happened once that >> libkgapi changed the API and I could not make a new kio-gdrive release >> in time. >> >> Do you see any drawbacks? Please discuss :) > You will lose the external versioning of the tarballs. What do you mean exactly? > > Cheers, > Albert Cheers, Elvis >> Thanks >> >> Cheers, >> Elvis >> >> > > >
Re: Add kio-gdrive to the release service
El dilluns, 22 de juny de 2020, a les 23:44:39 CEST, Elvis Angelaccio va escriure: > Hi release team, > > I'd like to add kio-gdrive to the release service. kio-gdrive depends on > libkgapi which is also included in the release service, so it makes > sense to follow the same release schedule. It already happened once that > libkgapi changed the API and I could not make a new kio-gdrive release > in time. > > Do you see any drawbacks? Please discuss :) You will lose the external versioning of the tarballs. Cheers, Albert > > Thanks > > Cheers, > Elvis > >
Re: Add kio-gdrive to the release service
+1 Nate On 6/22/20 3:44 PM, Elvis Angelaccio wrote: Hi release team, I'd like to add kio-gdrive to the release service. kio-gdrive depends on libkgapi which is also included in the release service, so it makes sense to follow the same release schedule. It already happened once that libkgapi changed the API and I could not make a new kio-gdrive release in time. Do you see any drawbacks? Please discuss :) Thanks Cheers, Elvis
