Upcoming freezes KDE 4.7
Hi, Just to let you all know that some freezes are coming up next week in preparation of the first 4.7 beta release. Some items of importance: -- Thursday, May 12, 2011: KDE 4.7 Dependency Freeze >From this moment on it is not allowed to add new dependencies or bump >dependencies versions. It is possible to get an exception for this. Post the >patch to reviewboard and add the release-team as reviewer. We will check if >the dependency is needed and is available on all platforms. In other words: If you have a feature that requires a new dependency or a version of a dependency that is higher than currently checked for in the build system, you need to have committed this change before this date. Thursday, May 12, 2011: KDE 4.7 Hard Feature Freeze Trunk is frozen for all feature commits, even those listed in the planned feature document. Only bug fixes are allowed. Thursday, May 19, 2011: KDE 4.7 Beta 1 Tagging Trunk is frozen for beta release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. The usual beta rules apply as soon as the Beta tarballs have been generated. Wednesday, May 25, 2011: KDE 4.7 Beta 1 Release The beta becomes available for general consumption. -- The rest of the schedule is available at: http://techbase.kde.org/Schedules/KDE4/4.7_Release_Schedule Or add a reference to the always up-to-date ics file to your calendar-app: http://www.kde.org/releaseschedule.ics Best, -- Tom Albers KDE Sysadmin
Re: Upcoming freezes KDE 4.7
The KDE 4.7 Hard Freeze date is still a couple of days away, but I am going to ask for an exception. I have pending UI changes for the proxy configuration dialog that will not make that date and it cannot be pushed until 4.8. This item is already on the features list, but I get held up fixing rather critical bugs and was not able to get around to completing it. It is critical that these changes be in the 4.7 ; so I am asking for an exception. They should be in place for the Beta 2 tagging... On Sat, May 7, 2011 at 4:56 PM, Tom Albers wrote: > Hi, > > Just to let you all know that some freezes are coming up next week in > preparation of the first 4.7 beta release. Some items of importance: > > -- > Thursday, May 12, 2011: KDE 4.7 Dependency Freeze > From this moment on it is not allowed to add new dependencies or bump > dependencies versions. It is possible to get an exception for this. Post the > patch to reviewboard and add the release-team as reviewer. We will check if > the dependency is needed and is available on all platforms. > > In other words: If you have a feature that requires a new dependency or a > version of a dependency that is higher than currently checked for in the > build system, you need to have committed this change before this date. > > Thursday, May 12, 2011: KDE 4.7 Hard Feature Freeze > Trunk is frozen for all feature commits, even those listed in the planned > feature document. Only bug fixes are allowed. > > Thursday, May 19, 2011: KDE 4.7 Beta 1 Tagging > Trunk is frozen for beta release tagging. Only urgent fixes, such as those > fixing compilation errors, should be committed. The usual beta rules apply as > soon as the Beta tarballs have been generated. > > Wednesday, May 25, 2011: KDE 4.7 Beta 1 Release > The beta becomes available for general consumption. > -- > > The rest of the schedule is available at: > http://techbase.kde.org/Schedules/KDE4/4.7_Release_Schedule > > Or add a reference to the always up-to-date ics file to your calendar-app: > http://www.kde.org/releaseschedule.ics > > Best, > -- > Tom Albers > KDE Sysadmin >
Re: Upcoming freezes KDE 4.7
Dawit, I'm not so sure that this is a new feature -- more like an improvement to an existing feature. BTW: exception requests should be sent to the Release Team (who I've CC'd) Speaking as a Release Team member, I have no problem with your exception request. More problematic would be the need for new translatable strings past the string freeze. So you may also need to coordinate with the translators. -Allen On Tuesday, May 10, 2011 01:49:01 pm Dawit A wrote: > The KDE 4.7 Hard Freeze date is still a couple of days away, but I am > going to ask for an exception. I have pending UI changes for the proxy > configuration dialog that will not make that date and it cannot be > pushed until 4.8. This item is already on the features list, but I get > held up fixing rather critical bugs and was not able to get around to > completing it. It is critical that these changes be in the 4.7 ; so I > am asking for an exception. They should be in place for the Beta 2 > tagging... > > On Sat, May 7, 2011 at 4:56 PM, Tom Albers wrote: > > Hi, > > > > Just to let you all know that some freezes are coming up next week in > > preparation of the first 4.7 beta release. Some items of importance: > > > > -- > > Thursday, May 12, 2011: KDE 4.7 Dependency Freeze > > From this moment on it is not allowed to add new dependencies or bump > > dependencies versions. It is possible to get an exception for this. Post > > the patch to reviewboard and add the release-team as reviewer. We will > > check if the dependency is needed and is available on all platforms. > > > > In other words: If you have a feature that requires a new dependency or a > > version of a dependency that is higher than currently checked for in the > > build system, you need to have committed this change before this date. > > > > Thursday, May 12, 2011: KDE 4.7 Hard Feature Freeze > > Trunk is frozen for all feature commits, even those listed in the planned > > feature document. Only bug fixes are allowed. > > > > Thursday, May 19, 2011: KDE 4.7 Beta 1 Tagging > > Trunk is frozen for beta release tagging. Only urgent fixes, such as those > > fixing compilation errors, should be committed. The usual beta rules apply > > as soon as the Beta tarballs have been generated. > > > > Wednesday, May 25, 2011: KDE 4.7 Beta 1 Release > > The beta becomes available for general consumption. > > -- > > > > The rest of the schedule is available at: > > http://techbase.kde.org/Schedules/KDE4/4.7_Release_Schedule > > > > Or add a reference to the always up-to-date ics file to your calendar-app: > > http://www.kde.org/releaseschedule.ics > > > > Best, > > -- > > Tom Albers > > KDE Sysadmin > > >
Re: Upcoming freezes KDE 4.7
Hi, On Tuesday, May 10, 2011 17:17:04 Allen Winter wrote: > I'm not so sure that this is a new feature -- more like an improvement to an > existing feature. > > BTW: exception requests should be sent to the Release Team (who I've CC'd) > > Speaking as a Release Team member, I have no problem with your exception > request. More problematic would be the need for new translatable strings > past the string freeze. So you may also need to coordinate with the > translators. Yep, if it contains new strings, translators would need notification of the new strings. If it's getting too close to release time, it would be good to ask if there are problems with the translations then. > On Tuesday, May 10, 2011 01:49:01 pm Dawit A wrote: > > The KDE 4.7 Hard Freeze date is still a couple of days away, but I am > > going to ask for an exception. I have pending UI changes for the proxy > > configuration dialog that will not make that date and it cannot be > > pushed until 4.8. This item is already on the features list, but I get > > held up fixing rather critical bugs and was not able to get around to > > completing it. It is critical that these changes be in the 4.7 ; so I > > am asking for an exception. They should be in place for the Beta 2 > > tagging... I also do not see a problem with that. Just to get a better understanding, why are these changes important? Thanks for working on this, btw. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
Re: Upcoming freezes KDE 4.7
On Tue, May 10, 2011 at 5:50 PM, Sebastian Kügler wrote: > Hi, > > On Tuesday, May 10, 2011 17:17:04 Allen Winter wrote: >> I'm not so sure that this is a new feature -- more like an improvement to an >> existing feature. >> >> BTW: exception requests should be sent to the Release Team (who I've CC'd) >> >> Speaking as a Release Team member, I have no problem with your exception >> request. More problematic would be the need for new translatable strings >> past the string freeze. So you may also need to coordinate with the >> translators. > > Yep, if it contains new strings, translators would need notification of the > new strings. If it's getting too close to release time, it would be good to > ask if there are problems with the translations then. Actually there are going to be very few string additions and changes. For example, input for entering SOCKS proxy information will be made available and hence new strings that come with that. Otherwise, there is not much change when it comes to strings and translations. I will try to inform the translators by marking my commits with "GUI:" and also sending a message about the changes to the appropriate list. >> On Tuesday, May 10, 2011 01:49:01 pm Dawit A wrote: >> > The KDE 4.7 Hard Freeze date is still a couple of days away, but I am >> > going to ask for an exception. I have pending UI changes for the proxy >> > configuration dialog that will not make that date and it cannot be >> > pushed until 4.8. This item is already on the features list, but I get >> > held up fixing rather critical bugs and was not able to get around to >> > completing it. It is critical that these changes be in the 4.7 ; so I >> > am asking for an exception. They should be in place for the Beta 2 >> > tagging... > > I also do not see a problem with that. > > Just to get a better understanding, why are these changes important? Because things like entering SOCKS proxy information is missing right now and have to be added back. Moreover, the entire proxy configuration dialog can be streamlined and not be as clunky as it is right now. For example, the separate dialogs for configuring manual and system proxy information are really clunky and the source of a couple of outstanding bug reports ; so in the new dialog they will be gone. That would not only simplify the UI for the users but also make code maintenance much easier.
Re: Upcoming freezes KDE 4.7
On Wednesday 11 May 2011 00:39:37 Dawit A wrote:
> On Tue, May 10, 2011 at 5:50 PM, Sebastian Kügler wrote:
> > Yep, if it contains new strings, translators would need notification of
> > the new strings. If it's getting too close to release time, it would be
> > good to ask if there are problems with the translations then.
>
> Actually there are going to be very few string additions and changes.
A simple way to help translators is to commit new strings as soon as possible,
even if the code "around it" does not yet work or is not even there:
// reserve future strings
{
(void) i18nc("Some hint what it is for", "New string that I need");
(void) i18n("Another new string that I need later");
}
This is also a good way to make sure your translators' hints/comments (the "c"
part above) are sufficient for translation; the translator doesn't see the
code, they only see the strings.
Christoph Feck (kdepepo)
KDE Quality Team
Re: Upcoming freezes KDE 4.7
On Tuesday 10 May 2011 23:39:37 Dawit A wrote: > I will > try to inform the translators by marking my commits with "GUI:" and > also sending a message about the changes to the appropriate list. Once the soft freeze arrives you must first get permission from the kde-i18n- doc mailing list _before_ you commit any new strings, not just tell them after. Only typo fixes and existing untranslated strings can be comitted without advance permission, but you must still cc the list when you do so. If you can, follow Christoph's advice and commit as many of the strings as possible before the freeze into the class where they are needed, that way you don't annoy the translators with too many excpetion requests. The GUI tag only tells the documentation team (a different team entirely) that the UI has changed and they need to update the affected doco. John.
