Re: Cutting a release?

2019-01-04 Thread Ivan Vučica
ChangeLogs and VCS logs takes a lot of the time when > > cutting a release I could better spend wrestling with git tagging, GPG > > signing and uploading to multiple locations. > > I have done this for back today and plan to do it for gui tomorrow. We should > still merge

Re: Cutting a release?

2019-01-03 Thread Fred Kiefer
> Am 02.01.2019 um 17:48 schrieb Ivan Vučica : > > In the meantime, if maintainers could help me out by updating the > non-autogenerated news entries and such, that'd help a lot. Crawling > through the ChangeLogs and VCS logs takes a lot of the time when > cutting a release I

Re: Cutting a release?

2019-01-03 Thread Yavor Doganov
В Thu, 03 Jan 2019 08:29:45 +0100, Gürkan Myczko написа: > On 01.01.2019 18:48, Gregory Casamento wrote: >> The Gorm changes David committed warrant a release of the app. So I >> concur with doing a release. > > Sounds great! Will it happen before 12th Jan 2019? The sooner, the > better. For

Re: Cutting a release?

2019-01-02 Thread Gürkan Myczko
On 01.01.2019 18:48, Gregory Casamento wrote: The Gorm changes David committed warrant a release of the app. So I concur with doing a release. Sounds great! Will it happen before 12th Jan 2019? The sooner, the better. Best, ___ Gnustep-dev

Re: Cutting a release?

2019-01-02 Thread Yavor Doganov
В Wed, 02 Jan 2019 16:48:51 +, Ivan Vučica написа: > I realized I'm not sure what transition means. Out of curiosity, is it > the transition from e.g. libgnustep-gui0.26 to libgnustep-gui0.27? Yes, that's a library transition. The Debian Release team "acks" a transition when the new

Re: Cutting a release?

2019-01-02 Thread Ivan Vučica
le to bother for sponsorship if we agree on a release. I suppose ftpmasters will be a hard block at that point. In the meantime, if maintainers could help me out by updating the non-autogenerated news entries and such, that'd help a lot. Crawling through the ChangeLogs and VCS logs takes a lot

Re: Cutting a release?

2019-01-01 Thread Yavor Doganov
В Tue, 01 Jan 2019 23:28:35 +, Ivan Vučica написа: > On Tue, Jan 1, 2019 at 9:43 PM Yavor Doganov wrote: >> I believe it's too late for that. >> > I could cut a release this weekend, and then we do another one by the > end of the month. It is probably doable, but there should be a

Re: Cutting a release?

2019-01-01 Thread Ivan Vučica
On Tue, Jan 1, 2019 at 11:23 PM Ivan Vučica wrote: > > >> >> PS: Did you see the two pull requests for back today? The first one, that >> wasn’t a real pull request rather a question about the code, has triggered >> me to rethink the removal of RContext. Perhaps somebody else could have a >>

Re: Cutting a release?

2019-01-01 Thread Ivan Vučica
On Tue, Jan 1, 2019 at 9:43 PM Yavor Doganov wrote: > I believe it's too late for that. GUI would need its SONAME bumped which > would mean we'll have to do a transition, but the transition freeze is on > 12th Jan. > I could cut a release this weekend, and then we do another one by the end of

Re: Cutting a release?

2019-01-01 Thread Gürkan Myczko
The freeze for buster will happen according to the following timeline: 2019-01-12 - Transition freeze 2019-02-12 - Soft-freeze 2019-03-12 - Full-freeze > On Jan 1, 2019, at 23:29, Gregory Casamento wrote: > > Could someone post the schedules for Debians releases or, at least, let us > know

Re: Cutting a release?

2019-01-01 Thread Gregory Casamento
Could someone post the schedules for Debians releases or, at least, let us know where to look for this information? I don’t know where a reliable source for this information is. All too often we plan a release only to find out we are too late. Knowing the schedule so we can plan accordingly

Re: Cutting a release?

2019-01-01 Thread Yavor Doganov
В Tue, 01 Jan 2019 16:24:29 +0100, Gürkan Myczko написа: > I think it would be great to have that new release for the next Debian > release which is going to happen soon: I believe it's too late for that. GUI would need its SONAME bumped which would mean we'll have to do a transition, but the

Re: Cutting a release?

2019-01-01 Thread Gregory Casamento
Vučica : >> > >> > Hi maintainers, >> > >> > If you want, I can spend some time cutting a release. It has been a >> while since the last one. Do we need a one? Are there critical bugs we >> fixed? Are there critical bugs blocking the release? >>

Re: Cutting a release?

2019-01-01 Thread Gürkan Myczko
Fred Kiefer > >> >> > Am 01.01.2019 um 12:44 schrieb Ivan Vučica : >> > >> > Hi maintainers, >> > >> > If you want, I can spend some time cutting a release. It has been a while >> > since the last one. Do we need a one? Are there

Re: Cutting a release?

2019-01-01 Thread Stefan Bidigaray
On Tue, Jan 1, 2019, 07:50 Fred Kiefer > > > Am 01.01.2019 um 12:44 schrieb Ivan Vučica : > > > > Hi maintainers, > > > > If you want, I can spend some time cutting a release. It has been a > while since the last one. Do we need a one? Are there critical bugs

Re: Cutting a release?

2019-01-01 Thread Fred Kiefer
> Am 01.01.2019 um 12:44 schrieb Ivan Vučica : > > Hi maintainers, > > If you want, I can spend some time cutting a release. It has been a while > since the last one. Do we need a one? Are there critical bugs we fixed? Are > there critical bugs blocking the release? Th

Re: Cutting a release?

2019-01-01 Thread David Chisnall
On 01/01/2019 11:44, Ivan Vučica wrote: Hi maintainers, If you want, I can spend some time cutting a release. It has been a while since the last one. Do we need a one? Are there critical bugs we fixed? Are there critical bugs blocking the release? There’s a pull request for icu-config

Cutting a release?

2019-01-01 Thread Ivan Vučica
Hi maintainers, If you want, I can spend some time cutting a release. It has been a while since the last one. Do we need a one? Are there critical bugs we fixed? Are there critical bugs blocking the release? There’s a pull request for icu-config removal that we could apply to -base. It might