When a version is released, you can't add new features or fixes into
that release, as those aren't in that release.
There is usually a new, empty section for the next release at the top of
the file.
Ah.... you read it wrong and out of context: I was commenting on a given
situation, and you read this method from outside that situation :-)
All fixes and updates should be added to the SNAPSHOT area.
Martijn
Gwyn Evans wrote:
How does that work then - If I add to the last-released, i.e. b4 now,
don't you have to manually find the seperation from real b4 ones and
move them when you do the next release?
/Gwyn
On 25/08/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All,
Please add the changes to the right section. Last additions are done at
the already released wicket 1.1-b3, not to the snapshot section.
Martijn
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
