Sorry for being a bit late.
For all products that allow new issues I've created the follwoing:
Version - "4.3.0-dev" to label issues where it was found.
Milestone - "4.3.0" to label where a fix should go into.
When something should be missing just give me a hint.
@All:
I just want to remind
works for me :)
> On Jan 24, 2019, at 4:26 PM, Andrea Pescetti wrote:
>
> Marcus write:
>> No further opinions? Come on :-)
>
> More or less, my opinion is the same as yours: we can't use "trunk" since
> trunk is a moving target ("trunk" today is something different than "trunk"
> in a few mo
Marcus write:
No further opinions? Come on :-)
More or less, my opinion is the same as yours: we can't use "trunk"
since trunk is a moving target ("trunk" today is something different
than "trunk" in a few months). I think we used codes such as 4.2.0-dev
and this should be the way to go, so
No further opinions? Come on :-)
Marcus
Am 19.01.19 um 12:11 schrieb Marcus:
Am 19.01.19 um 09:39 schrieb Peter Kovacs:
Maybe a version trunk would help?
before I spent 30 minutes to update all the products in BZ with a new
version let me summarize what we have and what is really needed:
Am 19.01.19 um 12:24 schrieb Mechtilde:
Hello,
Am 19.01.19 um 12:11 schrieb Marcus:
Am 19.01.19 um 09:39 schrieb Peter Kovacs:
Maybe a version trunk would help?
before I spent 30 minutes to update all the products in BZ with a new
version let me summarize what we have and what is really nee
Hello,
Am 19.01.19 um 12:11 schrieb Marcus:
> Am 19.01.19 um 09:39 schrieb Peter Kovacs:
>> Maybe a version trunk would help?
>
> before I spent 30 minutes to update all the products in BZ with a new
> version let me summarize what we have and what is really needed:
>
> - trunk is used to comm
Am 19.01.19 um 09:39 schrieb Peter Kovacs:
Maybe a version trunk would help?
before I spent 30 minutes to update all the products in BZ with a new
version let me summarize what we have and what is really needed:
- trunk is used to commit changes that could be integrated in a release
som
Maybe a version trunk would help?
On 19.01.19 08:13, Mechtilde wrote:
> Hello,
>
> can we get the version "trunk2 in bugzilla to track the issues which
> comms there and are not in the 420-dev branch.
>
> Kind regards
>
-
To unsu
Hello,
can we get the version "trunk2 in bugzilla to track the issues which
comms there and are not in the 420-dev branch.
Kind regards
--
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 499