Re: [Firebird-docs] Docbook version of 4.0 release notes

2018-10-26 Thread Helen Borrie
Martin,

You will probably want this file as well:

http://web.firebirdsql.org/download/prerelease/rlsnotes/manual/src/docs/rlsnotes/rlsnotes.xml


Keep a backup of the "live" version of this file, which does not
contain the  elements for v.4.

Helen


---
This email has been checked for viruses by AVG.
https://www.avg.com



___
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs


Re: [Firebird-docs] Docbook version of 4.0 release notes

2018-10-25 Thread Köditz , Martin
Hi Helen,

thank you.

Regards,
Martin


___
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs


Re: [Firebird-docs] Docbook version of 4.0 release notes

2018-10-25 Thread Helen Borrie


> In the meantime, I'll zip up the sources for the Fb4 alpha notes and
> put them in the pre-release area of the web.firebirdsql.org website
> and send you a link.

http://web.firebirdsql.org/download/prerelease/rlsnotes/manual/src/docs/rlsnotes/rlsnotes40/alpha_1.zip

Note, these files do not have Linux line-endings.  Your github client
should be set up to do the substitution on pushing.

Helen


---
This email has been checked for viruses by AVG.
https://www.avg.com



___
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs


Re: [Firebird-docs] Docbook version of 4.0 release notes

2018-10-25 Thread Helen Borrie
Martin wrote:

> basically, I agree with you. But why can't I find the release notes
> for the alpha 4.0 on Github? I thought Alpha 1 is freezed, isn't it?

The problem is not whether the alpha or beta is frozen, but of a
translator publishing notes for an alpha or beta and its being stuck
as the only translated version available because nobody followed up
with an update.

> I think there are some core sections that will not change much. So please 
> send me the material.

Actually, everything changes radically, especially from alpha -->
beta.  Alpha notes are really just placeholders for the new features,
in most cases.

> Just a thought. Would it be useful to make open changes in your own
> branches and merge them later with the release branch?

We could do something like that.  I have a repository for docs on
github that Denis and I used while we were working on the Developer's
Guide.  It has not been used since then.  It could do with a cleanup,
once I figure out how to do that.  I'm a Github moron but I did manage
to work it before our repositories went under 2FA.  At the moment I am
stuck with not being able to push anything.  Mark has given me some
tips on what I might try and I'm planning to get into that at the
weekend.

In the meantime, I'll zip up the sources for the Fb4 alpha notes and
put them in the pre-release area of the web.firebirdsql.org website
and send you a link.

Note, Dmitry is currently preparing stuff for the Fb4 Beta 1, so I
expect to be working on that over the next couple of weeks.

Helen


---
This email has been checked for viruses by AVG.
https://www.avg.com



___
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs


Re: [Firebird-docs] Docbook version of 4.0 release notes

2018-10-25 Thread Köditz , Martin
Hi Helen,

basically, I agree with you. But why can't I find the release notes for the 
alpha 4.0 on Github? I thought Alpha 1 is freezed, isn't it?

> Also, bug fixes are meant to be cleaned out for the final release notes, so 
> that only bugs that existed in older versions are documented.

Ok, I didn't know that.

> All in all, you are taking on a hot task if you want to keep translations in 
> synch during alpha and beta.  I can send them to you privately if you like.

I think there are some core sections that will not change much. So please send 
me the material.

Just a thought. Would it be useful to make open changes in your own branches 
and merge them later with the release branch?

Regards
Martin

-Ursprüngliche Nachricht-
Von: Helen Borrie [mailto:hele...@tpg.com.au] 
Gesendet: Mittwoch, 24. Oktober 2018 20:46
An: Chatter regarding Firebird documentation 

Betreff: Re: [Firebird-docs] Docbook version of 4.0 release notes

Martin,

you wrote:

> where may I get the docbook version oft he 4.0 alpha release notes?
> Would be great if I can translate those in time.

Release Notes sources don't go into version control until the release itself, 
specifically to avoid having translators putting in effort to translate stuff 
that is going to change a lot as the release evolves.

Take it from me, getting the background for new features and improvements is 
like squeezing blood from a stone!  It is just how it is, nobody's fault.  
Typically (and correctly) the developers don't commit themselves to documenting 
new things until they are close to completing them.

Also, bug fixes are meant to be cleaned out for the final release notes, so 
that only bugs that existed in older versions are documented.

All in all, you are taking on a hot task if you want to keep translations in 
synch during alpha and beta.  I can send them to you privately if you like.

Helen


---
This email has been checked for viruses by AVG.
https://www.avg.com



___
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs


___
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs


Re: [Firebird-docs] Docbook version of 4.0 release notes

2018-10-24 Thread Helen Borrie
Martin,

you wrote:

> where may I get the docbook version oft he 4.0 alpha release notes?
> Would be great if I can translate those in time.

Release Notes sources don't go into version control until the release
itself, specifically to avoid having translators putting in effort to
translate stuff that is going to change a lot as the release evolves.

Take it from me, getting the background for new features and
improvements is like squeezing blood from a stone!  It is just how it
is, nobody's fault.  Typically (and correctly) the developers don't
commit themselves to documenting new things until they are close to
completing them.

Also, bug fixes are meant to be cleaned out for the final release
notes, so that only bugs that existed in older versions are
documented.

All in all, you are taking on a hot task if you want to keep
translations in synch during alpha and beta.  I can send them to you
privately if you like.

Helen


---
This email has been checked for viruses by AVG.
https://www.avg.com



___
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs