Re: [rules-dev] [Proposal] Better release process: 2) 5.3.0.Beta1 in 6 weeks from now (5-AUG)
I don't believe we can ever get the release perfect, but knowing the dates right after
the previous release would help with the planning.
Maybe the last 2 weeks should be done using a release branch? We have community people
working on new features and using the master to get the codes stable would slow them down.
5.2.x branch was pretty long, still I didn't find it that hard to cherry pick and
merge my bug fixes.
Toni
On Jun 24, 2011, at 1:25 PM, Geoffrey De Smet wrote:
If we do more releases, the releases process will become easier and
maybe even a non-event.
At least, I believe that paradox :)
Here's what I propose:
- For the next 4 weeks, until 22-JUL, we focus on big, risky features.
- The 2 weeks after that, until 5-AUG, we focus on bugfixing and avoid risky changes.
On 5-AUG, I release 5.3.0.Beta1 directly from master.
If needed, we can call it 5.3.0.Alpha1 instead.
This will allow our users to verify backwards compatibility and new features sooner
and give us feed-back sooner.
What do you think? Good idea or too ambitious?
--
With kind regards,
Geoffrey De Smet
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Attachments:
- attachment.html (text/html — 1.8 KB)