F27 Beta is coming soon and there was (still is) some discussion about Modular Server. We will probably not release Modular Server for the F27 Beta release date, but despite of when it will come out, we need to prepare/rewrite the server website for modularity in any case, as the Council already approved it. My plan would be to release F27 Beta websites and immediately start branching a devel branch for Modular Server, which could become real after some weeks of the Beta release date.
As this will be a lot of new strings we need to freeze translations before pushing the source files and should make sure our scripts for checksums point to the right links. There is not much we know other than that actually, I'll add information below once we get them. For now it is good to track all the pieces we need under this ticket.
I will also help with some copywriting.
@mattdm cool !! I'm adding here some more information of what the plan would be to get the pages live from now to F27 GA. https://pagure.io/fesco/issue/1775#comment-466045
So it seems we are going towards a ad hoc release cycle for Modular Server, which even went through the Server SIG today. Please take note of: https://fedoraproject.org/wiki/User:Langdon/Proposed_Modular_Server_Release
That means we need to branch Modular Server immediately after F27 Beta Release date and we also need to freeze translations. I will take care of informing L10n teams in time.
Adding @codeblock to this issue as well; he said he'd be able to help. So is there a specific branch we should use now for building up the changes we want to deploy after F27 Beta releases?
@mattdm and @langdon: Something that would help here would be new testimonials from either developers or users of the new Modular Server. I realize there's not a huge group of folks to tap for this, but the point is our existing Server testimonials are a bit long in the tooth, and arguably not useful for Modular Server. A quote from each of 2-3 people that cover compelling features in the Modular Server would help immensely. (Q.v. https://getfedora.org/server/ if you're confused about the testimonials I'm referring to.)
No there is no specific branch for now, I thought to branch directly at Beta release date, so we have an already merged beta F27 Beta branch. If this is going to be too far away due to other Beta slips, we can branch anytime.
Might not be a bad idea to make a special branch now, iff. it's not troublesome. The regular Beta release was still at risk yesterday, although the outlook is better this week for sure.
We are ready to go ahead towards Modular Server now. I made a new modular-server branch where we should work on, will build it also in staging to show you how things look like.
Note: please file a PR at least for the first commit, because I need to freeze translations in production first.
Is there a mockup somewhere of the new content?
I have some questions and woud like to organize this a bit, because e don't have much time. I'll add people to the single questions, hoping you will reply ;)
@langdon are Modular Server images to treat like other ISO files? So for my ignorance, but how do they work? Which format? Do we need to use automation or just fixed links? How many different images we will have? (remember also ARM, netinstall, alt...)
@duffy @ryanlerch do we have a mockup how this should look like? I guess the same structure as traditional server, but images? Backgrounds? Icons?
@mattdm @pfrields feel free to worlk already on text, messages, whatever we need from a Marketing and technical POV to be as clear as possible.
I can put things together and make all the rest. I am just not sure how you want to have these pages and what the content will be. Also, if you feel we should setup a meeting to discuss this better, let's do it. Thank you all for your help.
Metadata Update from @robyduck: - Issue tagged with: release
This is an old plan, new modularity will get live tomorrow, Closing this as fixed anyway, although in another ticket.
Metadata Update from @robyduck: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.