I have validator access to your locale as well.. I see that you hadn't rolled out 3.0 (only 3.0.1, which isn't finished)
The process is (at the page http://nn.wordpress.org/wp-admin/tools.php?page=rosetta_manage_translations) 1: build package 2: roll out package When the package is rolled out, regular users will see it at their upgrade screen ( somedomain.net//wp-admin/update-core.php ) I built the 3.0 package for you with these settings: - Get translations from: translate.wordpress.org - local branch for dist-files: tags/3.0 - project: 3.0 and 3.0.x (usually you'd use development, but since there has been changes in the po-file, I used this one) - WordPress revision: 15274 (this was the revision where 3.0 was tagged at http://core.trac.wordpress.org/ ) - WordPress version: 3.0 So now you have this package in "built versions". You can roll it out if you want! Peter On Thu, Jul 29, 2010 at 00:16, Eivind <[email protected]> wrote: > Hi, > > I recently translated and committed files to > http://svn.automattic.com/wordpress-i18n/nn_NO/ (tags, branches and > rosetta - not trunk), made a screenshot, and requested deployment. > > Now, nn.wordpress.org has the correct rosetta translation and screenshot. > What is needed to allow normal wordpress users to upgrade to 3.0 in nn_NO > from their dashboard? I am beginning to understand this has nothing to do > with the deployment process. > > Forgive my ignorance. > > All the best > > Eivind Ødegård > > > _______________________________________________ > wp-polyglots mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-polyglots > -- +47 920 42 782
_______________________________________________ wp-polyglots mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-polyglots
