As per mdz, perhaps it is better to leave the material unchanged. I'll
close the bug for now.
** Changed in: ubuntu-docs (Ubuntu)
Status: Confirmed => Rejected
--
Firefox default Homepage should now reffer to 6.06.1
https://bugs.launchpad.net/bugs/55913
You received this bug notification
On Thu, Jun 14, 2007 at 07:31:15AM -, Matthew East wrote:
> No, I don't think so. As a result of the passage of time, and given that
> we're not going to be changing the version number in the About Ubuntu
> document, and given that updating a package in Dapper is a non-trivial
> exercise, I'm t
> Do others have strong views?
No
I wonder if this still makes sence.
Since the useres already get used to it! ??
...and given it isn´t a trivial changeat least for dapper.
We should only leave this bug open, if we intend to change anything in
future (read as LTS+1)
--
Firefox default Homep
No, I don't think so. As a result of the passage of time, and given that
we're not going to be changing the version number in the About Ubuntu
document, and given that updating a package in Dapper is a non-trivial
exercise, I'm tempted to say that we should probably do nothing about
this bug now. D
Matthew, did this change get made? Can we close this bug?
--
Firefox default Homepage should now reffer to 6.06.1
https://bugs.launchpad.net/bugs/55913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
A problem with changing the version number in the documentation - it
can't be done in translations, because the entities we use to substitute
the version number are expanded into the translated xml.
I've started a discussion on the doc list about how to fix this for Edgy
[1], but for now the appro
** Changed in: ubuntu-docs (Ubuntu)
Importance: Untriaged => Medium
Status: Unconfirmed => Confirmed
--
Firefox default Homepage should now reffer to 6.06.1
https://launchpad.net/bugs/55913
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listi
On Sun, Aug 13, 2006 at 10:05:31AM -, Matthew East wrote:
> I can't think of a way that the About Ubuntu document automatically
> relies on lsb_release at the moment.
It should perform that substitution during the build process. Someone from
the development team should be able to provide a si
On Sun, Aug 13, 2006 at 10:24:36AM -, Thilo Six wrote:
> An other thought maybe for edgy
>
> Why not have a systemwide variable for this purpose like the same way we
> define the LANG variable?
>
> Maybe:
> $ echo $DISTRIBUTION
> Ubuntu
> $ echo $RELEASE
> Dapper
> $ echo $RELEASENUMBER
> 6.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Thilo Six:
> If we start scipting the Relese Number in "About Ubuntu" why not do the same
> with the FF hp?
About Ubuntu and the other documents are docbook xml and take their
version numbers from one file: /usr/share/ubuntu-docs/libs/global.ent
An other thought maybe for edgy
Why not have a systemwide variable for this purpose like the same way we
define the LANG variable?
Maybe:
$ echo $DISTRIBUTION
Ubuntu
$ echo $RELEASE
Dapper
$ echo $RELEASENUMBER
6.06
$ echo $RELEASENUMBERMINOR
.1
--
Firefox default Homepage should now reffer to
[OT]
First i like to thank you for the productive discussion here.
That´s sadly not the normal way in FOSS.
[/OT]
Matt:
>Indeed, it would be best if the "About Ubuntu" document automatically
> substituted its version number based on lsb_release, so that we have even
> fewer things to change.
One
I can't think of a way that the About Ubuntu document automatically
relies on lsb_release at the moment.
So, the changes I will do, based on what Matt has commented above are:
* Remove the version number from the firefox homepage and its translations
* Bump the version number in all of the docu
If the inconsistency with the Firefox default page is an issue, I'd prefer
to remove the version number entirely. It doesn't need to be there, and
it's just one more opportunity for human error when doing releases.
Indeed, it would be best if the "About Ubuntu" document automatically
substituted
Thanks for this Matt: About Ubuntu and all the other ubuntu-specific
documents all get their version number from the same file, so changing
that will change it all.
The firefox homepage is separate from this scheme, so if you want to
leave that and upload new -docs packages with the change to Abou
The support team can't rely on this for anything particularly useful; a
user could upgrade to an equivalent level immediately before the point
release, and have the same packages without the version number changing.
Changing "About Ubuntu" should satisfy their needs by giving them an
easy way to h
I'm still not completely satisfied that we can close this bug. Matt, as
Thilo pointed out on the mailing list, on the point release spec it
says:
"The support team would like to have good traceability of the contents
of Dapper at its original release and at each point release.
The support team and
understand.
I just thought it would be more obviously for users they have everything
installed and do not need to worry they are missing something. Because the FF
default homepage is something like a "figurehead".
I do not want to cause unnecessary work. It just thought it shouldn´t
get lost at
6.06.1 is a maintenance release of 6.06. It merely incorporates many
post-release updates and doesn't constitute a proper new release. It is
not necessary or appropriate to change the version number in every
context. 6.06 is still correct; systems installed or upgraded with
6.06.1 are simply run
...of course i meant the Dapper point update which where released today.
--
Firefox default Homepage should now reffer to 6.06.1
https://launchpad.net/bugs/55913
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
20 matches
Mail list logo
