ROSA 2012.1 > detailed development plans, the next steps...
5 posts
• Page 1 of 1
ROSA 2012.1 > detailed development plans, the next steps...
ROSA 2012.1 > detailed development plans, the next steps...
The official name of the distro is ROSA Desktop 2012
We had already the roadmap
http://www.rosalab.com/blogs/rosa-deskt ... s-approved
Now I can publish, for the most curious, something more technical
bye, NicCo
The official name of the distro is ROSA Desktop 2012
We had already the roadmap
http://www.rosalab.com/blogs/rosa-deskt ... s-approved
Now I can publish, for the most curious, something more technical
- 1. Repair all known -devel package Main, Non-Free and Restricted
> (remove .la files and rebuild) - 2. Import package texlive to ABF git and bind to the platform
- 3. Finish the X Server update
- 4. The first mass-rebuild and fix packages
- 5. Fixing upgrade to 2012.1 from 2012lts (it should be smooth)
- 6. Completion of upgrade KDE4 (done)
- 7. Adjust and enable rpmlint (partially done)
- 8. Switch to ffmpeg 0.11.x
- 9. Synchronization of wxWidgets and dependent packages with Cooker
> (complete conversion to the Unicode version)
- 10. The second mass rebild and repair that will fall due to the
> mismatch of the new standards, RPM and changes in the API ffmpeg - 11. Total imports from Cooker Contrib
- 12. Mass rebuild Contrib and repair that will fall on .la files,
> rpmlint, etc. - 13. Actively update Main, Non-Free and Restricted packages to the
> current versions
bye, NicCo
-
NicCo


- Amministratore

- Posts: 3693
- Joined: 6 December 2007, 19:54
After the Alfa 2 ISOs release, we have received a lot of updates.
Some days ago, at the beginning of this week
after updating to new gcc 4.7.2....., and a new rpm 5.x version
it started a complete mass rebuild of the entire ROSA 2012.1
/main
it was completed rapidly, in the mid of week with a good success,
only 500 srpm were reported errors, din't built at the first attempt
all these packages are being fixed, in the next few days...
As the result we would have a beta release with clean packages,
I remember you that Beta ISOs will be released in the next week
Here, the renewed
Some days ago, at the beginning of this week
after updating to new gcc 4.7.2....., and a new rpm 5.x version
it started a complete mass rebuild of the entire ROSA 2012.1
/main
it was completed rapidly, in the mid of week with a good success,
only 500 srpm were reported errors, din't built at the first attempt
all these packages are being fixed, in the next few days...
As the result we would have a beta release with clean packages,
I remember you that Beta ISOs will be released in the next week
Here, the renewed
-
NicCo


- Amministratore

- Posts: 3693
- Joined: 6 December 2007, 19:54
After the Beta 1 ISOs release, we have received a lot of updates.
Some days ago,
it started a complete mass rebuild of the entire ROSA 2012.1:
/contrib
Some days ago,
it started a complete mass rebuild of the entire ROSA 2012.1:
/contrib
-
NicCo


- Amministratore

- Posts: 3693
- Joined: 6 December 2007, 19:54
Some days ago,
it started a complete mass rebuild of the entire ROSA 2012.1:
/restricted
it started a complete mass rebuild of the entire ROSA 2012.1:
/restricted
-
NicCo


- Amministratore

- Posts: 3693
- Joined: 6 December 2007, 19:54
ROSA 2012.1 is frozen, soon will start the merging for OpenMandriva
[rosa-devel] Release candidate stage - repository is becoming frozen
A: Maillist for ROSA developers.
[rosa-devel] Release candidate stage - repository is becoming frozen
A: Maillist for ROSA developers.
Alex Burmashev wrote:Hello everyone.
From this moment of time we are beginning to freeze the rosa2012.1 repository.
What does this mean:
1) autopublish feature is disabled, nobody can autopublish packages to 2012.1 repo.
2) Manual publishing is enabled only for platform admins.
Currently there are a lot of people there, but i am going to leave there myself, Andrey Bondrov, Alex Kazancev and Arkady Shane ( for Gnome images ).
If you believe that you still need personal publishing feature - please contact me via one of the mail lists.
3) We are not going to start a full QA check for 2012.1 yet, packages still can be updated by maintainers and repo admins,
but if you can't contact some of platform admins to verify your update please create a QA request the same way as for 2012lts ( Marathon ).
4) If publish rights will be granted to you, please keep in mind that you keep responsibility and should not "break" the repo by your updates.
-
NicCo


- Amministratore

- Posts: 3693
- Joined: 6 December 2007, 19:54
5 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 3 guests
