PostSharp Technologies
What is the release plan for Metalama #41
-
|
Is there already a more or less reliable release plan for Metalama? I have to start new projects and I can use the current prerelease version, but I could not use it for creating production releases. Some milestones could be helpful. Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
The release plan is that we are feature-complete and almost, but not yet, code-complete (i.e. there are still some minor gaps) and we are now working on stabilizing the product. When we will have a feeling that the product is stable, we will make it Release Candidate, then General Availability. How long this will still take before the last milestone, we don't know. Since there is no run-time component in Metalama, it does not make sense to avoid using it for a production release if you use if for development anyway. However I understand you may be bound by corporate policies that would make sense for run-time components, but actually apply to all components you use. So unfortunately I cannot give you a short answer. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the quick response.
I will discuss the matter internally.
Regards
From: Gael Fraiteur ***@***.***>
Sent: Monday, September 5, 2022 9:48 AM
To: postsharp/Metalama ***@***.***>
Cc: steinerm55 ***@***.***>; Author ***@***.***>
Subject: Re: [postsharp/Metalama] What is the release plan for Metalama (Discussion #41)
The release plan is that we are feature-complete and almost, but not yet, code-complete (i.e. there are still some minor gaps) and we are now working on stabilizing the product. When we will have a feeling that the product is stable, we will make it Release Candidate, then General Availability. How long this will still take before the last milestone, we don't know.
Since there is no run-time component in Metalama, it does not make sense to avoid using it for a production release if you use if for development anyway. However I understand you may be bound by corporate policies that would make sense for run-time components, but actually apply to all components you use.
So unfortunately I cannot give you a short answer.
—
Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpostsharp%2FMetalama%2Fdiscussions%2F41%23discussioncomment-3556190&data=05%7C01%7C%7C71bddee89b394dbae3a308da8f12ea7b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637979608651212012%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=QlIlPE8rlfHJF3IXlx3VoYWu7GY0jdztRsAhptXOwT4%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJF376XACQYBI5LBQKXK4ZDV4WQR5ANCNFSM6AAAAAAQEWB7YE&data=05%7C01%7C%7C71bddee89b394dbae3a308da8f12ea7b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637979608651212012%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7RrXJPOX0NfJCIhn4ItVlG69C%2FVD%2FdzRWE9zsBwcNBc%3D&reserved=0>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Beta Was this translation helpful? Give feedback.
The release plan is that we are feature-complete and almost, but not yet, code-complete (i.e. there are still some minor gaps) and we are now working on stabilizing the product. When we will have a feeling that the product is stable, we will make it Release Candidate, then General Availability. How long this will still take before the last milestone, we don't know.
Since there is no run-time component in Metalama, it does not make sense to avoid using it for a production release if you use if for development anyway. However I understand you may be bound by corporate policies that would make sense for run-time components, but actually apply to all components you use.
So unfortunately I can…